JP2011104843A - Image forming apparatus, method and program for processing information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To flexibly determine the use of a USB device when it is connected to an MFP. <P>SOLUTION: The image forming apparatus includes: a storage means for storing a management table indicating the possibility of the use of a USB device to correlate with Vender ID and/or Product ID of the USB device connectable via a USB interface and to correlate with class information and sub-class information; an information capturing means for capturing the Vender ID and/or Product ID of the USB device connected via the USB interface and the class information and sub-class information; and a determining means. If information captured by the information capturing means is information that has not been stored in the management table and if a Vender ID or product ID same as the Vender ID or Product ID of the captured information is equal to or greater than a predetermined number as a number stored to be usable in the management table, the determining means determines that the connected USB device to be usable. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an image forming apparatus to which a USB (Universal Serial Bus) device can be connected.

  In a device such as an MFP (Multifunction Peripheral) that requires strict cost requirements for hardware configuration, a hard key with low operability is generally used. When a user inputs character string data such as a login user name, password, and scan delivery destination information, for example, input is performed using a hard key with low operability. This hard key includes a so-called mobile phone type character input key and a numeric keypad.

  For MFPs equipped with a large touch panel, a method of using a software keyboard displayed on the touch panel is generally implemented. In order to expand the character input means and improve the user-friendliness, a technology that enables character input using a USB keyboard connected to a USB host in an MFP including a USB host is considered and already known.

  For example, in Patent Document 1, in an MFP having poor character input means, an application for handling a USB keyboard is arranged on the MFP, and based on class / subclass information of a USB device connected to a USB host, A technique for determining whether or not a device is a USB keyboard is disclosed. As a result, the character input means can be expanded by accepting a character input from the USB keyboard by the user using an application for handling the USB keyboard.

  However, in the prior art, when determining that the USB device connected to the USB host is a USB keyboard and determining whether to start device handling, the class of the USB device is the Human Interface Device class, and the subclass In general, whether or not is a Keyboard class is used as a criterion. In this method, the class is the Human Interface Device class, and the subclass is the Keyboard class. However, USB devices that should not be handled in the same way (or do not want to be handled) in reality are handled in the same way as USB keyboards. There is a problem that.

  For example, as an example of a USB device, a part of a card reader of a non-contact ID card, a magnetic card, or a barcode card can be given. These USB devices are widely used for user authentication using an ID card (for example, a user's employee ID card or entrance / exit card) in the MFP. These USB devices have a function of outputting a card ID to a USB host as a character string input from a USB keyboard when a user connects (or holds) the card to a reader. If the class and subclass information of these devices is the same as that of the USB keyboard, it is handled as a general character input device in the same manner as the USB keyboard. As a result, highly confidential information such as the user's card ID is displayed as it is on the input character display unit of the MFP as input characters, which may cause leakage of security information.

  Therefore, the present invention has been made in view of the above problems, and when a USB device is connected to the MFP, an image forming apparatus and information capable of making a flexible determination on the use of the connected USB device. It is an object to provide a processing method and an information processing program.

  An image forming apparatus according to an aspect of the present invention includes a management table indicating whether a USB device can be used in association with a vendor ID and / or product ID of a USB device connectable via a USB interface, and class information and subclass information. Storage means for storing; information acquisition means for acquiring the vendor ID and / or product ID of the USB device connected via the USB interface; class information and subclass information; and information acquired by the information acquisition means Determination means for determining use of the connected USB device based on the management table, wherein the determination means is information that is not stored in the management table. If there is, the vendor ID of the acquired information, or Same vendor ID as Rodakuto ID, or to the product ID, determines the number stored as use permission by the management table is equal to or greater than a predetermined number, and use permission of the connected USB device.

  The information processing method according to another aspect of the present invention indicates whether or not the USB device can be used in association with a vendor ID and / or product ID of a USB device connectable via a USB interface, and class information and subclass information. An information processing method in an image forming apparatus having a management table, the information acquisition step of acquiring a vendor ID and / or product ID, class information and subclass information of a USB device connected via the USB interface; A determination step for determining use of the connected USB device based on the information acquired in the information acquisition step and the management table, wherein the determination step includes the information acquired in the information acquisition step; Stored in the management table If the number stored as the use permission in the management table for a vendor ID or product ID that is the same as the vendor ID or product ID of the acquired information is a predetermined number or more, It is determined that the connected USB device is permitted to be used.

  The image forming apparatus and the information processing method of the present invention can be realized by a program that can be executed by a computer, and can also be realized by causing a computer to read a recording medium that records the program.

  According to the present invention, when a USB device is connected to the MFP, it is possible to make a flexible determination on the use of the connected USB device.

FIG. 2 is a block diagram illustrating an example of a hardware configuration of the MFP according to the embodiment. FIG. 2 is a schematic diagram illustrating a basic module configuration of an MFP according to an embodiment. The figure which shows an example of a USB device descriptor. The figure which shows Example 1 of a USB device management table. The figure which shows Example 2 of a USB device management table. FIG. 3 is a block diagram illustrating an example of a functional configuration of the MFP according to the embodiment. FIG. 6 is a diagram illustrating a control sequence when the USB application is activated in the MFP according to the embodiment. The flowchart which shows an example of a process of USB device management service.

  Embodiments relating to the image forming apparatus of the present invention will be described below. In this embodiment, as a device having a configuration applicable to a printer device, an MFP, or the like, an image formation capable of using a USB device according to the present invention (a device connected from the outside via a USB I / F) is possible. An example of an apparatus is illustrated.

<Hardware configuration>
FIG. 1 is a block diagram illustrating an example of a hardware configuration of the MFP 1 according to the embodiment. As shown in FIG. 1, the MFP 1 includes a control unit 2, a main storage unit 3, an auxiliary storage unit 4, an external storage device I / F unit 5, a network I / F unit 6, an operation unit 7, a display unit 8, and an engine unit. 9 is included.

  The control unit 2 is a CPU that controls each device, calculates data, and processes in a computer. The control unit 2 is an arithmetic device that executes a program stored in the main storage unit 3. The control unit 2 receives data from the input device or the storage device, calculates and processes the data, and outputs the data to the output device or the storage device.

  The main storage unit 3 is a ROM (Read Only Memory), a RAM (Random Access Memory), or the like, and a storage device that stores or temporarily stores programs and data such as an OS and application software that are basic software executed by the control unit 2 It is.

  The auxiliary storage unit 4 is an HDD (Hard Disk Drive) or the like, and is a storage device that stores data related to application software and the like.

  The external storage device I / F unit 5 is an interface between the MFP 1 and a storage medium 15 (for example, a flash memory) connected via a data transmission path such as USB (Universal Serial Bus).

  Also, a predetermined program is stored in the storage medium 15, the program stored in the storage medium 15 is installed in the MFP 1 via the external storage device I / F unit 5, and the installed predetermined program is executed by the MFP 1. It becomes possible.

  The network I / F unit 6 is a peripheral having a communication function connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network) constructed by a data transmission path such as a wired and / or wireless line. This is an interface between the device and the MFP 1.

  The operation unit 7 and the display unit 8 are composed of a key switch (hard key) and an LCD (Liquid Crystal Display) having a touch panel function (including GUI software key: Graphical User Interface), and use the functions of the MFP 1 It is a display and / or input device that functions as a UI (User Interface).

  The engine unit 9 is a mechanical part such as a plotter or a scanner that actually performs processing relating to image formation.

