JP2007052630A - Device driver application method and host device using the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To utilize functions that a peripheral device has even if a host device is not mounted with a device driver complying to class specifications of the peripheral device. <P>SOLUTION: The host device (car navigation) 1 acquires information on a logical interface described in class specifications from the peripheral device 2, when the host device does not have any device drivers for using functions (modem functions) that the peripheral device (cellular phone) 2 has. Prescribed commands (AT commands) used in the functions (modem functions) are transmitted to each acquired logical interface, and a logical interface responding to the commands appropriately is retrieved. Then, functions that the peripheral device 2 has are used through the retrieved logical interface. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a device driver application method for applying a device driver for using a function of a peripheral device in a host device to which the peripheral device is connected, and a host device using the device driver application method.

  In personal computers, USB (Universal Serial Bus) is widely used as one of peripheral device connection interfaces. Some embedded devices such as car navigations are equipped with a USB interface, and are used to connect a mobile phone or the like. In normal USB connection, the personal computer and car navigation are host devices, and the connected peripheral devices are peripheral devices.

  The host device includes a host controller serving as an electrical and physical interface with the peripheral device, and a host driver that is software for driving and controlling the host controller. In order for the host device to use the functions of the peripheral device, in addition, a device driver that controls the peripheral device via the host controller and the host driver is necessary, and this is installed and used.

  USB discloses a class specification that defines the functions and interfaces of typical peripheral devices. If the peripheral device meets this published class specification and the host device is equipped with a device driver corresponding to the previously published class specification, the user simply connects the peripheral device to the host device. It can be used, and it is not necessary to install a device driver in the host device.

  However, if the peripheral device is provided with a unique function that is not in the published class specification, for example, if the communication device is provided with a monitor function unique to the peripheral device manufacturer (vendor), the vendor will provide its own class specification. It is also possible to define a vendor-specific class specification (vendor-specific class). In such a case, the vendor generally provides a medium such as a CD-ROM storing a device driver for using the vendor, and the user generally installs it on the host device.

  When it is necessary to install a device driver in advance on the host device side, such as a peripheral device having a vendor-specific class, the user not only performs the installation work but also a media drive that stores the device driver provided by the vendor. It is also necessary to prepare a device, and when a peripheral device to be connected is replaced, a sequential installation operation becomes necessary, which is troublesome.

  In this regard, the technology described in Patent Document 1 stores a device driver program to be installed in the host device on the peripheral device side, and the host device reads this to automatically execute installation and store the device driver. Media is not required.

