JP2011186770A - Apparatus, method and system for controlling device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a means which can control respective devices without performing physical connection/disconnection of a connection cable even when a plurality of devices of the same model are connected. <P>SOLUTION: When a plurality of devices of the same model are connected to a device control apparatus, a data source manager obtains individual identification information of each of the devices of the same model, generates a device display name of each device from the individual identification information and registers the individual identification information and the device display name in a table by associating them with each other. Further, the data source manager transmits a table of devices composed of the device display names of respective devices to an application. When a device of the same model is selected by the application, the data source manager specifies the selected device by referring to the table based on the device display name and unloads a device driver of another device of the same model as the selected device. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

The present invention relates to an apparatus, a method, and a device control system having a function of controlling a device.

Imaging devices (scanners, whiteboards, etc.) that are used by connecting to a client PC are standardized by the TWAIN standard. Since this TWAIN standard device does not consider the control of multiple units from the same PC, serial numbers, etc. In many cases, information for identifying the same device / separate body is not described on the device. Therefore, due to limitations of the STI (Still Image) service of the operating system (hereinafter referred to as OS), even when multiple devices of the same model are connected, the same device / separate device cannot be identified, and only one of them can be identified. Could not use (recognize).

In order to solve such a problem, in response to the USB device receiving a USB device information request command from the USB host, a vendor ID stored in the storage means and a code of an arbitrary number of digits such as a DIP switch There is disclosed a USB system that transmits a product ID of a USB device generated from a code set by a code setting means capable of manually setting to a USB host (see Patent Document 1).

JP 2006-134093 A

Certainly, the USB system of Patent Document 1 generates a product ID that identifies and identifies the type of device in the USB device, and transmits it to the USB host, so that the USB host connects multiple devices of the same model. However, the same device / separate body of the device can be identified.

However, the USB system disclosed in Patent Document 1 needs to include a code setting unit (dip switch) for generating a product ID for identifying and identifying the type of device in the USB device. There is a problem that you have to operate with.

In addition, even if multiple devices of the same model are connected, even if the same device / separate body of the device can be identified on the OS, the same device / separate body of the device cannot be identified on the TWAIN standard application. There is also a problem that devices of the same model cannot be displayed in an identifiable manner, and the devices cannot be switched and used.

Further, the USB system of Patent Document 1 does not consider the case of using a device connected to a network such as a LAN (Local Area Network). Thus, it is also a problem to identify the same device / separate body of TWAIN standard compliant devices.

In addition, since a device compatible with the TWAIN standard is used, it is necessary to customize a TWAIN standard-compliant application provided by each device vendor and a TWAIN standard-compliant device driver.

In view of the above-described problems, the present invention acquires and manages individual identification information for each device of the same model, even when a plurality of devices of the same model are connected in the client PC, and each device of the same model device By creating a display name and controlling the validity / invalidity of the connection with each device of the same model, even when using an application compliant with the TWAIN standard, setting by connecting / disconnecting the connection cable physically, using a dip switch, etc. It is an object to perform control so that a plurality of devices can be used without switching.

Even when multiple devices of the same model are connected to the network via a device server, each device can be separated from the TWAIN standard application of the client PC by adding unique information to the device in the device server. It is intended to control the device so that it can be identified as an individual and can be used by switching a plurality of devices.

In addition, by customizing (changing) only the data source manager of the client PC, multiple TWAIN standard compatible applications and multiple TWAIN standard compatible device drivers provided by each device vendor can be changed without changing the TWAIN standard compatible application. It is intended to allow devices to identify and use the same equipment / separate bodies.

In order to solve the above-described problem, the device control apparatus according to claim 1 is a device control apparatus that operates the device via the application by controlling an interface between the application and the device. Receiving a device list display command from the application, and receiving device information from the currently connected device in response to receiving the device list display command by the device list display command receiving unit. Device information acquisition means to be acquired, device type determination means for determining whether or not a device of the same model is connected based on the device information acquired by the device information acquisition means, and device of the same model by the same model determination means Is determined to be connected, A device display name generation unit that acquires individual identification information of each device of one model and generates a device display name for enabling identification of a device corresponding to the acquired individual identification information; and the device display name generation unit Table registration means for registering the generated device display name in the table in association with the individual identification information, and for devices connected to the same model, describe the device display name registered in the table. For a device that is not connected, a device list that describes a device display name included in the device information is created, and a device list transmitting unit that transmits the device list to the application; and a device selection command is received from the application And a device selection command receiving means for receiving the device selection command. If the device selection command received by the means includes a device display name registered in the table, a device driver unload device that unloads a device driver of the same model other than the device that matches the device display name And means.

In order to solve the above problem, a device control method according to claim 5 is a device control method for operating the device via the application by controlling an interface between the application and the device. A device list display command receiving step for receiving a device list display command from the application, and a device from a currently connected device in response to receiving the device list display command in the device list display command receiving step. A device information acquisition step for acquiring information, a same model determination step for determining whether a device of the same model is connected based on the device information acquired in the device information acquisition step, and a same model in the same model determination step Devices connected A device display name generating step for acquiring individual identification information of each device of the same model, and generating a device display name for enabling identification of a device corresponding to the acquired individual identification information. A table registration step of registering the device display name generated in the device display name generation step in the table in association with the individual identification information, and devices registered in the table for devices connected to the same model A device list transmission step for creating a device list describing a device display name included in the device information for a device to which a display name is described and the same model is not connected, and transmitting the device list to the application; Receive a device selection command from the application. If the device display name registered in the table is included in the device selection command received in the device selection command receiving step and the device selection command receiving step, the same model other than the device matching the device display name A device driver unloading step of unloading a device driver of the device.