<Module configuration>
FIG. 2 is a schematic diagram illustrating a basic module configuration of the MFP 1 according to the embodiment. The hardware configuration includes a USB device 17 as an element related to the present invention, in addition to a plotter engine 10 and an engine control board 11 necessary for image forming processing, in a configuration section shown as an engine (plotter) in FIG.

  The engine control board 11 is equipped with a CPU 2 for controlling the entire apparatus. The CPU 2 controls processing means such as a plotter engine 10 provided in the apparatus and a USB device 17 connected via the USB I / F in order to perform image forming processing according to a program provided by a software configuration described later. Realize the desired function.

  In the USB device 17, a USB device class driver is incorporated as software for driving the USB device in response to software on the apparatus main body, which will be described later. And respond with descriptor information.

  As shown in the module configuration of FIG. 2, the software configuration is roughly divided into an application layer and a service layer. The application layer includes a printer application 51 which is a page description language and a printer application, and performs processing specific to the user service related to the MFP 1.

  The printer application 51 receives print data from a service layer module (described later) that provides a connection function with an external I / F such as the network management service 32, interprets the language, and develops the image data. The developed image data is transferred to the plotter engine 10 through the engine I / F 13 and printed out.

  In the embodiment, the operation in the confidential print mode is possible, and if the print data is instructed to be confidential print, the print data is not immediately output, but is temporarily stored in an external storage device such as an HDD. Thereafter, a password input from an operation panel processing module 53 (to be described later) is accepted. If the password matches the password in the print data, the print data temporarily stored in the HDD is expanded and the print output is executed.

  The operation panel processing module 53 is configured as a part of the printer application 51 in the embodiment. This is a module that controls the operation keys / buttons and various displays / display panels for inputting settings such as printing conditions from the operation panel of the MFP 1. When confidential printing is designated, it has a function of displaying a screen that prompts the user to input a password.

  In addition, a USB application (hereinafter also referred to as a USB application) 57 is installed in the application layer as an element related to the present invention. The USB application 57 is a module for analyzing data of the connected USB device 17 and providing a function specialized for the device. When the USB device 17 is not connected, the USB application 57 is not activated to save virtual memory on the system, but is activated by the USB device management service 37 when the USB device 17 is connected.

  The USB application 57 provides a function of acquiring an input from the USB device 17 connected via the USB I / F and transmitting the input to the printer application 51. In addition, the MFP 1 includes other applications such as a copy, a fax, and a scanner, but these applications are not always necessary.

  In the service layer, management of the network management service 32, the memory management service 33, and the USB device management service 37 as elements related to the present invention, which interpret the processing requests from the application layer and generate acquisition requests for each hardware resource A service, a system management service 31 that arbitrates acquisition requests from the management service, an operating system (OS) 20, and a USB device management table 38.

  The service layer has a GW-API (application program interface) 55 that enables a processing request from the application layer to be received by a predefined function.

  The OS 20 executes each management service and each software of the application layer in parallel as a process, and realizes the function of the host controller and the USB host controller 27 as an element related to the present invention on the OS 20. The host controller controls the physical device on the host side and provides a logical data bus with the device.

  The USB device management service 37 exists as a resident daemon in the software configuration of the MFP 1. When the USB device management service 37 resident as a daemon is activated, the USB application 57 registers a pair of an application ID owned and an available USB device descriptor through the API 55 provided by the daemon in the daemon. The USB device descriptor is acquired from the device class driver of the USB device 17 every time the USB device is connected.

  Each time the daemon receives a registration request from the USB application 57, the daemon updates a USB device management table (hereinafter also referred to as a management table) 38, and stores information related to the USB application 57 and descriptor information. In the management table 38, device class information that characterizes the USB device, device ID, and the like, and information indicating the relationship between the application program used for the device and the availability of the application are described.

  The USB device management service 37 stores and manages the management table 38 in a nonvolatile storage location. Therefore, when the USB device 17 is next connected, the use of the USB application 57 corresponding to the connected device can be determined by referring to the management table 38.

  FIG. 3 is a diagram illustrating an example of a USB device descriptor. As shown in the example of FIG. 3, the USB device descriptor describes the definition of the operation and function of the USB device 17. Configuration is performed by the USB host controller 27 in accordance with the contents of the USB device descriptor, and conditions for enabling communication between the connected USB device 17 and the USB host controller 27 are set.

  In addition, as shown in the example of FIG. 3, the USB device descriptor has information such as device class and device subclass, so it is possible to specify the device actually used in the subclass of the abstracted USB device. become. In the embodiment, in order to handle at the interface level, the interface device class and subclass are referred to as shown in the example of FIG.

  Further, as shown in the example of FIG. 3, it is also possible to specify the vendor ID, product ID, and device release number (ID) from the USB device descriptor.

  Here, the meaning of each information will be described. The class information is information indicating the type of UBS interface that the device has. For example, HID (Human interface device) such as a keyboard and mouse and MSD (Mass Storage Device) such as a USB flash memory are class information.

  The subclass information is supplementary information of information indicating the type of USB interface possessed by the device. For example, when the class information is HID, a keyboard and a mouse are subclass information.

  The vendor ID is a unique identifier indicating the manufacturer of the USB device. The product ID is a unique identifier indicating the model number of the USB device. The device release number is a unique identifier indicating the firmware version of the USB device.

  The management table 38 manages a flag for determining whether or not the connected USB device can be used by using at least one of device class information and subclass information that characterizes the USB device 17 and vendor ID and product ID.

  Here, an example of the USB device management table 38 will be described with reference to FIGS. 4 and 5. FIG. 4 is a diagram illustrating Example 1 of the USB device management table. As shown in FIG. 4, the management table 38 associates the class, subclass, and vendor ID of the USB device 17 and manages whether the USB device 17 can be used.

  In the example shown in FIG. 4, there are “CANDIDATE” and “IGNORE” as flags indicating availability (hereinafter, used flags). “CANDIDATE” means that activation of the USB application 57 is permitted. “IGNORE” means that activation of the USB application 57 is not permitted.

  For example, when the class is “HID”, the subclass is “Keyboard”, and the vendor ID is “0x1234”, the usage flag is “CANDIDATE”, so the USB device 17 activates the KB (Keyboard) input support application. Can be used.

  Even with the same class information and subclass information, when the vendor ID is “0x4321”, the use flag is “IGNORE”, so the USB device 17 cannot activate the KB input support application. The vendor indicated by the vendor ID “0x4321” is effective when it is not desired to connect the USB device created by the vendor because of low reliability.

  The vendor ID shown in FIG. 4 may be a product ID. When the product ID is set, it is possible to determine whether the USB application can be used for each product. In addition, since the same ID may be given between different vendors using only the product ID, the vendor ID and product ID may be managed in the management table 38 in association with other information. This makes it possible to determine whether or not the USB device can be used more flexibly.

  FIG. 5 is a diagram illustrating Example 2 of the USB device management table. As shown in FIG. 5, the management table 38 associates the class, subclass, vendor ID, product ID, and device release number of the USB device 17 to manage the usability of the USB device 17. In the example illustrated in FIG. 5, the usage flag includes “ONLY”. The meaning of “ONLY” means that only the USB device 17 is permitted to be used.

  For example, one “ONLY” can be set for a USB device whose class is “HID”, and only one USB device can be used. It is also possible to set “ONLY” for each subclass and allow one USB device for each subclass.

  Therefore, when “ONLY” is registered in the management table 38, use permission is determined for the device information “ONLY”. In the example shown in FIG. 5, since the device release number is used, it is possible to determine in detail whether or not the same product can be used depending on the version.

  If the use is permitted using the management table (see FIG. 4 or FIG. 5) when the USB device is connected, the USB application 57 corresponding to the connected device is activated.

  That is, when the USB device 17 is connected to the apparatus main body, the USB host controller 27 detects that the USB device 17 is connected, and makes a request to acquire the USB device descriptor to the detected USB device 17. In response to this request, the USB device descriptor sent by the USB device class driver of the USB device 17 is acquired on the host side.

  Next, the USB device management service 37 resident as a daemon manages device information (class information, subclass information, vendor ID, etc.) described in the USB device descriptor acquired by the USB host controller 27 in the daemon. Is registered in the management table (see FIG. 4 or 5).

  When the information matches the “device class” and “device subclass” described in the management table 38, information indicating the USB application 57 associated with the device information is acquired from the management table 38 and registered in advance. The USB application 57 is notified of the connection of the USB device 17.

  The USB application 57 can execute various initialization processes in response to the connection notification of the USB device 17.

  Following the initialization process, the USB device management service 37 constructs a data bus for data transmission / reception based on the USB device descriptor. As the data bus, Unix (registered trademark) domain socket, general-purpose IPC (Inter process Communication), and the like can be considered. Note that a general-purpose Mass Storage Class driver and Printer Class Driver are prepared inside the daemon in the embodiment, and these functions are provided to the upper USB application 57 simultaneously with the connection of the USB device 17. Can be provided.

