JP2015115900A - Image reading apparatus, control method of the same, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To adaptively read an image without depending on a driver of a request source.SOLUTION: On the basis of a command received from an information processing apparatus in accordance with a predetermined communication protocol, it is determined which of a first image reading sequence based on a command based on the predetermined communication protocol or a second image reading sequence based on a command not based on the predetermined communication protocol to use as an image reading sequence to use for image reading. Image reading is executed in accordance with the determined image reading sequence.

Description

  The present invention relates to an image reading technique for reading an image in response to a request from an information processing apparatus.

  In recent years, as the network infrastructure is improved, network-compatible printers, copiers, facsimiles, scanners, digital cameras, and devices (peripheral devices) having these combined functions are rapidly spreading. For example, a scanner (image reading apparatus) connected to a network has a function of transmitting image data generated by reading a document to an information processing apparatus such as a PC. In order to realize such a scanning function on the network, the image reading apparatus supports several network protocols and communicates with the information processing apparatus.

  Here, consider a case where Windows (registered trademark) Vista of Microsoft (registered trademark) is installed in the information processing apparatus as an OS (Operating System). In Windows (registered trademark) Vista (or later OS), a technology called WSD (Web Services on Devices) is supported. WSD is a standard specification defined to answer various service requests using devices. Basically, a web service architecture is used, and a standard communication protocol group on a standardized network, a print service, and a scan service are provided.

  An OS standard scanner driver using WSD (WIA: an OS standard image input API adopted by Microsoft after Windows (registered trademark) Me) is preinstalled in the OS. Since the image reading apparatus supports the WSD standard scan service, a network scan using an OS standard WIA driver is possible. In the standard scan service of WSD, various commands and various events for using the scan service are defined by a language based on a format compliant with WSD. Furthermore, it is also a logo requirement of WHQL (Windows Hardware Quality Labs) that the image reading apparatus supports the WSD standard scan service.

  As a prior art that supports WSD and other network protocols, there is a method of detecting devices using a plurality of protocols and combining the displays into one (see Patent Document 1).

JP 2009-187533 A

  Generally, as a scanner driver of Windows (registered trademark), there is a TWAIN driver manufactured by a peripheral manufacturer using an OS standard WIA driver and TWAIN (an interface between the image processing software and the scanner defined by the TWAIN working group). Since the WIA driver has few functions such as scan setting and image correction, the TWAIN driver may be required to perform scanning with more detailed settings according to the capabilities of the image reading apparatus.

  However, in the network scan using WSD, only a combination of an image reading apparatus compatible with the WSD standard scan service and a WIA driver installed in the information processing apparatus is currently supported. Since a method for performing network scanning from a TWAIN driver using WSD has not been established, there is a problem that a peripheral device manufacturer has to communicate between the image reading apparatus and the information processing apparatus using a unique network protocol.

  In addition, it is necessary to use a large memory capacity in the image reading apparatus to implement two network protocols unique to WSD and peripheral device manufacturers. Since Windows (registered trademark) Vista and later, it has become an essential requirement of WHQL to support the WSD standard scan service, and there is a direction to unify the WSD from the network protocol unique to the peripheral device manufacturer. When scanning can be performed from both the OS standard WIA driver and the peripheral device manufacturer's TWAIN driver using WSD, the image reading commands communicated between the image reading device and the information processing device are different for each driver. The image reading apparatus needs to distinguish whether the WIA driver or the TWAIN driver has issued the image reading command.

  SUMMARY An advantage of some aspects of the invention is that it provides an image reading technique capable of adaptively reading an image without depending on a driver of a request source.

In order to achieve the above object, an image reading apparatus according to the present invention comprises the following arrangement. That is,
An image reading device that reads an image in response to a request from an information processing device,
Communication means for communicating with the information processing device according to a predetermined communication protocol;
Based on the command received by the communication means, the image reading sequence used for image reading is not based on the first image reading sequence based on the command complying with the predetermined communication protocol or the predetermined communication protocol. Determination means for determining whether to use one of the second image reading sequences based on the command;
Execution means for executing image reading in accordance with the image reading sequence determined by the determining means.

  According to the present invention, it is possible to adaptively read an image without depending on the driver of the request source.