In order to solve the above problem, the device control system according to claim 9 controls the device via the device, a device server locally connected to the device, and the device server connected to the network. A device control system comprising: a device control apparatus configured to: a first device information acquisition unit configured to acquire device information from the device; and the device information acquired by the first device information acquisition unit. Any one of the unique information adding means for adding the address information of the device server itself, the device information acquired by the first device information acquiring means, or the device information to which the address information is added by the unique information adding means As the device information of the device Device information transmitting means for transmitting, wherein the device control apparatus receives a device list display command receiving means for receiving a device list display command from the application, and the device list display command receiving means receives the device list display command. Accordingly, devices of the same model are connected by the second device information acquisition unit that acquires the device information of the device from the device server and the device information acquired by the second device information acquisition unit. If the same model determination means and the same model determination means determine that the same model device is connected, the individual identification information of each device of the same model is acquired, and the acquired individual Generates a device display name that enables the device to be identified from the identification information. Device display name generation means, table registration means for registering the device display name generated by the device display name generation means in a table in association with the individual identification information, and for devices to which the same model is connected Describe the device display name registered in the table, create a device list describing the device display name included in the device information for devices that are not connected to the same model, and send the device list to the application A device list transmitting means, a device selection instruction receiving means for receiving a device selection instruction from the application, and a device display name registered in the table in the device selection instruction received by the device selection instruction receiving means. Device that matches the device display name. Device driver unloading means for unloading a device driver of a device of the same model other than a chair.

According to the present invention, even when a plurality of devices of the same model are connected to the client PC, individual identification information is acquired and managed for each device of the same model, and a device display name for each device of the same model is generated. By controlling the validity / invalidity of connections with devices of the same model, even when using applications that comply with the TWAIN standard, multiple settings can be made without physically connecting / disconnecting connection cables or setting with dip switches. The device can be switched and used.

In addition, according to the present invention, even when a plurality of devices of the same model are connected to a network via a device server, by adding a unique information to the device in the device server, an application compatible with the TWAIN standard of the client PC Thus, each device can be identified as a separate body, and a plurality of devices can be switched and used.

In addition, by customizing (changing) only the data source manager of the client PC, multiple TWAIN standard-compliant applications and TWAIN standard-compliant device drivers provided by various device vendors can be changed without changing the TWAIN standard-compliant application. Devices can be used to identify and use the same equipment / separate bodies.

1 is a diagram illustrating a schematic configuration of a device control system according to a first embodiment. 2 is a block diagram illustrating an internal configuration of a client PC 100. FIG. 7 is an example of the same model device information table stored in the data source manager 111 of the client PC 100 according to the first embodiment. 4 is a flowchart for explaining control at the time of executing scan in the client PC 100. FIG. 6 is a diagram illustrating a schematic configuration of a device control system according to a second embodiment. 14 is an example of a user information table stored in the data source manager 111 of the client PC 100 according to the second embodiment. FIG. 10 is a diagram illustrating a schematic configuration of a device control system according to a third embodiment. FIG. 10 is a block diagram illustrating an internal configuration of a device server 600 according to a third embodiment. 12 is a flowchart for explaining control when a device 200 is connected in a device server 600 according to a third embodiment. 14 is an example of the same model device information table stored in the data source manager 111 of the client PC 100 according to the third embodiment. FIG. 10 is a diagram illustrating a device list according to a third embodiment.

Hereinafter, embodiments of the present invention will be described in detail.

An embodiment according to Example 1 will be described.

<1. Device control system configuration>
FIG. 1 is a schematic configuration of a device control system for realizing the present invention, which includes a client PC 100 and devices 200 (200A, 200B).

In this device control system, the client PC 100 and the device 200 are connected by a connection cable 300 compliant with an interface such as USB (Universal Serial Bus) or IEEE1394.

Next, each device constituting the device control system of FIG. 1 will be described in order.

<2. Configuration of Client PC 100>
First, the hardware configuration and software configuration of the client PC (device control apparatus) 100 will be described with reference to FIG.

The client PC 100 includes a CPU 101, an input unit 102, a display unit 103, a memory 104, a communication unit 105, a local I / F 106, an external storage unit 107, and the like, which are connected via an internal bus 112.

The CPU 101 is a central processing control unit, and controls the client PC 100 as a whole by executing a predetermined program stored in the memory 104 or the external storage unit 107.

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

The display unit 103 is a display that displays various screens, and is built in or externally connected to the client PC 100.

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

The communication unit 105 is an interface for performing transmission / reception and communication control by a network packet corresponding to a network such as a wired network such as Ethernet (registered trademark) or a wireless network such as IEEE802.11a or IEEE802.11g. By performing data communication with the outside, data can be transmitted / received from the client PC 100.

The local I / F 106 is a transmission / reception interface compliant with, for example, a USB (Universal Serial Bus) specification, and is used for connection to the device 200.

The external storage unit 107 stores various software programs such as the OS 108, the TWAIN application program 109, the TWAIN device driver 110, and the data source manager 111.