<Functional configuration>
Next, a schematic functional configuration of the MFP 1 according to the present invention will be described. FIG. 6 is a block diagram illustrating an example of a functional configuration of the MFP 1 in the embodiment. As shown in FIG. 1, the USB application 57 includes a display control unit 501, and the USB device management service 37 includes an information acquisition unit 301 and a determination unit 302.

  The information acquisition unit 301 acquires device information of the USB device descriptor from the USB host controller 27. The information acquisition unit 301 may acquire the device information registered in the management table 38. For example, in the management table shown in FIG. 4, the information acquisition unit 301 acquires class information, subclass information, and vendor ID. In the management table shown in FIG. 5, the information acquisition unit 301 acquires class information, subclass information, vendor ID, product ID, and device release number.

  The determination unit 302 refers to the management table 38 using the device information acquired by the information acquisition unit 301, and determines whether the connected USB device 17 is usable. The determination unit 302 compares the acquired device information with the device information stored in the management table 38 to determine whether they match. The determination unit 302 determines that the use is possible when the use flag associated with the matched device information is “CANDIDATE” or “ONLY”, and identifies an application that issues a connection request.

  The USB device management service 37 activates the USB application 57 specified from the management table 38. Which USB application 57 should be activated can be known by referring to the management table 38. The display control unit 501 of the USB application 57 performs display control of information acquired from the USB device 17 on the operation panel (display unit 8) of the MFP 1. Further, the display control unit 501 does not display information related to the USB device 17 determined to be unusable by the determination unit 302 (for example, stored information) on the display unit 8 of the MFP 1.