1 is a block diagram illustrating a schematic configuration of an MFP according to a representative embodiment. It is a block diagram which shows schematic structure of PC which is typical embodiment. 1 is a diagram illustrating a schematic configuration of a network system including an MFP and a PC. It is a conceptual diagram of the module in PC at the time of the conventional network scan. It is a conceptual diagram of the module in PC at the time of a network scan. 6 is a sequence chart when the MFP and the PC according to the first embodiment communicate via a network and perform scanning from an OS standard WIA driver. 6 is a sequence chart when the MFP and the PC according to the first embodiment communicate via a network and perform scanning from an OS standard WIA driver and a TWAIN driver manufactured by a peripheral device manufacturer. 4 is a flowchart illustrating processing in which the MFP according to the first embodiment determines an OS standard WIA driver and a TWAIN driver manufactured by a peripheral device manufacturer. 10 is a sequence chart when the MFP and the PC of the second embodiment communicate via a network and perform scanning from an OS standard WIA driver and a TWAIN driver manufactured by a peripheral device manufacturer. 10 is a flowchart illustrating processing in which the MFP according to the second exemplary embodiment determines an OS standard WIA driver and a peripheral device manufacturer TWAIN driver. 10 is a sequence chart when an MFP and a PC according to the third embodiment communicate via a network and perform scanning from an OS standard WIA driver and a TWAIN driver manufactured by a peripheral device manufacturer. 15 is a flowchart illustrating processing in which the MFP according to the third embodiment determines an OS standard WIA driver and a peripheral device manufacturer TWAIN driver. 10 is a sequence chart when an MFP and a PC according to a fourth embodiment communicate via a network and perform scanning from a TWAIN driver manufactured by a peripheral device manufacturer. FIG. 16 is a sequence chart when the MFP and the PC according to the fifth embodiment communicate via a network and perform scanning from a TWAIN driver manufactured by a peripheral device manufacturer.

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