These software programs stored in the external storage unit 107 are read onto the memory 104 and executed under the control of the CPU 101.

The OS 108 is an operating system. In the present invention, when it is detected that the device 200 is connected via the local I / F 106, a function unit for acquiring device information of the connected device 200 and a device for identifying the device from the device information of the device 200 It is characterized by playing a role as a functional unit that generates individual identification information.

The device information identifies a vendor ID (VID) assigned to each manufacturer that manufactured the device to identify the manufacturer, a product ID (PID) assigned to each model to identify the model, and an individual device. Therefore, it is composed of a serial number assigned to each device.

The individual identification information is an instance ID composed of a vendor ID, a product ID, and connection port information of the client PC 100, a device ID stored in the registry of the OS 108, and the like, but is not limited thereto. Further, a combination of these may be used.

The connection port information of the client PC 100 is information for identifying the connection port of the client PC 100. For example, the USB port number of the client PC 100 or the IEEE 1394 port number may be used, but the present invention is not limited to these.

In the individual identification information, the instance ID has been described as being configured of the vendor ID and product ID of the device 200 and the connection port information of the client PC 100. However, the present invention is not limited to this, and the vendor ID, product ID, And it may consist of a serial number.

Now, details of the TWAIN application program 109, the TWAIN device driver 110, and the data source manager 111 will be described.

The TWAIN application program 109 is an application program corresponding to the TWAIN standard, and operates on the OS 108. Selection information of the device 200 acquired by the user via the input unit 102 and setting information at the time of service execution such as scanning can be set, and the service processing by the device 200 is controlled and the acquired image data is stored. It is a program that can be edited.

The TWAIN device driver 110 is software that generates an instruction or data to be transmitted to the device 200 via the local I / F 106 and controls the device 200 to acquire data. As described above, when the connection of the device 200 is detected by the OS 108, the TWAIN device driver 110 of each device 200 is individually loaded.

The data source manager 111 is software that exchanges data between the TWAIN device driver 110 and the TWAIN application program 109. In addition to this, a function for acquiring device information of the device 200 currently connected to the client PC 100 from the OS 108 and information (hereinafter referred to as a device list) on the device 200 describing the device display name are created and stored in the TWAIN application program 109. It also has a function to transmit to.

<3. Configuration of Device 200>
Next, the configuration of the device 200 will be described. The device 200 (device 200A, device 200B) is a general-purpose input / output device that supports the TWAIN standard and has a local interface. For example, it is a single function peripheral (SFP) such as a scanner, or a multifunction peripheral (MFP) having a print function, a copy function, a storage function, etc. in addition to a scanner function. However, it is not limited to these, and another device may be used.

<4. Details of Data Source Manager 111>
Next, the data source manager 111 of the client PC 100, which is a feature of the present invention, will be described in detail.

When receiving a device list display command from the TWAIN application program 109, the data source manager 111 determines whether devices of the same model are connected based on the device information acquired from the device 200. When the same model device 200 is connected, the individual identification information of each device of the same model is acquired from the OS 108, and a device display name that can identify each device of the same model is generated from this individual identification information. The name is associated with the individual identification information and registered in the same model device information table.

The same model device information table is a table in which information related to devices of the same model is registered. At least the individual identification information acquired from the OS 108 by the data source manager 111 and the device display name that can identify each device of the same model. Are registered in association with each other. It is referred to when determining whether or not a device 200 of the same model as the device 200 selected by the TWAIN application program 109 is connected.

FIG. 3 shows an example of the same model device information table composed of the device model name, device display name, and instance ID. In this example, there is shown a case where there is only information on one model of the device a200A and the device b200B which are devices of the same model. In addition, when devices of the same model with different models from the device a200A and the device b200B are connected, these pieces of information are also registered in the table.

The instance ID includes a vendor ID, a product ID, and connection port information described in the device information acquired from the OS 108. In the case of the device a200A, the vendor ID is “VID — 1234”, the product ID is “PID — 1234”, and the connection port information is “1 & 11111111 & 1 & 1”.

In this case, since the connection port information “1 & 1111111 & 1 & 1” of the device a200A and the connection port information “1 & 11111111 & 1 & 2” of the device b200B are different, the device a200A and the device b200B can be identified.

The device display name is generated based on the individual identification information acquired from the OS 108 so that the data source manager 111 displays each device of the same model in an identifiable manner. The device display name illustrated in FIG. 3 includes a serial number for individually distinguishing devices of the same model as the device model name, the device display name of the device a200A is “CIS-100-1”, and the device b200B The device display name is “CIS-100-2”.

In FIG. 3, the device display name generated by the data source manager 111 is illustrated as information associated with the individual identification information. However, the present invention is not limited to this, and the MAC address or other information that is device-specific information However, any device that can uniquely identify (identify) a device may be used.

Further, the data source manager 111 creates a device list of devices connected to the client PC 100 and transmits it to the TWAIN application program 109.

In this device list, the device display name registered in the same model device information table is described for devices connected to the same model, and the device display included in the device information for devices not connected to the same model Name is described.

Further, when the data source manager 111 receives the device selection command of the device 200 selected by the TWAIN application program 109 by the user operating the input unit 102, the data source manager 111 refers to the same model device information table and is included in the received device selection command. When the device display name to be registered is registered in the same model device information table, the connection with the selected device 200 is validated.