Further, when the device information acquired from the USB host controller 27 is not stored in the management table 38, the determination unit 302 determines that the use is permitted by satisfying the following condition, and stores this device information in the management table 38. sign up.
(1) A predetermined number or more of vendor IDs that are the same as the acquired vendor IDs are registered in the management table 38 as being usable. (2) A predetermined number or more of the product IDs that are the same as the acquired product IDs are being used in the management table 38. It is registered.

  If the determination unit 301 determines that one or both of the conditions (1) and (2) are satisfied, the determination unit 301 determines that the USB device can be used. This is because if a certain number of vendor IDs are registered in the management table 38 so as to be usable, this vendor can be determined as a reliable vendor.

  Further, the determination unit 301 stores the device information of the USB device 17 in the management table 38 with the usable flag as “CANDIDATE”. Accordingly, it can be determined that the USB device 17 can be used smoothly when the USB device 17 is next connected.

<Specific example>
Next, a specific example in which a USB keyboard is connected as the USB device 17 so that input support can be performed will be described.

  Conventionally, there is an example in which an operation panel is composed of several LCD (Liquid Crystal Display) panels and several buttons. When such a poor UI (user interface) is used, it is possible to prevent a bad USB keyboard from being determined to be usable when a USB keyboard is connected as a USB device to support input. The poor keyboard stores device information and a use flag “IGNORE” in the management table 38.

  In the specific example, the USB keyboard having the hardware configuration shown in FIG. 2 is a USB device (corresponding to the USB device 17 shown in FIG. 2). Further, the keyboard input support application having a software configuration is a USB application (corresponding to the USB application 57 shown in FIG. 2).

  The keyboard input support application is not activated in order to save virtual memory on the system when the USB keyboard is not connected. However, when the USB keyboard is connected, the determination by the determination unit 302 is performed, and the USB device management service 37 resident as a daemon is activated when the use is permitted. In addition, a function of acquiring an input made by the operator from a USB keyboard connected via the USB I / F and transmitting the input to the operation panel processing module 53 is provided. In addition, when the use is not possible as a result of the use determination by the determination unit 302, the keyboard input support application is not activated.

  The operation panel processing module 53 cooperating with the keyboard input support application accepts the keyboard input support application, processes the acquired character input through a communication path established with this application, and functions as a UI. Display on the panel.

  In addition, it has a function of receiving input such as the Enter key of a USB keyboard and completing input processing.

  As another specific example, a USB flash memory as the USB device 17 and a SCSI application as the USB application 57 can be considered. In this case, when the USB flash memory is connected to the MFP 1, the use determination by the determination unit 302 is performed as described above, and the SCSI application is activated by the USB device management service 37 when the use is permitted. As a result, data stored in the USB flash memory can be read and written.

  On the other hand, if the use is not possible as a result of the use determination by the determination unit 302, the SCSI application is not activated. Therefore, it is impossible to read and write data from the USB flash memory. As a result, if a low-quality USB flash memory is known, its use can be prevented in advance.

  As another specific example, the USB device 17 is an IC card, the class information of this IC card is HID, and the subclass information is a keyboard. Conventionally, this IC card is permitted to be used as a USB keyboard, and personal information is displayed on the display unit 8. In the present invention, the product ID of the IC card is stored in the management table 38 as a use flag “IGNORE”. Thus, when a USB device having secret information such as an IC card whose class information is HID and subclass information is a keyboard is connected, it is possible to prevent the secret information from being displayed on the display unit 8.

  The use flag described above indicates whether or not the USB device can be used. However, whether or not information from the USB device is displayed on the display unit 8 (for example, whether or not information from the IC card is displayed on the display unit 8). It may be a flag indicating whether data can be input from and / or output from the USB device (in the case of a USB flash memory, read / write).