<Embodiment 1>
As Embodiment 1, an information processing method for performing a network scan (scan via a network) using WSD (Web Services on Devices) which is one of communication protocols on a network will be described.

  FIG. 1 is a block diagram showing a schematic configuration of an MFP (Multi Function Peripheral) which is an example of an embodiment of an image reading apparatus. The MFP 100 has a printer function, a scanner function, and a storage function, and can provide each function service via a network.

  In the MFP 100, the printer function is realized by the printer unit 101, the scanner function is realized by the scanner unit 102, and the storage function is realized by the memory card mounting unit 103 and the memory card 104. Also, a copy function can be realized by combining a printer function and a scanner function.

  The printer unit 101 prints data such as print data received from the outside or image data stored in the memory card 104 on a print sheet by a printing method such as an inkjet method or an electrophotographic method. The scanner unit 102 optically reads a document set on a document table, converts it into electronic data, converts it into a specified file format, and transmits it to an external device via a network. In the copy service, image data generated by reading a document placed on a document table by the scanner unit 102 is transferred to the printer unit 101, and the printer unit 101 prints the document data on printing paper. In addition, a file stored in the memory card 104 can be read and edited by an external device connected via a network, and the file can be stored in the memory card 104 from the external device.

  The MFP 100 further includes a central processing unit (CPU) 105 for controlling various components of the MFP 100 and a program memory 106 such as a ROM for storing data such as programs read by the CPU 105. The MFP 100 also includes a work memory 107 such as a RAM for temporarily storing and buffering data such as image data when executing each service, a display unit 108 such as an LCD, and an operation unit 109 including switches. .

  In addition, MFP 100 includes a network communication unit 110 for connecting MFP 100 to a network to perform various communications, and a network connection unit 111 for connecting network communication unit 110 to a network medium. The network communication unit 110 corresponds to at least one of a wired network and a wireless network. In the case of a wired network, the network connection unit 111 is a connector for connecting a wired network cable to the MFP 100. In the case of wireless network compatibility, the network connection unit 111 is an antenna.

  The MFP 100 further includes a flash memory 112 that is a nonvolatile memory in order to store transmission source information of packets received by the network communication unit 110. The MFP 100 further includes a USB communication unit 114 for communicating with an information processing apparatus (PC) via a USB (Universal Serial Bus) interface, and the information processing apparatus is connected to a USB connection unit 115 using a connector such as a USB connector. Connect with.

  Various components of the MFP 100 are connected to each other through a signal line 113.

  FIG. 2 is a block diagram illustrating a schematic configuration of a PC that is an example of an embodiment of an information processing apparatus. The information processing apparatus can be realized, for example, by installing predetermined software on a general-purpose PC.

  In FIG. 2, 201 is a CPU for controlling various components of the PC 200. Reference numeral 202 denotes a disk device that installs application programs read by the CPU 201, an OS (Operation System), and the like, and stores data such as various files. Reference numeral 203 denotes an external disk reader for reading the contents of an external storage medium such as a CD-ROM. A memory 204 is used for the CPU 201 to perform processing such as temporary storage of data and buffering as necessary.

  Various programs are installed in the PC 200 by executing a software setup program for using the MFP 100 from the PC 200. The various programs include a scanner driver for using the scan function and a printer driver for using the printer function. Further, various applications such as a polling application for inquiring the state of MFP 100 (the presence or absence of an event, etc.) and management software (status monitor) for managing the state (status) of MFP 100 are included. Further, an image processing application corresponding to TWAIN as an API (Application Programming Interface) and an image processing application corresponding to WIA as an API are included.

  Reference numeral 205 denotes a display unit composed of an LCD or the like. Reference numeral 206 denotes an operation unit such as a keyboard or a mouse. Reference numeral 207 denotes a network communication unit for connecting the PC 200 to the network to perform various communications. Reference numeral 208 denotes a network connection unit for connecting the network communication unit 207 to a network medium.

  Similar to MFP 100, network communication unit 207 and network connection unit 208 correspond to at least one of a wired network and a wireless network. A specific form, like the network communication unit 110 and the network connection unit 111 built in the MFP 100, takes necessary functions and forms according to the corresponding network. Reference numeral 209 denotes a signal line for connecting various components of the PC 200 to each other. Reference numeral 210 denotes a USB communication unit for communicating with various peripheral devices via a USB interface. Reference numeral 211 denotes a USB connection unit such as a USB connector.

  FIG. 3 is a block diagram showing a schematic configuration of a network system including MFP 100 of FIG. 1 and PC 200 of FIG.

  In FIG. 3, an MFP 100 that is an image reading apparatus and a PC 200 that is an information processing apparatus are connected to a network 300. The network 300 is, for example, a local area network (LAN).

  In FIG. 3 and the following description, a network composed of the network 300 that is a wired network cable is treated. However, the present invention is not limited to this, and the wired network and the wireless network are mixed even if the network mode is a wireless network. The same applies to the network. The image reading apparatus is not necessarily the MFP 100, and may be a single-function image scanner or digital camera.

  In FIG. 3, only one PC 200 and one MFP 100 are shown, but a plurality of PCs 200 and a plurality of MFPs 100 can be connected to the same network 300.

  FIG. 4 is a conceptual diagram of modules in the PC 200 during a conventional network scan.

  The TWAIN compatible application 401 in the PC 200 activates the TWAIN driver 402 and accesses the MFP 100 via the scanner control driver 403.

  Here, in order to perform communication on the network, a peripheral device manufacturer's original (vendor's original) network protocol 404 is used, and commands are transmitted / received to / from the MFP 100 through WINSOCK (Windows (registered trademark) Sockets API) 405. Get the data.

  Next, when executing a scan from the WIA-compatible application 406, the OS standard Microsoft WSD Scan Driver (WSD ScDrv.dll) 408 is activated via the OS STI / WIA Service 407. The WSD Scan Driver 408 communicates with the MFP 100 through the WINSOCK (Windows (registered trademark) Sockets API) 405 using the WSD service (WSD API) 409 to acquire image data.

  FIG. 5 is a conceptual diagram of modules in the PC 200 according to the first embodiment with respect to FIG.

  The TWAIN compatible application 401 in the PC 200 activates the TWAIN driver 402 and accesses the MFP 100 via the scanner control driver 403.

  Here, similarly to the WSD Scan Driver 408, the scanner control driver 403 uses the WSD service (WSD API) 409 to transmit / receive commands to / from the MFP 100 through the WINSOCK (Windows (registered trademark) Sockets API) 405. get. Thereby, the network scan can be realized from the TWAIN driver 402 without using the network protocol 404 (FIG. 4) unique to the peripheral device manufacturer.

  The PC 200 and the MFP 100 can use these commands to implement processing related to network scanning.

  FIG. 6 is a sequence chart when the MFP 100 and the PC 200 communicate via the network 300 and perform a network scan (WSD scan) from the OS standard WIA driver.

  The PC 200 is assumed to have an environment in which an OS such as Windows (registered trademark) Vista or Windows (registered trademark) 7 corresponding to the WSD scan service is installed. In order for the OS to recognize the MFP 100 as an image reading apparatus compatible with the WSD scan service, the MFP 100 on the network displayed on the PC 200 may be selected and installed. With this procedure, the OS standard WSD scanner driver is installed.

  When scanning from the OS standard WIA driver, the PC 200 transmits a WSD scan request command (CreateScanJob Request) including scan settings (scan parameters) to the MFP 100 at the start of scanning (S601).

  If the MFP 100 can scan according to the scan parameters including the scan request command, the MFP 100 returns a scan response command (CreateScanJob Response) to the PC 200 (S602).

  In response to this, the PC 200 transmits a WSD image acquisition request command (RetrieveImage Request) to the MFP 100 using the WIA driver (S603).

  Upon receiving the image acquisition request command, the MFP 100 returns an image acquisition response command (RetrieveImage Response) to the PC 200 (S604). Subsequently, the MFP 100 executes reading (scanning) of an image by the scanner unit 102 in accordance with the designated scan setting, and transmits scan data (for example, a JPEG image) obtained thereby to the PC 200 by a message transmission optimization mechanism (MTOM). (S605).

  FIG. 7 is a sequence chart when the MFP 100 and the PC 200 communicate with each other via the network 300 and perform a network scan using WSD from the OS standard WIA driver and the TWAIN driver manufactured by the peripheral device manufacturer according to this embodiment. . In FIG. 7, the same reference numerals are added to the same sequences as those in FIG.

  When scanning from the TWAIN driver, the PC 200 transmits a scan request command (CreateScanJob Request) including scan settings (scan parameters) to the MFP 100 at the start of scanning (S701).

  If the MFP 100 is in a scannable state, the MFP 100 returns a scan response command (CreateScanJob Response) to the PC 200 (S702).

  Next, since the PC 200 transmits a command (vendor command) unique to the vendor (peripheral device manufacturer) using the TWAIN driver, the scanner element acquisition request command (GetScannerElements Request), which is a WSD standard command, is included in the format including the vendor command. It is transmitted to the MFP 100 (S703).

  Here, when scanning from the WIA driver of the PC 200, the MFP 100 receives an image acquisition request command (RetrieveImage Request) from the PC 200 (S603). In this case, the MFP 100 returns an image acquisition response command (RetrieveImage Response) to the PC 200 (S604).

  On the other hand, when the scanner element acquisition request command (GetScannerElements Request) is received from the PC 200, the MFP 100 determines that the scan is from the TWAIN driver of the PC 200. In that case, the MFP 100 interprets the vendor command in the scanner element acquisition request command (GetScannerElements Request). Then, the MFP 100 incorporates a WSD scanner element acquisition response command (GetScannerElements Response) so as to include response information of the vendor command, and returns it to the PC 200 (S704). Thereafter, S703 and S704 are repeated in accordance with a vendor-specific command sequence, and command transmission / reception and image data transmission / reception are performed using WSD commands.

  FIG. 8 is a flowchart illustrating processing in which the MFP 100 determines and switches between the WSD scan from the OS standard WIA driver of FIG. 7 and the WSD scan from the TWAIN driver. This flowchart is performed by the CPU 105 loading a program into the work memory 107 and executing it.

  In step S <b> 1001, the MFP 100 receives a scan request command (CreateScanJob Request) from the PC 200. In S1002, MFP 100 transmits a scan response command (CreateScanJob Response) to PC 200 if scanning is possible. In step S1003, the MFP 100 determines whether an image acquisition request command (RetrieveImage Request) is received from the PC 200 as the next command. As shown in FIG. 6, at the time of scanning from the OS standard WIA driver, an image acquisition request command is transmitted after the scan request command.

  When the image acquisition request command is received (YES in S1003), in S1004, the MFP 100 determines that the scan is from the OS standard WIA driver. In step S1005, the MFP 100 reads an image using a scan sequence from the OS standard WIA driver in FIG.

  On the other hand, when an image acquisition request command (RetrieveImage Request) has not been received (NO in S1003), in S1006, the MFP 100 determines whether or not a vendor command is included in the received command. If a vendor command is included (YES in step S1006), in step S1007, the MFP 100 determines that the scan is from a TWAIN driver manufactured by a peripheral device manufacturer (vendor specific). In step S1008, the MFP 100 reads an image using a scan sequence from a TWAIN driver manufactured by a peripheral device manufacturer (vendor unique) in FIG.

  On the other hand, if the vendor command is not included (NO in S1006), the process returns to S1003.

  As described above, according to the first embodiment, it is determined whether the vendor command is included in the next command after the difference in the scan sequence or the scan request command (CreateScanJob Request). Thereby, it is possible to determine a scan from the OS standard WIA driver and a scan from the TWAIN driver manufactured by the peripheral device manufacturer.

  As a result, network scanning can be performed from either the OS standard WIA driver or the peripheral device manufacturer's TWAIN driver using WSD.

  Further, by providing a configuration for distinguishing from which driver of the WIA driver and the TWAIN driver the image reading command is transmitted, the image reading apparatus determines which driver is requested to scan, and sends to each driver. The network scan can be performed by the transmission / reception of the corresponding image reading command and the image data transfer method.

  That is, even when only WSD is supported as a network protocol, network scanning is possible from both the OS standard WIA driver and the TWAIN driver manufactured by the peripheral device manufacturer. By supporting scanning from the TWAIN driver using WSD, it is possible to support many scan settings and image correction functions not found in the OS standard WIA driver, and to fully draw out the performance of the image reading apparatus. Can do. Further, the cost of the image reading apparatus can be prevented by using only one communication protocol, WSD.

