JP2002163225A - USB connection control method and USB system - Google Patents

Abstract

(57) [Summary] [Problem] A non-PC USB host device cannot secure sufficient storage capacity, and therefore cannot hold driver software necessary for operating various USB device devices, so that a USB device device cannot be held. There was a problem that could not be used. A USB device device connected to a USB host device includes driver software storage means for storing driver software necessary for connecting and operating the USB device device. USB
When the USB device device 120 is connected to the host device 110, the product ID and vendor ID of the USB device device currently usable by the USB host device 110 and the connected US
Check the product ID and vendor ID of device B. If the collation results are different, the USB
The driver software is acquired from the device device 120, and the connected USB device device is made usable.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a USB (Universa)
The present invention relates to a USB connection control method and a USB system for a USB host device to acquire driver software for a USB device device connected via a (Serial Bus) bus.

[0002]

2. Description of the Related Art Conventionally, as a USB host device for connecting a USB device via a USB, there is a USB host system built in a personal computer.
Generally, in order to enable a USB device to be used with a USB host system, a user installs driver software necessary for operating the USB device by using a floppy (registered trademark) disk or CD-ROM.
Is installed in the USB host system from such a storage medium.

Alternatively, various information such as driver software can be obtained from various peripheral devices or information sources on a network by using a general-purpose interface function.

Therefore, in a USB host system built in a personal computer, even when a new USB device device is connected, it can be appropriately processed by acquiring driver software as needed.

[0005]

However, in the case of a USB host device built in a small device having no general-purpose function such as a personal computer, the capacity of the built-in storage device is small, so that various USB device devices are used. It is impossible to keep a plurality of driver software for operation. Further, there is a problem that it is impossible to have various peripheral device interfaces for acquiring driver software from outside.

The present invention solves the above-mentioned conventional problems. Even if a storage device holding driver software for operating a USB device is a small device having a small capacity, a user can use a USB host device. USB connection control method for automatically acquiring necessary driver software by simply connecting a USB device device to a USB host device and making the USB device device usable
It is intended to provide a B system.

[0007]

In order to achieve this object, a USB connection control method according to the first aspect of the present invention relates to a USB connection control method for a USB connected to a USB host device via a USB bus.
USB for the USB host device to acquire driver software necessary for operating the device device
In the connection control method, a product ID and a vendor ID unique to the USB device device are acquired from the USB device device connected to the USB host device (procedures 301 and 302), and a driver already held in the USB host device is acquired. The product ID and the vendor ID of the software are compared with the newly acquired product ID and the vendor ID (step 303), and when the comparison result does not match, the USB host device is stored in the USB device device in advance. Acquire the driver software in response to a driver software transfer request for operating the USB device (steps 304 and 30)
5).

[0008] The USB system according to claim 2 is a USB system.
US for the B host device (USB host device 110)
USB connected via B bus (USB bus 100)
In a USB system in which the USB host device obtains driver software necessary for operating a device device (USB device device 120), the USB device device is used in order for the USB device device to operate the USB device device. Driver software storage means (driver software storage means 121) for storing driver software used by the USB host device in advance, and driver software stored in the driver software storage means in response to a vendor request for a driver software transfer request from the USB host device. The US
Driver software transfer means (driver software transfer means 122) for transferring to the B host device;
A device ID storage unit (device ID storage unit 111) for storing the product ID and the vendor ID of the driver software, and a device ID obtaining unit for obtaining the product ID and the vendor ID of the USB device device by a standard request (Device ID acquisition unit 112), the product ID and vendor ID acquired by the device ID acquisition unit, and the product I stored in the device ID storage unit.
A device ID matching unit (device ID matching unit 113) for matching D and the vendor ID, and requesting transfer of driver software stored in the USB device device by a vendor request when the matching result does not match. Driver software acquisition means for acquiring driver software (driver software acquisition means 11
4).

According to the present invention, driver software for operating a USB device device is stored in advance in a storage device provided in the USB device device,
U host device and USB device device
By providing a transfer request function of driver software based on a vendor request of the SB standard and a response function thereof, when a USB device device is connected to a USB host device and driver software is required, the USB software is required.
It becomes possible to transfer the driver software of the USB device device from the USB device device to the USB host device via the bus, and the storage device holding the driver software does not have a general-purpose function like a personal computer and has a small capacity. Even in a small device or the like, the USB host device can automatically acquire necessary driver software.

[0010]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 shows a US according to the present invention.
FIG. 2 is a block diagram illustrating a schematic configuration of a USB host device and a USB device device configuring the B system. In FIG. 1, a USB host device 110 and a USB device device 120 are connected to each other via a USB bus 100,
Means for enabling USB connection are separately provided in the USB host device and the USB device device.

That is, the USB host device 110
Device I for storing product ID and vendor ID of driver software held in SB host device
D storage means 111, device ID acquisition means 112 for acquiring a product ID and a vendor ID of a USB device device by a standard request, device ID acquisition means 11
2. Device ID collating means 113 for collating the product ID and the vendor ID obtained in step 2 with the product ID and the vendor ID stored in the device ID storing means 111, and driver software stored in the USB device by the vendor request Driver acquisition means 11 for requesting and acquiring a transfer
4 is provided.