<Operation>
Next, the operation of the MFP in the embodiment will be described. FIG. 7 is a diagram illustrating a control sequence when the USB application 57 is activated in the MFP 1 according to the embodiment. Hereinafter, the control operation when the USB application 57 is started will be described according to the sequence shown in FIG.

  When the USB device 17 is connected to the apparatus main body in step S101, the OS 20 functioning as a host controller first makes a descriptor acquisition request to the USB device 17. In response to this request, the device driver of the USB device 17 transmits the descriptor information to the OS 20.

  In step S102, the USB device management service 37 as a resident daemon monitors the connection processing performed by the OS 20, and when the OS 20 acquires the descriptor, the USB device 17 detects the acquired descriptor of the USB device 17.

  In step S103, the USB device management service 37 acquires device information whose use flag is “ONLY” in the management table 38, and collates it with the device information of the descriptor detected in step S102. If the collation results match, the process proceeds to step S106, and if not, the process proceeds to step S104.

  In step S104, the USB device management service 37 acquires device information whose use flag is “IGNORE” in the management table 38, and collates it with the device information of the descriptor detected in step S102. If the collation results match, the process is terminated as unusable, and if not, the process proceeds to step S105.

  In step S105, the USB device management service 37 acquires device information whose use flag is “CANDIDATE” in the management table 38, and collates it with the device information of the descriptor detected in step S102. If the collation results match, the process proceeds to step S106, and if not, the process ends. If the collation result does not match in step S105, use condition determination processing described later may be performed.

  In step S106, if the USB device management service 37 determines that the USB device 17 is permitted to be used as a result of the collation, the USB device management service 37 acquires an application ID associated with the device information. Next, the USB device management service 37 notifies the USB application 57 having the application ID registered in advance of the connection of the USB device 17. The USB application 57 receives the connection notification of the USB application 57 and activates the application.

  The USB application 57 performs an operation corresponding to the input of the USB device 17 as an operation according to the application program after the initialization process at the time of activation as follows.

  In step S107, when data is input from the USB device 17 (for example, operation input in the case of a keyboard), the operation input is accepted by the OS 20.

  In step S108, the USB application 57 detects an input accepted by the OS 20.

  In step S <b> 109, the USB application 57 transmits the input character string data detected via the OS 20 to the operation panel processing module 53 of the printer application 51.

  In step S110, the operation panel processing module 53 that receives the input character string data displays the received data through the display panel on the UI.

  For example, when the USB device 17 is a USB keyboard and the USB application 57 is a keyboard input support application, when inputting a password from the USB keyboard, a sequence similar to steps S107 to S110 is performed in order of a character string consisting of a predetermined number of characters one by one. To support the UI in the password check process.

  In the above example, the example in which required device information is obtained from the management table 38 and collated with the detected device information has been described. However, the management table 38 indicates whether there is the same information as the detected device information. Corresponding device information may be searched in the order of “ONLY”, “IGNORE”, and “CANDIDATE”.

  Next, usage condition determination processing by the USB device management service 37 will be described. FIG. 8 is a flowchart illustrating an example of processing of the USB device management service 37. In the process shown in FIG. 8, when the device information is not stored in the management table 38 (if it is unknown data), the use determination is performed on the unknown device information from the information stored in the management table 38. .

  In step S201, the USB device management service 37 refers to the management table 38, and is the same as the vendor ID of the device information detected in step S102 and can be used (the use flag is “ONLY” and “CANDIDATE”). The number of vendor IDs is counted.

  In step S202, the USB device management service 37 determines whether the number counted in step S201 is a predetermined value or more. The usage condition here is that the count value in step S201 is equal to or greater than a predetermined value. As other usage conditions, it is conceivable that any combination of information among the device information satisfies a predetermined condition. For example, the use condition may be that the class information and the vendor ID are the same as the preset information.

  If the determination result in step S202 is YES, the process proceeds to step S203, and if the determination result is NO, the process ends. The predetermined value for the count is set in advance by the user.

  In step S <b> 203, the USB device management service 37 stores the detected device information in the management table 38. At this time, the use flag is set to “CANDIDATE”. Further, it may be stored as “ONLY” by user setting.

  In step S204, the USB device management service 37 activates the corresponding USB application 57 based on the related class information and subclass information. At this time, if there is no corresponding application, a startable application may be displayed on the display unit 18 and may be selected by the user.

  As a result, even if the device information not stored in the management table 38 is acquired by the USB device management service 37, the use determination can be performed based on the data stored in the management table 38.

  As described above, according to the embodiment, when a USB device is connected to the MFP, it is possible to make a flexible determination on the use of the connected USB device. Further, according to the embodiment, even if an unknown USB device stored in the management table is connected, it is possible to determine whether to use the unknown USB device based on the device information stored in the management table. .

  Note that the processing contents described in the embodiments may be a program for causing a computer to execute the program, and the program may be executed by the computer to cause the image forming apparatus to perform the above-described processing. It is also possible to record the program on a recording medium and cause the computer to read the recording medium on which the program is recorded, thereby causing the image forming apparatus to perform the processing described above.

  In addition, this invention is not limited to the said Example as it is, A component can be deform | transformed and embodied in the range which does not deviate from the summary in an implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiments. Furthermore, constituent elements over different embodiments may be appropriately combined.