Specifically, when the device 200 having the same model is selected by the TWAIN application program 109 among the TWAIN device drivers 110 loaded when the connection of the device 200 is detected, the connection with the selected device 200 is performed. Only the connection is validated, and the TWAIN device driver 110 of the other device 200 of the same model is unloaded, thereby invalidating the connection with the other device 200 of the same model. When the data transmission / reception with the device 200 of the same model whose connection has been validated is completed, the unloaded TWAIN device driver 110 is loaded again.

<5. Processing at the time of scan execution in the client PC 100>
From here, the control at the time of execution of scanning in the client PC 100 will be described with reference to the flow of FIG.

In the present embodiment, a case will be described in which the device a200A and the device b200B connected to the client PC 100 are devices of the same model, the device a200A is selected, and scanning is executed.

First, the user starts the TWAIN application program 109 by operating the input unit 102 (step S401).

The OS 108 acquires device information for identifying the device 200 from the device a 200A and the device b 200B via the local I / F 106, and stores the device information in the memory 104 (step S402).

Subsequently, the data source manager 111 determines whether the device 200 of the same model is connected to the client PC 100 from the device information acquired in step S402 (step S403).

In step S403, since the device a200A and the device b200B are devices of the same model (Yes in step S403), the process proceeds to step S404. Next, the data source manager 111 acquires the individual identification information generated by the OS 108, generates a device display name (step S404), and sets the information of the corresponding device 200 (device display name, individual identification information) to the same model device information. Register in the table (step S405).

The data source manager 111 creates a device list from the device display names registered in the same model device information table and transmits the device list to the TWAIN application program 109 (step S406).

Based on the device list received from the data source manager 111, the TWAIN application program 109 generates a graphical user interface (GUI) screen for the user to select a device 200 to be used from among device selection candidates. The information is displayed on the display unit 103 (step S407).

On this GUI screen, a device a200A and a device b200B connected to the client PC 100 are displayed in an identifiable manner. The user operates the input unit 102 to select the device a200A that performs the scan from the list of device selection candidates displayed on the display unit 103 (step S408). At this time, the selected device a200A is displayed on the display unit 103 while being distinguished from other devices (device b200B).

When the data source manager 111 receives a device selection command including information on the device selected from the TWAIN application program 109 based on the selection result in step S408, the data source manager 111 refers to the device display name registered in the same model device information table. Then, it is determined whether there is a device of the same model as the selected device a200A (step S409).

Since the selected device a200A and device b200B are devices of the same model, the determination result in step S409 is Yes, and the process proceeds to step S410. Then, the data source manager 111 unloads the TWAIN device driver 110 of the device b200B (step S410). As a result, only the connection with the device a200A is enabled, and the connection with the device b200B is disabled.

The TWAIN device driver 110 of the device a200A transmits a scan execution request to the device a200A and acquires scanned image data (step S411). When the device a200A continues to scan, the process of step S411 is repeatedly executed.

When the acquisition of the scan image data from the device a200A is completed, the data source manager 111 disconnects the connection with the device a200A and ends the process. Here, the TWAIN device driver 110 of the device b200B unloaded in step S410 is loaded again (step S412).

After the scanning by the device a200A is completed, when the user operates the input unit 102 to select the termination of the TWAIN application program 109 (step S413), the data source manager 111 stores information (data) in the same model device information table. It is determined whether there is any (step S414). If there is information in the same model device information table (Yes in step S414), the same model device information table is initialized (step S415), and the process ends.

Here, since the device a200A and the device b200B are devices of the same model, since the information is registered in the same model device information table, the same model device information table is initialized.

The initialization process of the same model device information table in step S415 is to delete all information (device display name and individual identification information) registered in the same model device information table. If there is information on another model other than the device a200A and the device b200B in the same model device information table, the information is also deleted.

In addition, after executing the process of step S412, when performing a scan with a device different from the selected device without ending the TWAIN application program 109, the process returns to step S408, and the process from step S408 to step S412 is performed again. It can be realized by repeating.

Note that, when the device a200A and the device b200B are not the same model, the determination results of step S403 and step S409 described above are different, and this portion will be described.

In step S403, the data source manager 111 determines that the same type of device 200 is not connected, the determination result is No, and the process proceeds to step S406.

In step S409, since there is no device of the same model as the selected device a200A, the determination result is No, the process proceeds to step S416, and a scan execution request is transmitted to the device a200A in the same manner as in step S411. The acquired image data is acquired, and the process proceeds to step S413.

In this flow, initialization processing of the same model device information table is not performed after the TWAIN application program 109 is finished, and when the scanning is finished with the selected device a200A, the TWAIN device driver 110 of the device b200B is loaded again. It may be performed at the same time as or immediately after.

As described above, according to the device control system of the first embodiment, only the connection with the device 200 selected by the TWAIN application program 109 is enabled by the data source manager 111 and the same model other than the selected device 200 is selected. By unloading the TWAIN device driver 110 of the device 200, a plurality of devices 200 can be switched and used without physically removing and inserting the interface.