<Embodiment 2>
The MFP 100 and the PC 200 used in the second embodiment, the configuration outline, the conceptual diagram of the modules in the PC 200, and the scan sequence chart can use the same configurations as those described with reference to FIGS. Omitted.

  In the second embodiment, a method in which the custom flag is added to the scan request command will be described as a method in which the MFP 100 determines a scan from the OS standard WIA driver and a scan from the TWAIN driver manufactured by the peripheral device manufacturer. .

  FIG. 9 is a sequence chart when the MFP 100 and the PC 200 communicate with each other via the network 300 and perform a network scan using WSD from the OS standard WIA driver and the TWAIN driver manufactured by the peripheral device manufacturer according to this embodiment. . In FIG. 9, the same reference numerals are added to the same sequences as those in FIG.

  When scanning from the TWAIN driver, the PC 200 uses a custom flag for explicitly setting that scanning is from the TWAIN driver together with the scan setting (scan parameter) at the start of scanning (in the vendor-specific namespace in the XML format command). A scan request command (CreateScanJob Request) including a defined tag is added and vendor-specific information (identifier) is added) to MFP 100 (S801).

  If the MFP 100 is in a scannable state, the MFP 100 returns a scan response command (CreateScanJob Response) to the PC 200 (S802). In step S801, the MFP 100 detects whether there is a custom flag. If there is a custom flag, the MFP 100 determines that the scan is from the TWAIN driver. If there is no custom flag, the MFP 100 scans from the WIA driver. Judge that there is.

  Here, when scanning from the WIA driver of the PC 200, the MFP 100 receives an image acquisition request command (RetrieveImage Request) from the PC 200 (S603). In this case, the MFP 100 returns an image acquisition response command (RetrieveImage Response) to the PC 200 (S604).

  On the other hand, when scanning from the TWAIN driver of the PC 200, since a vendor-specific command (vendor command) is transmitted, the PC 200 includes a vendor element including a scanner element acquisition request command (GetScannerElements Request) which is a standard command of WSD. Then, it is transmitted to the MFP 100 in the format (S803).

  When scanning from the TWAIN driver of the PC 200, the MFP 100 determines that the vendor command is incorporated, and interprets the vendor command in the scanner element acquisition request command (GetScannerElements Request). Then, the MFP 100 incorporates the WSD scanner element acquisition response command (GetScannerElements Response) so as to include the response information of the vendor command, and returns it to the PC 200 (S804). Thereafter, S803 and S804 are repeated according to the vendor-specific command sequence, and command transmission / reception and image data transmission / reception are performed using WSD commands.

  FIG. 10 is a flowchart illustrating processing in which the MFP 100 determines and switches between the WSD scan from the OS standard WIA driver of FIG. 9 and the WSD scan from the TWAIN driver. This flowchart is performed by the CPU 105 loading a program into the work memory 107 and executing it.

  In step S <b> 1101, the MFP 100 receives a scan request command (CreateScanJob Request) from the PC 200. In step S1102, the MFP 100 determines whether a custom flag has been added to the scan request command. If the custom flag has not been added (NO in S1102), in S1103, the MFP 100 determines that the scan is from the OS standard WIA driver. In S1104, MFP 100 transmits a scan response command (CreateScanJob Response) to PC 200. In step S1105, the MFP 100 reads an image using a scan sequence from the OS standard WIA driver in FIG.

  On the other hand, if a custom flag has been added (YES in S1102), in S1106, the MFP 100 determines that the scan is from a TWAIN driver manufactured by a peripheral device manufacturer (vendor specific). In step S <b> 1107, the MFP 100 transmits a scan response command (CreateScanJob Response) to the PC 200. In step S1108, the MFP 100 reads an image using the scan sequence from the TWAIN driver manufactured by the peripheral device manufacturer in FIG.

  As described above, according to the second embodiment, the MFP 100 determines whether the custom flag is included in the scan request command (CreateScanJob Request) that is the first command in the scan sequence. Thereby, it is possible to determine a scan from the OS standard WIA driver and a scan from the TWAIN driver manufactured by the peripheral device manufacturer. Also, by including a custom flag in the scan request command (CreateScanJob Request) that is the first command to start scanning, WIA / TWAIN scanning can be quickly switched without analyzing the scan sequence.