JP 2003-150530 A

  According to the above-mentioned Patent Document 1, the peripheral device is equipped with a device driver to be installed in the host device. For this purpose, each peripheral device must support this, and the burden on the device manufacturer is Increase. In addition, there are various types of OSs and host drivers mounted on the host device. If device drivers corresponding to the OSs are mounted, the memory capacity for storing them increases, which causes the device cost to rise.

  Further, when a mobile phone owned by a user is connected to the car navigation for communication, mobile phones of various vendors are connected. Therefore, if the class specifications are not standardized among the vendors of each mobile phone, for example, if only the device driver of the class specifications for which car navigation is publicly available, the use that has the mobile phone of the vendor specific class The user cannot use it, and it becomes necessary to replace the cell phone with a mobile phone compatible with car navigation. This is inconvenient for the user.

  The present invention solves the above-described problem, and does not include a device driver installed on the peripheral device side, and even when the host device does not include a device driver corresponding to the class specification of the peripheral device. The purpose is to make it possible to use the functions of the peripheral device.

  In order to achieve the above object, in the device driver application method according to the present invention, when the host device does not have a device driver for using the functions provided in the peripheral device, it is described in the class specification description data from the peripheral device. Get information about the specified logical interface. For each acquired logical interface, a predetermined command handled by a desired function is transmitted, a logical interface that obtains a predetermined response is searched, and a function included in the peripheral device is used via the searched logical interface. .

  In the host device according to the present invention, class specification acquisition means for acquiring information on the logical interface described in the class specification description data from the peripheral device, and a predetermined command to be handled with a desired function for each acquired logical interface An interface search driver for searching for a logical interface that sends out and obtains a predetermined response is provided. When the host device does not have a device driver for using the function provided by the peripheral device, the function provided by the peripheral device is used via the logical interface searched by the interface search driver.

  According to the present invention, even when there is no device driver corresponding to the class specification of the connected peripheral device in the host device, if the device can be used functionally, a new device driver is installed. The peripheral device can be used without doing so. In addition, since it can be implemented only by the device driver on the host device side, the peripheral device can be left as it is, and there is an effect that a problem on the peripheral device side such as an increase in the cost required for the memory does not occur. is there.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing an embodiment of a USB communication system using a device driver application method according to the present invention. The present embodiment is a communication system having a configuration in which a car navigation (hereinafter referred to as “car navigation”) 1 is used as a host device and a mobile phone 2 is used as a peripheral device and these are connected by a USB cable 10.

  First, the internal configuration of the car navigation 1 will be described. The car navigation overall control unit 11 includes a CPU 12, a memory 13, a navigation peripheral I / F unit 14, and a USB host controller 15. The CPU 12 controls the system according to various programs 131 to 134 described later stored in the memory 13 to realize a car navigation function. The USB host controller 15 is used to match an electrical and physical interface with the mobile phone 2.

  The navigation peripheral I / F unit 14 is connected to the following elements. The display unit 16 displays various information such as map information. The operation unit 17 is used by the user to perform various operation settings such as route search. The operation unit 17 also instructs the mobile phone 2 to transmit data to the mobile phone 2. The GPS antenna 18 receives radio waves sent from GPS satellites in order to detect position information of the own vehicle. The map information storage unit 19 is a recording medium such as a CD-ROM for storing map information and a data reading drive device.

  Various programs and data 131 to 134 stored in the memory 13 will be described. The car navigation overall control processing unit 131 performs, for example, the following car navigation function processing. First, power-on is detected, and the vehicle position is detected from information received from the GPS antenna 18. Then, the map data around the detected vehicle position is read from the map information storage unit 19 and output to the display unit 16. If the user operates the operation unit 17 to detect that the destination has been set, the current position and the route to the set destination are searched, and the search route is displayed in the map information. If it is detected by the operation instruction of the operation unit 17 that data communication using the mobile phone 2 is detected, USB communication control with the mobile phone 2 is performed using the USB device driver 133 and the USB host driver 134, and the mobile phone 2 is connected. It also performs processing such as performing data communication.

  The USB device driver 133 is software for communicating with a USB device function processing unit 233 in the cellular phone 2 to be described later, and controls the activation of the USB host driver 134 while controlling the USB device in the cellular phone 2 designated by the operation unit 17. Enable the function. A driver corresponding to each USB device function to be used is mounted on the USB device driver 133. In this embodiment, a driver corresponding to a modem function 1331 and a driver corresponding to a function other than a modem 1332 (audio function for hands-free voice call) Etc.) are implemented. Furthermore, the present embodiment is characterized in that a use function compatible interface search driver 1333 is provided in the USB device driver 133.

  The USB device driver identification data unit 132 stores identification data such as a class ID and a vendor ID in the class specification definition as information for identifying the driver installed in the USB device driver 133 for each USB device function. .

  FIG. 4A shows an example of information stored in the USB device driver identification data unit 132.

  In FIG. 4A, 401 indicates a device class ID, 402 indicates a device subclass ID, and these are IDs included in a device descriptor indicating the characteristics of the entire USB device. The illustrated setting values indicate values defined in the class specification of the communication device, the device class ID indicates the communication device class ID, and the device subclass ID indicates the communication device subclass ID.

  Reference numeral 403 denotes an interface class ID, and 404 denotes an interface subclass ID, which is an ID included in an interface descriptor indicating a function in the USB device. Each illustrated ID value also indicates a value defined by the class specification of the communication device, the interface class ID indicates a communication interface class, and the interface subclass ID indicates an “Abstract Control Model” setting corresponding to a modem function.

  The USB host driver 134 is software that enables access to the USB host controller 15. The USB host driver 134 controls the USB host controller 15 in accordance with activation control from the USB device driver 133 and performs USB communication.

  Next, a configuration example of the mobile phone 2 will be described. In this embodiment, it is assumed that an existing device is used for the mobile phone 2 as a USB peripheral device, and main components related to the operation of this embodiment are shown.

  The overall mobile control unit 21 of the mobile phone 2 includes a CPU 22, a memory 23, and a USB function controller 24. The CPU 22 reads out and executes various programs 231 to 234 stored in the memory 23 to realize a mobile phone function.

  The USB function controller 24 is a USB interface on the USB peripheral device side, and in accordance with commands from the USB function driver 234 and a USB device function processing unit 233 that controls the activation of the USB function driver 234 and performs this function processing, the USB host on the car navigation 1 side. USB communication with the controller 15 is performed.

  The memory 23 stores a mobile phone overall control processing unit 231, a class specification description data unit 232, a USB device function processing unit 233, and a USB function driver 234. In this embodiment, the USB device function processing unit 233 includes a telephone directory exchange function (a function for externally writing and reading telephone directory data stored in a mobile phone), a modem function for data communication, and other functions (hands-free). As shown in the figure, a telephone directory exchange function processing unit 2331, a modem function processing unit 2332, and other function processing unit 2333 are provided.

  Here, in USB communication, communication is performed by establishing a logical pipe on the communication path between the USB host controller 15 and the USB function controller 24 with software. The cellular phone 2 which is a USB peripheral device forms an interface by grouping pipes, and the phone book exchange function processing unit 2331, the modem function processing unit 2332, and the other function processing unit 2333 of the USB device function processing unit 233 correspond respectively. To use the interface. The USB device driver 133 performs operations such as pipe establishment by designating the interface used for the device function to be used to the USB host driver 134 and starting up.

  The class specification description data part 232 stores information necessary for the car navigation 1 as a USB host device to communicate with each function of the USB device function processing part 233 of the mobile phone 2. The data stored here are various descriptors defined by the USB, such as a device descriptor describing information related to the entire device, and an interface descriptor describing information related to the interface.

  The device descriptor includes information such as a device class ID, a vendor ID, and a product ID representing the function of the entire device. The interface descriptor relates to the interface used by each function of the USB device function processing unit 233. Information such as an interface class ID, an interface number, and the number of pipes used.

  FIG. 4B is an example of information stored in the class specification description data part 232.

  In FIG. 4B, 405 to 410 are device descriptors, 411 to 414 are configuration descriptors indicating logical configurations in the USB device, 415 to 420 are interface descriptors, and 421 to 422 are characteristics of endpoints used in the interface. Represents an endpoint descriptor. Reference numerals 423 to 428 denote the following interface descriptors.

  Each descriptor includes “bLength” 405, 411, 415, 421, 423 indicating the data size of the descriptor, and “bDescriptorType” 406, 412, 416, 422, 424 indicating the descriptor type defined in the USB specification. Yes.

  “BDeviceClass” 407 and “bDeviceSubClass” 408 in the device descriptor respectively indicate a device class ID and a device subclass ID, and the illustrated values are values indicating vendor-specific. In addition, the device descriptor includes “idVendor” 409 in which a vendor ID as a manufacturer is set, “idProduct” 410 in which a product ID is set.

  “WTotalLength” 412 in the configuration descriptor indicates the total number of data in the configuration, and the data size of all descriptors after the configuration descriptor is set. “BNumInterfaces” 414 is the number of interfaces defined in the configuration, and indicates that there are two interfaces # 0 and # 1 in the illustrated case.

  “BInterfaceNumber” 417 and 425 in the interface descriptor indicate interface numbers. The interface numbers are assigned sequentially to the interfaces in the configuration, and “bInterfaceNumber” 417 is “00h” and 425 is “01h”. “BNumEndpoints” 418 and 426 indicate the number of endpoints used in the interface. “BInterfaceClass” 419 and 427 and “bInterfaceSubClass” 420 and 428 are for setting an interface class ID and an interface subclass ID. In the figure, the setting of a vendor specific class is described.

  Endpoint descriptors are provided before 421 and 422 and before 423, and although not shown, the maximum packet size transferred at the endpoint and the corresponding USB transfer type (bulk transfer, interrupt transfer, etc.) are described. .

  In the above configuration, the car navigation 1 needs to use the USB device driver 133 corresponding to the function to be used when using a desired function in the USB device function processing unit 233 in the mobile phone 2. Therefore, processing (device driver application method) for searching for and assigning a corresponding USB device driver from the USB device driver 133 will be described below.

  FIG. 2 is a flowchart showing an embodiment of a device driver application method according to the present invention. In the present embodiment, description will be given along processing executed by a car navigation system that is a host device.

  In S301, the USB connection detection is checked. The USB host controller 15 detects that the mobile phone 2 is connected to the car navigation 1, and notifies the USB host driver 134 that the connection is present. In S <b> 302, a descriptor acquisition request is sent, and the stored information is read from the class specification description data part 232 in the mobile phone 2. The descriptor acquisition request is one of commands defined as a standard device request in the USB standard. In S303, the descriptor read from the class specification description data part 232 is received from the mobile phone 2 and stored therein. Here, all stored descriptors are received.

  In S304, various IDs such as a device class ID and an interface class ID described in the received and stored descriptor are compared with the setting ID stored in the USB device driver identification data unit 132 installed in the car navigation 1. .

  For example, in the example of FIG. 4, (a) device class ID 401 and (b) “bDeviceClass” 407, (a) device subclass ID 402 and (b) “bDeviceSubClass” 408, (a) interface class ID 403 and ( The “bInterfaceClass” 419 of b) and the interface subclass ID 404 of (a) are all compared with the “bInterfaceSubClass” 420 of (b) to determine whether or not they all match. In this example, the class ID described in the class specification description data part 232 is unique to the vendor and therefore does not match.

  In S305, if a matching ID is found as a result of the ID comparison, it is determined that the corresponding USB device driver is present. In step S306, the function corresponding driver in the USB device driver 133 that is associated with the matched ID is registered as a device control API (Application Programming Interface), and the process ends. Here, the device control API is a function interface activated when the car navigation overall control processing unit 131 accesses the USB device driver. In S306, the function interface is activated so that the corresponding function driver found in the above process is activated. Process to set.

  If no matching ID is found in S305, it is determined that there is no corresponding USB device driver, and the process proceeds to the next step S307 and subsequent steps.

  In the processing after S307, an interface corresponding to a desired function (for example, a modem function) of the cellular phone is searched using the use function corresponding interface search driver 1333. On the mobile phone 2 side, an interface is assigned to each function stored in the USB device function processing unit 233. When the class ID is a vendor-specific ID, which interface number is assigned to which function, I do not know on the car navigation 1 side.

  Therefore, the used function compatible interface search driver 1333 establishes a pipe for each interface number included in the descriptor information stored in S303 processing, sends a modem control command, and assigns a modem function depending on whether there is a response. The interface number is searched.

  In S307, the number of interfaces set in the mobile phone 2, that is, the maximum interface number m is detected from the received descriptor information. In S308, the initial value of the interface number to be searched is set to n = 0, for example.

  In S309, a pipe with the interface number n (initial value = 0) is established. In S310, a modem control command (specifically, an AT command or the like) is transmitted. In S311, a response waiting timer for the transmitted modem control command is set.

  In S312, it is determined whether there is a normal command response code (for example, “OK”) within the set time. If a normal command response is obtained, the interface number n is stored in the memory 13 as a modem function interface in S313. That is, when a modem control command is transmitted and a predetermined response is received, it is determined that the interface number n is an interface that can be used for the modem function.

  On the other hand, if a normal command response cannot be obtained (timeout), it is determined that the interface is not usable as a modem function, and the pipe having the interface number n is deleted in S314. In step S315, the interface number n is updated to n + 1. For the updated interface number, the process returns to S309 again, and pipe establishment and command response are repeated. If the interface number n exceeds the maximum value m in S316, the process is terminated.

  FIG. 3 is a diagram showing a command sequence in the flowchart of FIG. An interface to which a modem function is assigned is searched between the car navigation 1 and the mobile phone 2. Here, in the cellular phone 2, for example, the interface number 0 (IF # 0) is stored in the telephone book exchange function processing unit 2331, the interface number 1 (IF # 1) is stored in the modem function processing unit 2332, and the other function processing unit 2333. Is assigned interface number 2 (IF # 2).

  The used function corresponding interface search driver 1333 first establishes a pipe with interface number 0 and sends a modem control command (AT). However, since interface number 0 is assigned to the telephone directory exchange function processing unit 2331, a response to this command cannot be obtained. Next, a pipe with interface number 1 is established and a modem control command is transmitted. Since interface number 1 is assigned to the modem function processing unit 2332, a pipe is established with the modem function processing unit 2332, and a response code (OK) to the command is returned. Accordingly, it is determined that the interface number 1 is a modem function interface. In this way, the interface number 1 that can be used for the modem function is stored in the memory 13 (S313).

  Thereafter, when the car navigation overall control processing unit 131 designates the modem function and operates the USB device driver 133, the USB device driver 133 reads the interface number stored in the memory 13 for the modem function. By operating the USB host driver 134 via this, a pipe is established with the modem function processing unit 2332 in the mobile phone 2 and communication is possible.

  The used function compatible interface search driver 1333 is not limited to the modem function, and can be applied to other functions of the mobile phone.

  As described above, a device driver corresponding to identification information such as a mobile phone class ID may not be found for a mobile phone connected to a car navigation system. In such a case, according to the present embodiment, it is possible to search for a communicable interface by transmitting a predetermined command from the car navigation system to the mobile phone. Since the desired function of the mobile phone can be used via the searched interface, the function of the mobile phone that can be used in the car navigation system can be expanded.

  Therefore, when data communication is performed by connecting a mobile phone to a car navigation system, even if the class specification of the connected mobile phone is different for each vendor, the modem function of more vendors' mobile phones can be used. As a result, the convenience of car navigation systems can be improved.

  In this embodiment, since no new correspondence is required on the mobile phone side, the number of mobile phones that can be used in the car navigation system can be expanded, and it is not necessary to install a device driver on the car navigation side later. It is effective in embedded systems.

  In the above embodiment, the case where the host device is a car navigation and the peripheral device is a mobile phone is described as an example. However, the present invention is not limited to this, and the present invention is applicable to a system and a device that communicate by connecting the host device and the peripheral device via USB. Needless to say, you can.

  That is, according to the present invention, even if there is no device driver corresponding to the class specification of the connected peripheral device in the host device, if the device can be used functionally, a new device driver is installed. Peripheral devices can be used without having to

  Further, since it can be implemented only by the device driver on the host device side, the peripheral device may remain as it is, and the burden on the peripheral device side such as an increase in cost required for the memory is not increased.

The block diagram which shows one Example of the USB communication system using the device driver application method by this invention. The flowchart figure which shows one Example of the device driver application method by this invention. The figure which shows the command sequence in the flowchart of FIG. The figure which shows an example of the information stored in the USB device driver identification data part 132 and the class specification description data part 232.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Car navigation (host device), 2 ... Cell-phone (peripheral device), 10 ... USB cable, 11 ... Car navigation whole control part, 12 ... Car navigation side CPU, 13 ... Car navigation side memory, 131 ... Car navigation whole control processing part, 132 ... USB device driver identification data part, 133 ... USB device driver, 1331 ... modem function compatible driver, 1332 ... other function compatible driver, 1333 ... used function compatible interface search driver, 134 ... USB host driver, 14 ... navi peripheral I / F part, 15 ... USB host controller, 21 ... mobile overall control part, 22 ... mobile phone side CPU, 23 ... mobile phone side memory, 231 ... mobile phone overall control part, 232 ... class specification description data part, 233 ... USB device Function processing unit, 2331 ... Phonebook exchange function processing unit 2332 ... modem function processing unit, 2333 ... Other function processing unit, 234 ... USB function driver, 24 ... USB function controller.

Claims (5)

A device driver application method for applying a device driver for using a function provided in a peripheral device in a host device connected to the peripheral device,
The peripheral device has class specification description data that describes the type of function provided and information of the logical interface assigned to each function.
When the host device does not have a device driver for using the functions of the peripheral device,
Obtain information of each logical interface described in the class specification description data from the peripheral device,
For each logical interface acquired from the peripheral device, a predetermined command handled by a desired function is sent,
Search for a logical interface that can obtain a predetermined response from the peripheral device in response to the command,
A method of applying a device driver, comprising using a function of the peripheral device via the retrieved logical interface. The device driver application method according to claim 1,
The peripheral device is provided with a modem function, sends an AT command for modem control as the predetermined command, and retrieves a logical interface used for the modem function by obtaining a predetermined response code for the command. Device driver application method. The device driver application method according to claim 1 or 2,
The device driver application method, wherein the host device is a car navigation and the peripheral device is a mobile phone. In a host device that connects peripheral devices and uses the functions of the peripheral devices,
The peripheral device has class specification description data that describes the type of function provided and information of the logical interface assigned to each function.
Class specification acquisition means for acquiring information of each logical interface described in the class specification description data from the peripheral device,
For each acquired logical interface, an interface search driver that sends a predetermined command handled by a desired function and searches for a logical interface that can obtain a predetermined response is provided.
When the host device does not have a device driver for using the function provided by the peripheral device, the function provided by the peripheral device is used via the logical interface searched by the interface search driver. A host device. The host device according to claim 4, wherein
The peripheral device has a modem function, and the interface search driver sends an AT command for modem control as a predetermined command, and searches for a logical interface used for the modem function by obtaining a predetermined response code for the command. And a host device.

Images