In addition to the method of selecting the device 200 to be used from the device selection candidates displayed on the display unit 103 using the above-described GUI screen, an input device (infrared sensor, The state change of the device 200 is detected by a push switch or the like, and the client PC 100 is notified of the state change, so that the client PC 100 selects the device 200 in which the state change has occurred in response to the state change notification. May be.

An embodiment according to Example 2 will be described.

<6. Selection of Device 200 Using Card Reader>
In the second embodiment, an embodiment in which the device 200 to be used is selected by holding the card over the card reader 400 connected to the client PC 100 will be described.

Note that the configuration and flow of the first embodiment described with reference to FIGS. 2 to 4 can be similarly applied to the second embodiment, and thus detailed description thereof will be omitted, and only differences will be described.

FIG. 5 is a schematic configuration of a device control system according to the second embodiment, which includes a client PC 100, a device 200 (200A, 200B), and a card reader 400.

The card reader 400 is connected to the client PC 100 via the connection cable 300 and has a function of acquiring user information such as a card ID and a user ID recorded on the card. Note that the card reader 400 may be configured to be built in the client PC 100.

In the present embodiment, description will be made using the technology of a non-contact IC card that communicates between the cards when the card is brought close to (over the card reader 400). For example, there is FeliCa (registered trademark) as this non-contact IC card technology. It is not limited to this technology, and other non-contact types such as a close contact type (ISO / IEC10536; communication distance of 2 mm or less) and a proximity type (ISO / IEC14443; communication distance of 10 cm or less) established as an international standard. A technique using a method or a contact method (such as ISO / IEC7816) may be used. Instead of using the card reader 400, the card and the client PC 100 can be directly connected to exchange information.

The data source manager 111 of the client PC 100 further stores a user information table in addition to the same model device information table shown in FIG. As illustrated in FIG. 6, the user information table is a table indicating the correspondence between user information and usable (connectable) devices for each user. Note that the same model device information table information and the user information table information shown in FIG. 3 may be stored as one table. Such a user information table associates a user with a device 200 that can be used by the user.

In this embodiment, the device a200A and the device b200B connected to the client PC 100 are devices of the same model, and the user A selects the device a200A by bringing the card close to (holds over) the card reader 400, and executes scanning. explain.

In the client PC 100, when the card reader 400 is connected, the OS 108 activates a device driver (not shown) and an application program (not shown) that control the card reader 400.

Then, the control at the time of scan execution in the client PC 100 according to the second embodiment will be described with reference to the flow of FIG.

In the present embodiment, the processes in steps S401 to S407 are the same as those in the first embodiment, and thus description thereof is omitted.

If it is detected in step S408 that the card associated with the user A is held over the card reader 400, the device a200A is selected (step S408).

Specifically, when a card associated with the user A is held over the card reader 400, a device driver (not shown) that controls the card reader 400 acquires the user information of the user A from the card, and the data source manager 111 Send to. The data source manager 111 refers to the same model device information table as the user information table based on the user information of the user A received from the device driver, and identifies the device a200A that can be used by the user A. The selection is complete.

Subsequent processing is the same as Step S409 to Step S416 of the first embodiment, and a description thereof will be omitted. This completes the execution of the scan according to the second embodiment.

As described above, according to the device control system of the second embodiment, the user uses the card reader 400 connected to the client PC 100 to select the device 200 to be used by the user. A plurality of devices 200 can be switched and used without being inserted or removed.

An embodiment according to Example 3 will be described.

<7. Configuration of Device Control System According to Embodiment 3>
In the first embodiment and the second embodiment described above, the mode of controlling the device 200 locally connected to the client PC 100 has been described. However, in the third embodiment, the device 200 locally connected to the client PC 100 and the device 200 connected to the network. An embodiment will be described in which each device is controlled from the client PC 100 in a system in which a device 200 locally connected to a network-connected device server is mixed.

Note that the configuration and flow of the first embodiment described with reference to FIGS. 2 to 4 can be similarly applied to the third embodiment, and thus detailed description thereof will be omitted, and only differences will be described.

FIG. 9 illustrates a schematic configuration of a device control system according to the third embodiment, which includes a client PC 100, a device 200 (200A, 200B, 200C, 200D, 200E, 200F), and a device server 600 (600A, 600B). In the following description, it is assumed that the device a200A, the device b200B, the device c200C, and the device e200E are devices of the same model, and that the device d200D and the device f200F are different models from the other devices 200, respectively.

In this device control system, the device a 200A and the device b 200B are locally connected to the client PC 100 via the connection cable, and the device c 200C and the device d 200D are locally connected to the device server a 600A and the device server b 600B via the connection cable 300, respectively. Yes. The device e200E and the device f200F have a communication unit (not shown) equivalent to the communication unit 105 included in the client PC 100 described in the first embodiment, and are connected to the client PC 100 via a wired or wireless network 500. .

First, the client PC 100 will be described, but only differences from the first embodiment will be described.

In this embodiment, devices (device a200A, device b200B) locally connected to the client PC 100, devices (device c200C, device d200D) connected via the device server 600, and devices (device e200E, device f200F) connected via the network. ) Are mixed. In order to identify and control these devices, it is necessary to acquire device information different from those in the first and second embodiments. Hereinafter, device information acquired by the OS 108 of the client PC 100 in this embodiment will be described.

The OS 108 acquires information including at least a vendor ID and a product ID as device information of the device 200 from the device a200A and the device b200B, as in the first embodiment. From the device e200E and the device f200F, information obtained by adding the address information (for example, IP address or MAC address) of the device 200 itself to information equivalent to the device a200A and the device b200B is acquired as the device information of the device 200. From the device server a600A and the device server b600B, device information (equivalent to information acquired from the device a200A and the device b200B) acquired from the device 200 (device c200C or device d200D) locally connected to the device server 600 is stored in the device server 600. What added the address information is acquired as device information of the device 200.