<Embodiment 3>
The MFP 100 and the PC 200 used in the third embodiment, a schematic configuration, a conceptual diagram of modules in the PC 200, and a scan sequence chart can use the same configurations as those described with reference to FIGS. Omitted.

  In the third embodiment, a method in which the MFP 100 incorporates a vendor command into a scan request command will be described as a method for the MFP 100 to determine a scan from an OS standard WIA driver and a scan from a TWAIN driver manufactured by a peripheral device manufacturer.

  FIG. 11 is a sequence chart when the MFP 100 and the PC 200 communicate via the network 300 and perform a network scan using WSD from the OS standard WIA driver and the TWAIN driver manufactured by the peripheral device maker according to this embodiment. . In FIG. 11, the same reference numerals are added to the same sequences as those in FIG.

  When scanning from the TWAIN driver, the PC 200 transmits a scan request command (CreateScanJob Request) issued at the start of scanning to the MFP 100 in a format including a vendor command (peripheral device manufacturer's unique command) (S901).

  If the vendor command is incorporated, the MFP 100 determines that the scan is from the TWAIN driver. If the scan is possible, the MFP 100 incorporates the scan response command (CreateScanJob Response) so that the response information of the vendor command is included. Is returned to the PC 200 (S902).

  After that, the PC 200 transmits a scanner element acquisition request command (GetScannerElements Request), which is a WSD standard command, to the MFP 100 in a form incorporating the vendor command in accordance with the vendor-specific command sequence (S903).

  The MFP 100 interprets the vendor command in the scanner element acquisition request command (GetScannerElements Request), embeds the WSD scanner element acquisition response command (GetScannerElements Response) so as to include the response information of the vendor command, and returns it to the PC 200 (S904). ). Thereafter, S903 and S904 are repeated in accordance with a vendor-specific command sequence, and command transmission / reception and image data transmission / reception are performed using WSD commands.

  FIG. 12 is a flowchart illustrating a process in which the MFP 100 determines and switches between the WSD scan from the OS standard WIA driver of FIG. 11 and the WSD scan from the TWAIN driver. This flowchart is performed by the CPU 105 loading a program into the work memory 107 and executing it.

  In step S <b> 1201, the MFP 100 receives a scan request command (CreateScanJob Request) from the PC 200. In step S1202, the MFP 100 determines whether a vendor-specific command (vendor command) is included in the scan request command. If the vendor command is not incorporated (NO in S1202), the MFP 100 determines that the scan is from the OS standard WIA driver (S1203). In S1204, MFP 100 returns a scan response command (CreateScanJob Response) to PC 200. In step S1205, the MFP 100 reads an image using the scan sequence from the OS standard WIA driver in FIG.

  On the other hand, if the vendor command is incorporated (YES in S1202), in S1206, the MFP 100 determines that the scan is from a TWAIN driver manufactured by a peripheral device manufacturer. In step S <b> 1207, the MFP 100 transmits a scan response command (CreateScanJob Response) incorporating a response of the vendor command to the PC 200. In step S1208, the MFP 100 reads an image using the scan sequence from the TWAIN driver manufactured by the peripheral device manufacturer in FIG.

  As described above, according to the third embodiment, the MFP 100 determines whether a vendor-specific command (vendor command) is included in the scan request command (CreateScanJob Request) that is the first command in the scan sequence. Thereby, it is possible to determine a scan from the OS standard WIA driver and a scan from the TWAIN driver manufactured by the peripheral device manufacturer. By including the vendor command in the scan request command (CreateScanJob Request) that is the first command to start scanning, the WIA / TWAIN scan can be quickly switched without analyzing the scan sequence.