10 Plotter Engine 11 Engine Control Board 17 USB Device 20 OS
27 USB host controller 31 System management service 32 Network management service 33 Memory management service 37 USB device management service 38 USB device management table 51 Printer application 53 Operation panel processing module 57 USB application 301 Information acquisition means 302 Determination means 501 Display control means

JP 2006-239969 A

Claims (5)

Storage means for storing a management table indicating whether or not the USB device can be used in association with a vendor ID and / or product ID of a USB device connectable via a USB interface, and class information and subclass information;
Information acquisition means for acquiring a vendor ID and / or product ID, class information and subclass information of a USB device connected via the USB interface;
Determination means for determining use of the connected USB device based on the information acquired by the information acquisition means and the management table;
The determination means includes
If the information acquired by the information acquisition means is information not stored in the management table, the vendor ID of the acquired information, or the same vendor ID or product ID as the product ID, in the management table An image forming apparatus that determines that the connected USB device is permitted to be used when the number stored as the permission for use is equal to or greater than a predetermined number. The determination means includes
When the information acquired from the acquisition means is information that is not stored in the management table, and when it is determined that use is permitted, the acquired information is stored in the management table as permission for use of the management table. The image forming apparatus according to claim 1. The management table is
The image forming apparatus according to claim 1, wherein device release information is further associated with availability of the USB device. An information processing method in an image forming apparatus having a management table indicating whether or not a USB device can be used in association with a vendor ID and / or product ID of a USB device connectable via a USB interface, and class information and subclass information. ,
An information acquisition step of acquiring a vendor ID and / or product ID of the USB device connected via the USB interface, and class information and subclass information;
A determination step of determining use of the connected USB device based on the information acquired by the information acquisition step and the management table;
The determination step includes
When the information acquired by the information acquisition step is information not stored in the management table, the vendor ID of the acquired information, or the same vendor ID or product ID as the product ID, in the management table An information processing method for determining that the connected USB device is permitted to be used if the number stored as the permission for use is equal to or greater than a predetermined number. Information processing program executed in an image forming apparatus having a management table indicating whether or not a USB device can be used in association with a vendor ID and / or product ID of a USB device connectable via a USB interface, and class information and subclass information Because
An information acquisition step of acquiring a vendor ID and / or product ID of the USB device connected via the USB interface, and class information and subclass information;
A determination step of determining use of the connected USB device based on the information acquired by the information acquisition step and the management table;
The determination step includes
When the information acquired by the information acquisition step is information not stored in the management table, the vendor ID or product ID of the acquired information is a vendor ID or product indicating use permission in the management table An information processing program that determines that a connected USB device is permitted to be used if the number of IDs is a vendor ID or product ID equal to or greater than a predetermined number.

Images