The address information included in the device e200E, the device f200F, the device server a600A, and the device server b600B is information for identifying the device 200 or the device server 600. For example, the IP address or MAC address of the device 200 or the device server 600 is not limited to these. Furthermore, it may be a combination of these pieces of information.

FIG. 10 is an example of the same model device information table composed of the device model name, device display name, and instance ID. In this example, the device a200A, the device b200B, the device c200C, and the device e200E are devices of the same model.

The instance ID includes a vendor ID, product ID, connection port information, or address information described in device information acquired from the OS 108. In the case of the device a200A, the vendor ID is “VID — 1234”, the product ID is “PID — 1234”, the connection port information is “1 & 11111111 & 1 & 1”, and in the device c200C, the vendor ID is “VID — 1234”, the product ID is “PID — 1234”, and the address information Is “192.168.1.11”.

In this case, the connection port information “1 & 1111111 & 1 & 1” of the device a200A, the connection port information “1 & 11111111 & 1 & 2” of the device b200B, the address information “192.168.1.11” of the device c200C, and the address information “192.168” of the device e200E. .3.33 ”makes it possible to identify the device a200A, the device b200B, the device c200C, and the device e200E even if devices having different connection forms are mixed in the system.

The device display name is generated based on the individual identification information acquired from the OS 108 so that the data source manager 111 displays each device of the same model in an identifiable manner. The device display name illustrated in FIG. 10 includes serial numbers for individually identifying devices of the same model as the device model name. The device display name of the device a200A is “CIS-100-1” and the device of the device b200B. The display name is “CIS-100-2”, the device display name of the device c200C is “CIS-100-3”, and the device display name of the device e200E is “CIS-100-4”.

<8. Configuration of Device Server 600>
Next, the hardware configuration and software configuration of the device server 600 in the device control system according to the third embodiment will be described with reference to FIG.

The device server 600 includes a CPU 601, a memory 602, a communication unit 603, a local I / F 604, an external storage unit 605, and the like, which are connected by an internal bus 606.

Since the CPU 601, the memory 602, the communication unit 603, the local I / F 604, and the internal bus 606 are the same as those in the client PC 100 described above, detailed description thereof is omitted.

The external storage unit 605 is a software function unit including a communication control unit 607 and a device control unit 608.

The communication control unit 607 is a functional unit connected to the client PC 100 via the communication unit 603 and the network 500, a function for transmitting device information to the client PC 100, and data between the client PC 100 via the network 500. It has a function to send and receive.

The device control unit 608 is a functional unit connected to the device 200 via the local I / F 604, a function for acquiring device information from the locally connected device 200, and a device included in the control command received from the client PC 100 Based on the information, the client PC 100 has a function of specifying the device 200 that requests data transmission / reception and controlling the device 200 via the local I / F 604.

<9. Processing when Device 200 is Connected to Device Server 600>
Next, processing executed on the device server 600 when the device 200 is locally connected to the device server 600 will be described with reference to the flowchart of FIG.

When the device 200 is locally connected, the device server 600 starts processing according to this flow.

First, the device control unit 608 acquires device information for identifying the device 200 from the device 200 via the local I / F 604, and stores it in the memory 602 (step S901).

Thereafter, the communication control unit 607 stands by until a device information inquiry is received from the client PC 100 (No in step S902). The inquiry from the client PC 100 is performed using a protocol such as UDP (User Datagram Protocol).

The communication control unit 607 notifies the device control unit 608 that there is an inquiry about device information from the client PC 100 (Yes in step S902), and the device control unit 608 device information of the device 200 locally connected to the device server 600. When the communication control unit 607 is identified, the communication control unit 607 transmits the device information of the device 200 identified through the communication unit 603 added to its own address information to the client PC 100 as the device information of the device 200, and ends the processing. (Step S903). Accordingly, the client PC 100 can acquire the device information of the device 200 locally connected to the device server 600 and the address information of the device server 600.

Note that the client PC 100 may acquire device information by a notification from the device server 600 without making an inquiry.

Also, in the device 200 connected to the network (device e200E, device f200F), similarly to the device server 600, the client PC 100 may acquire the device information from the device 200 connected to the network by making an inquiry. The device information may be acquired by a notification from the network-connected device 200 without the PC 100 making an inquiry.

<10. Processing at the Time of Scan Execution in Client PC 100 According to Embodiment 3>
Next, control during scan execution in the client PC 100 according to the third embodiment will be described using the flow of FIG. 4 as in the first and second embodiments.

In the present embodiment, a case will be described in which the device a200A, the device b200B, the device c200C, and the device e200E are devices of the same model, the device c200C is selected, and scanning is executed.

First, the user starts the TWAIN application program 109 by operating the input unit 102 (step S401).

The OS 108 acquires device information from the device a200A, the device b200B, the device c200C, the device e200E, the device server a600A, and the device server b600B, and stores the device information in the memory 104 (step S402).

Subsequently, the data source manager 111 determines whether devices of the same model are connected to the system from the device information acquired in step S402 (step S403).

In step S403, since the device a200A, the device b200B, the device c200C, and the device e200E are devices of the same model, the determination result is Yes and the process proceeds to step S404. Next, the data source manager 111 acquires the individual identification information generated by the OS 108, generates a device display name (step S404), and sets the information of the corresponding device 200 (device display name, individual identification information) to the same model device information. Register in the table (step S405).