<Embodiment 4>
The MFP 100 and the PC 200 used in the fourth embodiment, the configuration outline, the conceptual diagram of the modules in the PC 200, and the scan sequence chart can use the same configurations as those described with reference to FIGS. Omitted.

  In the fourth embodiment, a method for selectively using WSD standard commands according to the contents of commands in a scan sequence in which the MFP 100 performs a scan from a TWAIN driver manufactured by a peripheral device manufacturer that is not OS standard will be described.

  FIG. 13 is a sequence chart when the MFP 100 and the PC 200 communicate via the network 300 and perform a network scan using WSD from a TWAIN driver manufactured by a peripheral device manufacturer that is not an OS standard according to the present embodiment.

  When scanning from the TWAIN driver, the PC 200 uses a custom flag for explicitly setting that scanning is from the TWAIN driver together with the scan setting (scan parameter) at the start of scanning (in the vendor-specific namespace in the XML format command). A scan request command (CreateScanJob Request) including a defined tag (adding vendor-specific information) is transmitted to the MFP 100 (S1301).

  If the MFP 100 is in a scannable state, the MFP 100 returns a scan response command (CreateScanJob Response) to the PC 200 (S1302). In step S1301, the MFP 100 detects whether there is a custom flag. If there is a custom flag, the MFP 100 determines that the scan is from the TWAIN driver.

  Next, in order to transmit a vendor-specific command (vendor command) using the TWAIN driver, the PC 200 transmits a scanner element acquisition request command (GetScannerElements Request), which is a WSD standard command, to the MFP 100 in a form including the vendor command ( S1303).

  If the vendor command is included in the scanner element acquisition request command, the MFP 100 determines that the scan is from the TWAIN driver, and interprets the vendor command. Then, the MFP 100 incorporates a WSD scanner element acquisition response command (GetScannerElements Response) so as to include response information of the vendor command, and returns it to the PC 200 (S1304).

  Here, a setting-type command sequence that does not include image data in a vendor-specific command sequence is performed by repeating S1303 and S1304. This is because there is a concern that the performance may be deteriorated when a command for increasing the data size such as image data is transmitted / received by a scanner element acquisition request command / scanner element acquisition response command.

  Further, regarding the acquisition of image data, the PC 200 transmits a WSD image acquisition request command (RetrieveImage Request) to the MFP 100 (S1305).

  The MFP 100 returns an image acquisition response command (RetrieveImage Response) to the PC 200 (S1306). Subsequently, the MFP 100 transmits scan data (for example, a JPEG image) to the PC 200 by MTOM (Message Transmission Optimization Mechanism) (S1307).

  Here, the scan data need not be limited to the JPEG format, and may be image data corresponding to various file formats such as the BMP format and the RAW format. Then, the image data is transferred by repeating S1305 to S1307 in accordance with the vendor-specific command sequence. The scan sequence described with reference to FIG. 13 can be applied in place of the scan sequence from the TWAIN driver of the first, second, and third embodiments.

  As described above, according to the fourth embodiment, when a command sequence unique to a vendor is executed, the performance is reduced by changing (switching) the command processing system according to the type of the command. Can be prevented.