Further, the USB device device 120 is a USB device device.
The driver software storage unit 121 that stores driver software used by the USB host device 110 to operate the B device device 120, and the driver software storage unit 121 in response to a vendor software transfer request from the USB host device 110. A driver software transfer unit 122 that transfers the stored driver software to the USB host device 110 is provided.

The transfer of the driver software is realized by a vendor request based on the USB standard. To this end, a transfer request for driver software on the USB host device 110 side and a USB device device
The function of the driver software transfer processing on the side is defined by a vendor request based on the USB standard, and this function is executed by the driver software acquisition means 114 and the driver software transfer means 122.

FIG. 2 is a block diagram showing a software configuration in the USB system shown in FIG. FIG.
As shown in FIG. 2, the software of the USB host device 201 includes an application 202, driver software 203 for operating the USB device device, and
It is hierarchically composed of USB host device ID storage means for realizing the SB host device function and USB host controller driver software 204 for operating the controller.

A USB device device 2 that can be connected to the USB host device 201 via the USB bus 211
05, 207, and 209 store respective driver software 206, 208, and 210 necessary for operating these USB device devices in their respective storage devices. These driver software 206,
208 and 210 are binary software operating on the USB host device 201 or JAVA (registered trademark).
And other interpreted languages.

FIG. 3 is a flowchart showing a connection operation in the USB host device and the USB device device having the above configuration. When the USB device device 120 is connected to the USB host device 110, the USB host device obtains the product ID and the vendor ID of the USB device device by the device ID obtaining means 112. That is,
In step 301, the USB host device transmits the standard request “Get_descriptor” based on the USB standard to the connected U
Transmitted to the SB device, and in step 302, the USB device 120 responds to the
The USB host device transmits a device descriptor based on the standard to the USB host device, and the USB host device acquires a product ID and a vendor ID unique to the USB device device in the device descriptor.

The USB host device 110 has a device ID
The product ID and the vendor ID stored in the storage unit 111, that is, the product ID and the vendor I of the driver software currently held inside the USB host device and capable of operating the USB device device
D and the product ID and the vendor ID of the USB device device 120 obtained in step 302
At 03, the collation is performed by the device ID collation means 113.

If the collation results do not match, the USB host device 110 executes the vendor request by the driver software acquisition means 114 to execute the USB device 1
Then, the driver software stored in the driver software storage unit 121 is obtained. That is, procedure 3
At 04, the USB host device 110 transmits a vendor request to the USB device device 120 to request the transfer of driver software. In step 305, the USB device device 120 reads the driver software stored in the driver software storage unit 121 in response to the vendor request, and
To the USB host device 110, and the USB host device 110 acquires the transferred driver software.

For example, in FIG. 2, when the USB device device 205 is connected to the USB host device 201,
The USB host device 201 executes the above steps 301 to 3
05, the driver software 206 is acquired. U
The SB host device 201 incorporates the obtained driver software 206 into the driver software 203 and makes the connected USB device device 205 usable.

[0020]

As described above, according to the present invention,
Driver software for operating the USB device device is stored in advance in a storage device provided in the USB device device, and a transfer request function of the driver software based on a USB standard vendor request is stored in the USB host device and the USB device device. And providing the response function, the driver software of the USB device device can be transferred from the USB device device to the USB host device when the USB device device is connected to the USB host device and driver software is required. This makes it possible to acquire driver software for automatically operating the connected USB device by simply connecting the USB device to the USB host device even in a small device having a small storage device. Possible That.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a schematic configuration of a USB system according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a software configuration of the USB host device and the USB device device shown in FIG. 1;

FIG. 3 is a flowchart showing a connection operation of the USB connection control method according to one embodiment of the present invention.

[Explanation of symbols]

Reference Signs List 100 USB bus 110, 201 USB host device 111 Device ID storage means 112 Device ID acquisition means 113 Device ID collation means 114 Driver software acquisition means 120, 205, 207, 209 USB device device 121 Driver software storage means 122 Driver software transfer means 202 Application 203 USB device driver software 204 USB host controller driver software 206, 208, 210 Driver software

Claims (2)

[Claims] 1. A USB connection control method for causing a USB host device to acquire driver software necessary for operating a USB device device connected to the USB host device via a USB bus, the USB host device comprising: Product ID unique to the USB device from the USB device connected to the device
And the vendor ID are obtained. The product ID and the vendor ID of the driver software already stored in the USB host device are compared with the newly obtained product ID and the vendor ID. The USB device in which the host device is held in the USB device device in advance
Acquiring the driver software by a transfer request of the driver software for operating the device device,
A USB connection control method, comprising: 2. A USB system in which the USB host device obtains driver software necessary for operating a USB device device connected to the USB host device via a USB bus, wherein the USB device device includes: The USB for operating the USB device device
A driver software storage unit for storing driver software used by the host device in advance; and a driver software stored in the driver software storage unit in response to a vendor request for a driver software transfer request from the USB host device, to the USB host device. And a driver software transfer means for transferring the driver software, wherein the USB host device comprises:
D, a device ID storing unit for obtaining a product ID and a vendor ID of the USB device device by a standard request, and a product I obtained by the device ID obtaining unit.
D and a device ID collating means for collating the vendor ID with the product ID and the vendor ID stored in the device ID memory means. When the collation results do not match, the device ID is stored in the USB device by a vendor request. A USB system, comprising: driver software acquisition means for requesting transfer of driver software to acquire the driver software.