The data source manager 111 creates a device list from the device display name registered in the same model device information table and the device display name included in the device information, and transmits it to the TWAIN application program 109 (step S406).

FIG. 11 is an example of a device list including device display names of the devices a200A to f200F.

This device list shows device display names (CIS-100-1, CIS-) registered in the same model device information table for devices (device a200A, device b200B, device c200C, and device e200E) to which the same model is connected. 100-2, CIS-100-3, CIS-100-4), and devices not connected to the same model (device d200D, device f200F) include device display names (CIS-200) included in the device information. , CIS-300).

Based on the device list received from the data source manager 111, the TWAIN application program 109 generates a graphical user interface (GUI) screen for the user to select a device 200 to be used from among device selection candidates. The information is displayed on the display unit 103 (step S407).

On this GUI screen, the devices a200A to f200F are displayed in an identifiable manner. The user operates the input unit 102 to select the device c200C that performs scanning from the list of device selection candidates displayed on the display unit 103 (step S408). At this time, the selected device c200C is displayed on the display unit 103 while being distinguished from other devices.

The data source manager 111 receives a device selection command including information on the device selected from the TWAIN application program 109 based on the selection result in step S408, and refers to the device display name registered in the same model device information table. Then, it is determined whether there is a device of the same model as the selected device c200C (step S409).

Since the selected device c200C is a device of the same model as the device a200A, the device b200B, and the device e200E, the determination result in step S409 is Yes, and the process proceeds to step S410. Then, the data source manager 111 unloads the TWAIN device driver 110 of the device a200A, the device b200B, and the device e200E (step S410). As a result, only the connection with the device c200C is enabled, and the connections with the device a200A, the device b200B, and the device e200E are disabled.

The TWAIN device driver 110 of the device c200C starts communication with the device server a600A via the communication unit 105, transmits a scan execution request to the device c200C via the device server a600A, and the scanned image data Is acquired (step S411). Note that when scanning is continued with the device c200C, the process of step S411 is repeatedly executed.

When the acquisition of the scan image data from the device c200C via the device server a600A is completed, the data source manager 111 disconnects the connection with the device server a600A and ends the process. Here, the TWAIN device driver 110 of the device a200A, device b200B, and device e200E unloaded in step S410 is loaded again (step S412).

Since the subsequent processing is the same as Step S413 to Step S415 described in the first embodiment, description thereof is omitted.

Note that when the device d200D or the device f200F is selected in step S408, the determination in step S409 described above is different.

When the device d200D or the device f200F is selected, since there is no device of the same model in step S409, the determination result is No, the process proceeds to step S416, and a scan execution request is made to the device c200C as in step S411. Is transmitted, the scanned image data is acquired, and the process proceeds to step S413.

As described above, according to the device control system of the third embodiment, the client PC 100 acquires device information corresponding to a connection form from a locally connected device, a device connected via a device server, and a network connected device. In addition, since each device can be identified based on the individual identification information generated by the OS 108 from this device information, a plurality of devices 200 can be switched and used even when devices 200 having different connection forms are mixed in the system. Can do.

Note that the present invention is not limited to the above-described embodiment, and can be appropriately changed without departing from the gist of the present invention.

In the first to third embodiments, the device 200 is not limited to a device that supports TWAIN, but may be a device that supports ISIS (Image and Scanner Interface Specification).

In the first to third embodiments, the data source manager 111 may manage and identify the device 200 using only the device information acquired by the OS 108 without using the individual identification information generated by the OS 108.

In the third embodiment, when a plurality of devices 200 of the same model are connected to the device server 600, the device server 600 connects its own address information to the device information and / or the device 200 to identify each device. The device information to which the connection port information of the device server 600 is added is transmitted. The connection port information of the device server 600 is information for identifying the connection port of the device server 600. For example, the USB port number of the device server 600 or the IEEE 1394 port number may be used, but the present invention is not limited to these.

In the third embodiment, it has been described that the device information obtained by adding the address information of the device 200 (200E, 200F) and the device server 600 (600A, 600B) connected to the network is acquired. It may be acquired as separate information as well as acquired as one piece of information.

In the third embodiment, only the device information of the device 200 (200C, 200D, 200E, 200F) is acquired without acquiring address information from the network-connected device 200 (200E, 200F) or the device server 600 (600A, 600B). You may make it acquire. In this case, the address information of the device 200 (200E, 200F) and the device server 600 (600A, 600B) connected to the network on the client PC 100 side may be stored.

In the third embodiment, it has been described that the device 200 is selected by the TWAIN application program 109. However, as in the second embodiment, the device 200 may be selected using the card reader 400 or the input device.

Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus. This can also be achieved by reading the program code stored in the storage medium and executing the processing.

In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and a computer-readable storage medium storing the program code constitutes the present invention. .

Further, an OS (operating system) or the like running on the computer performs part or all of the actual processing based on an instruction of the program code, and the functions of the above-described embodiments are realized by the processing. You may do it.

Furthermore, after the program code read from the storage medium is written in the memory of the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. In some cases, the CPU or the like provided in the board or the function expansion unit executes part or all of the actual processing, and the above-described embodiment is realized according to the processing.