<Embodiment 5>
The MFP 100 and the PC 200 used in the fifth embodiment, the configuration outline, the conceptual diagram of the modules in the PC 200, and the scan sequence chart can use the same configurations as those described in FIG. 1 to FIG. Omitted.

  In the fourth embodiment, a method for selectively using WSD standard commands according to the contents of commands in a scan sequence in which the MFP 100 performs a scan from a TWAIN driver manufactured by a peripheral device manufacturer that is not OS standard will be described.

  FIG. 14 is a sequence chart when the MFP 100 and the PC 200 communicate via the network 300 to perform a network scan using WSD from a TWAIN driver manufactured by a peripheral device manufacturer that is not an OS standard according to this embodiment.

  When scanning from the TWAIN driver, the PC 200 uses a custom flag for explicitly setting that scanning is from the TWAIN driver together with the scan setting (scan parameter) at the start of scanning (in the vendor-specific namespace in the XML format command). A scan request command (CreateScanJob Request) including a defined tag is added and vendor-specific information is added (S1401).

  If the MFP 100 is in a scannable state, the MFP 100 returns a scan response command (CreateScanJob Response) (S1402). In step S1401, the MFP 100 detects whether there is a custom flag. If there is a custom flag, the MFP 100 determines that the scan is from the TWAIN driver.

  Next, since the PC 200 transmits a peripheral device manufacturer's original command (vendor command) using the TWAIN driver, the PC 200 transmits the scanner element acquisition request command (GetScannerElements Request), which is a WSD standard command, in a format including the vendor command ( S1403).

  If the vendor command is incorporated in the scanner element acquisition request command, the MFP 100 determines that the scan is from the TWAIN driver, interprets the vendor command, and prepares a response thereto. However, in this case, the MFP 100 returns a WSD scanner element acquisition response command (GetScannerElements Response) without incorporating the response information of the vendor command (S1404).

  Then, the PC 200 transmits a WSD image acquisition request command (RetrieveImage Request) to the MFP 100.

  In response to this, the MFP 100 transmits an image acquisition response command (RetrieveImage Response) to the PC 200 (S1406). Here, the MFP 100 incorporates the response information of the vendor command interpreted in S1403 into a message transmission optimization mechanism (MTOM) and transmits it (S1407). This is because the response of all the vendor commands is returned as one message in common in S1407, so that the scan sequence can be unified and the development load of the MFP 100 and the PC 200 can be suppressed. Further, even when the data size is increased as in the case of image data by using the image acquisition request command / image acquisition response command, there is no concern that the performance deteriorates.

  Then, in accordance with the command sequence unique to the peripheral device manufacturer, all command transmission / reception from setting commands to image data transfer is realized by repeating S1403 to S1407.

  Here, the scan sequence described with reference to FIG. 14 can be applied in place of the scan sequence from the TWAIN driver of the first, second, and third embodiments.