In order to supply the program code, for example, a floppy (registered trademark) disk, a hard disk, a magneto-optical disk, an optical disk represented by CD or DVD, a magnetic tape, a nonvolatile memory card, a ROM, or the like is used. Can do. Alternatively, the program code may be downloaded via a network.

100: Client PC
101: CPU
102: Input unit 103: Display unit 104: Memory 105: Communication unit 106: Local I / F (local interface)
107: External storage unit 108: OS
109: TWAIN application program 110: TWAIN device driver 111: Data source manager 112: Internal bus 200 (200A, 200B, 200C, 200D, 200E, 200F): Device 300: Connection cable 400: Card reader 500: Network 600 (600A, 600B): Device server 601: CPU
602: Memory 603: Communication unit 604: Local I / F (local interface)
605: External storage unit 606: Internal bus 607: Communication control unit 608: Device control unit

Claims (10)

A device control apparatus for operating the device via the application by controlling an interface between the application and the device,
Device list display command receiving means for receiving a device list display command from the application;
In response to receiving the device list display command by the device list display command receiving means, device information acquisition means for acquiring device information from a currently connected device;
The same model determination means for determining whether or not a device of the same model is connected by the device information acquired by the device information acquisition means;
When it is determined by the same model determination means that devices of the same model are connected, individual identification information of each device of the same model is acquired, and a device corresponding to the acquired individual identification information can be identified Device display name generation means for generating the device display name of
Table registration means for registering the device display name generated by the device display name generation means in a table in association with the individual identification information;
Write the device display name registered in the table for devices connected to the same model, and create a device list that describes the device display name included in the device information for devices not connected to the same model. , Device list transmitting means for transmitting the device list to the application;
Device selection command receiving means for receiving a device selection command from the application;
When the device selection command received by the device selection command receiving means includes a device display name registered in the table, the device driver of the same model device other than the device matching the device display name is unloaded. Device driver unloading means,
A device control apparatus comprising: The device control apparatus according to claim 1, further comprising a device driver loading unit that loads the device driver unloaded by the device driver unloading unit after the processing by the device is completed. The device control apparatus according to claim 1, further comprising a table initialization unit that initializes the table after the processing by the device is completed. If the device is networked or locally connected to a networked device server,
The device control according to claim 1, wherein the device information acquisition unit acquires only the device information, or acquires address information of the device or the device server together with the device information. apparatus. A device control method of operating a device via the application by controlling an interface between the application and the device,
A device list display command receiving step for receiving a device list display command from the application;
In response to receiving the device list display command in the device list display command receiving step, a device information acquisition step of acquiring device information from a currently connected device;
The same model determination step for determining whether or not a device of the same model is connected by the device information acquired in the device information acquisition step;
When it is determined in the same model determination step that devices of the same model are connected, individual identification information of each device of the same model is acquired, and a device corresponding to the acquired individual identification information can be identified A device display name generation step for generating a device display name of
A table registration step of registering the device display name generated in the device display name generation step in a table in association with the individual identification information;
Write the device display name registered in the table for devices connected to the same model, and create a device list that describes the device display name included in the device information for devices not connected to the same model. A device list transmission step for transmitting the device list to the application;
A device selection command receiving step for receiving a device selection command from the application;
If the device selection command received in the device selection command reception step includes a device display name registered in the table, the device driver of the same model device other than the device matching the device display name is unloaded. A device driver unloading step,
A device control method comprising: The device control method according to claim 5, further comprising a device driver loading step of loading the device driver unloaded in the device driver unloading step after the processing by the device is completed. The device control method according to claim 5, further comprising a table initialization step of initializing the table after the processing by the device is completed. If the device is networked or locally connected to a networked device server,
8. The device control according to claim 5, wherein in the device information acquisition step, only the device information is acquired, or address information of the device or the device server is acquired together with the device information. Method. A device control system comprising: a device; a device server locally connected to the device; and a device control device that controls the device via the device server connected to a network.
The device server is
First device information acquisition means for acquiring device information from the device;
Unique information adding means for adding address information of the device server itself to the device information acquired by the first device information acquiring means;
Device information for transmitting either the device information acquired by the first device information acquisition unit or the device information to which the address information is added by the specific information addition unit to the device control apparatus as device information of the device A transmission means;
With
The device controller is
Device list display command receiving means for receiving a device list display command from the application;
Second device information acquisition means for acquiring device information of the device from the device server in response to receiving the device list display instruction by the device list display instruction reception means;
The same model determination means for determining whether or not a device of the same model is connected based on the device information acquired by the second device information acquisition means;
When it is determined by the same model determination means that devices of the same model are connected, individual identification information of each device of the same model is acquired, and the corresponding device can be identified from the acquired individual identification information Device display name generation means for generating the device display name of
Table registration means for registering the device display name generated by the device display name generation means in a table in association with the individual identification information;
Write the device display name registered in the table for devices connected to the same model, and create a device list that describes the device display name included in the device information for devices not connected to the same model. , Device list transmitting means for transmitting the device list to the application;
Device selection command receiving means for receiving a device selection command from the application;
When the device selection command received by the device selection command receiving means includes a device display name registered in the table, the device driver of the same model device other than the device matching the device display name is unloaded. Device driver unloading means,
A device control system comprising: The device control system according to claim 9, wherein the unique information adding unit adds port information to which the device is locally connected to the device information acquired by the first device information acquiring unit.

Images