<Embodiment 6>
In the above embodiment, the scan data need not be limited to the JPEG format, but may be image data corresponding to various file formats such as the BMP format and the RAW format.

  As described in the above embodiment, the predetermined communication protocol for realizing the WSD service includes a scan request command (CreateScanJob Request), a scan response command (CreateScanJob Response), and an image acquisition request command as a command group conforming to the communication protocol. (RetrieveImage Request), a first command such as an image acquisition response command (RetrieveImage Response).

  Here, in the first command, a command unique to the vendor (peripheral device manufacturer) (second command), that is, a command that does not comply with a predetermined communication protocol can be included as necessary. Here, the second command includes a vendor command in the first and third embodiments, a custom flag for explicitly setting the scan from the TWAIN driver in the second embodiment, and the like.

  In the above-described embodiment, a predetermined communication protocol is used as an image reading sequence (scan sequence) to be used in accordance with the received contents of the first command and the second command (the order of reception and the presence / absence of inclusion). Either a first image reading sequence based on a compliant command or a second image reading sequence based on a command not compliant with a predetermined communication protocol is selected. The API may be other than TWAIN and WIA.

  Note that the processing of the above embodiment is also realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed. At this time, processing may be performed by one computer, or processing may be performed while linking a plurality of computers. Also, part or all of this processing may be realized by hardware such as ASIC (Application Specific Integrated Circuit).

Claims (11)

An image reading device that reads an image in response to a request from an information processing device,
Communication means for communicating with the information processing device according to a predetermined communication protocol;
Based on the command received by the communication means, the image reading sequence used for image reading is not based on the first image reading sequence based on the command complying with the predetermined communication protocol or the predetermined communication protocol. Determination means for determining whether to use one of the second image reading sequences based on the command;
An image reading apparatus comprising: execution means for executing image reading in accordance with the image reading sequence determined by the determining means. The determination unit is configured to read the first image reading based on an order in which the communication unit receives a first command that conforms to the predetermined communication protocol and a second command that does not conform to the predetermined communication protocol. The image reading apparatus according to claim 1, wherein the sequence or the second image reading sequence is determined. The determination unit determines the first image reading sequence or the second image reading sequence based on an identifier included in a first command that conforms to the predetermined communication protocol received by the communication unit. The image reading apparatus according to claim 1. The determination unit is configured to determine whether the first command that conforms to the predetermined communication protocol received by the communication unit includes a second command that does not conform to the predetermined communication protocol. The image reading apparatus according to claim 1, wherein the image reading sequence or the second image reading sequence is determined. The communication means transmits and receives a command in a format including a second command not conforming to the predetermined communication protocol to the information processing apparatus in a first command conforming to the predetermined communication protocol. The image reading apparatus according to claim 1, wherein: The image reading apparatus according to any one of claims 1 to 5, wherein the predetermined communication protocol is a WSD (Web Service on Device) protocol. The communication means includes a command conforming to the WSD protocol,
A command including a second command that does not comply with the WSD protocol in the scanner element acquisition request command (GetScannerElements Request) and the scanner element acquisition response command (GetScannerElements Response). The image reading device according to claim 6, wherein the image reading device transmits and receives the image. The communication means includes a command conforming to the WSD protocol,
Image acquisition request command (RetrieveImage Request)
A command in a format including a second command that does not conform to the WSD protocol in an image acquisition response command (RetrieveImage Response) is transmitted / received to / from the information processing apparatus. Or the image reading device according to 7. The communication means performs a response corresponding to all commands in a format including a second command that does not conform to the predetermined communication protocol in a command conforming to the WSD protocol using one message. The image reading apparatus according to claim 6, wherein the image reading apparatus is an image reading apparatus. A method for controlling an image reading apparatus for reading an image in response to a request from an information processing apparatus,
In accordance with a command received from the information processing apparatus according to a predetermined communication protocol, an image reading sequence used for image reading is a first image reading sequence based on a command conforming to the predetermined communication protocol, or the predetermined A determination step of determining which of the second image reading sequences based on a command that does not comply with the communication protocol is used;
An image reading apparatus control method comprising: an execution step of executing image reading according to the image reading sequence determined by the determination step. A program for causing a computer to control the control of an image reading device that executes image reading in response to a request from an information processing device,
The computer,
In accordance with a command received from the information processing apparatus according to a predetermined communication protocol, an image reading sequence used for image reading is a first image reading sequence based on a command conforming to the predetermined communication protocol, or the predetermined A determination unit that determines which of the second image reading sequences based on a command that does not comply with the communication protocol is used;
A program that functions as an execution unit that executes image reading in accordance with an image reading sequence determined by the determination unit.

Images