JP4444979B2 - Information processing device - Google Patents

Description

  The present invention relates to an image forming apparatus such as a scanner / printer / copy / facsimile / multifunction machine / multifunction machine, a storage apparatus, an information processing apparatus such as a personal computer / server computer, and an image processing apparatus. The present invention relates to an information processing apparatus.

The OA device executes document processing (image forming processing) in various forms. For example, a scanner reads document data (image data) from a read original, a printer prints document data (image data) on a print sheet, and a copy reads document data (image data) from a read original on a print sheet. In the facsimile, document data (image data) is transmitted / received via a telephone line. Document data (image data) to be printed on printing paper by a printer is created by, for example, document application software such as word processor software or spreadsheet software.
Japanese Patent Laid-Open No. 7-314783

  In recent years, networking of OA devices has been progressing rapidly. In order to appropriately cope with such a situation, “BMLinkS” has been proposed as a standard specification regarding an integrated interface of OA equipment. In BMLinkS, a search method (Discovery) for OA devices, a data format (Data Format) exchanged between OA devices, a control method for OA devices (Job / Device Control), and the like are standardized.

  In BMLinkS, the function of an OA device is modeled as an office service. The scan function of OA equipment is a scan service, the print function of OA equipment is a print service, the fax input function of OA equipment is a fax-in service, the fax output function of OA equipment is a fax-out service, and the storage function of OA equipment is modeled as a storage service. It becomes. As a result, a scanner usually has a scan service, a printer has a print service, a copy has a scan service and a print service, a facsimile has a fax-in service and a fax-out service, and a storage apparatus has a storage service. Commands such as create_job (job creation request) and list_jobs (job list request) are defined for the scan service and print service, and create_file (file creation request / data storage request) and list_files (file list) for the storage service. Commands such as request / data list request), read_data (data read request), and write_data (data write request) are defined. In BMLinkS, HTTP-SOAP is used as a network protocol.

  In a client terminal of an OA device functioning as a scanner, it is usually possible to set scanning conditions such as a reading size, a reading direction, a reading surface, and a reading resolution when the OA device executes a scanning process. However, what scanning conditions are supported by the OA device, such as a certain OA device supports the reading size “A4” and a certain OA device supports the reading sizes “A4” and “A3”. Is different for each OA device. Therefore, when it is desired to cause the OA device to execute scan processing under a desired scan condition, it is necessary to cause the OA device that supports the scan condition to execute scan processing. However, in a client terminal of an OA device functioning as a scanner, an OA device that performs a scanning process is usually selected by manual selection or default selection. However, an OA device selected by manual selection or default selection satisfies a desired scanning condition. Not necessarily supported. For this reason, a user who wants the OA device to execute a scan process under a desired scan condition needs to identify himself / herself an OA device that supports the scan condition. There is such a problem in the operability of a series of operations for causing the OA device to execute a scan process.

  In addition, in a client terminal of an OA device functioning as a printer, it is usually possible to perform an operation for setting print conditions such as a print size, a print orientation, a print surface, and a print resolution when the OA device executes print processing. However, what printing conditions the OA device supports, such as a certain OA device supporting the print size “A4” and a certain OA device supporting the print sizes “A4” and “A3”. Is different for each OA device. Therefore, when it is desired to cause the OA device to execute print processing under desired print conditions, it is necessary to cause the OA device that supports the print condition to execute print processing. However, in a client terminal of an OA device functioning as a printer, an OA device that executes print processing is normally selected by manual selection or default selection. However, an OA device selected by manual selection or default selection satisfies desired print conditions. Not necessarily supported. For this reason, a user who wants the OA device to execute a print process under a desired print condition has to identify the OA device that supports the print condition. There is such a problem in the operability of a series of operations for causing the OA device to execute print processing.

  By the way, when the OA device executes the scan processing, it is convenient if the OA device can subsequently execute the image data print processing related to the scan processing. However, in this case, as is apparent from the above description, in addition to the OA device selection process and scan condition setting process for executing the scan process, the OA device selection process and print condition setting process for executing the print process are performed. It becomes a problem. Similarly, when the OA device executes the scan process, it is convenient if the OA device can subsequently execute the image data storage process related to the scan process.

  It is an object of the present invention to provide an information processing apparatus that improves the operability of a series of operations for causing an OA apparatus to execute a scan process, with respect to an information processing apparatus that functions as a client terminal of an OA apparatus that functions as a scanner. To do.

  The present invention also relates to an information processing apparatus functioning as a client terminal of an OA device functioning as a scanner, causing the OA device to execute a scan process, and causing the OA device to perform print processing and storage processing of image data related to the scan process. It is an object of the present invention to provide an information processing apparatus that improves the operability of a series of operations for execution.

  In addition, as a problem associated with the networking of OA devices, securing the security of OA devices can be cited. Therefore, in order to ensure the security of the OA device, it is desirable to execute an authentication process when a client of the OA device accesses the OA device. In such a case, how to obtain authentication information, how to exchange authentication information between devices, what is the desire to ensure the security of OA devices and what is the desire to freely access OA devices How to make them compatible is a problem. In BMLinkS, in particular, compatibility with the BMLinkS concept of being connected anytime and anywhere, compatibility with the standard specification of BMLinkS, and the like become problems.

  It is an object of the present invention to propose a new information processing apparatus related to an authentication process executed when a client of an OA device accesses the OA device.

The present invention is an information processing apparatus functioning as a client of the image forming apparatus, against the server of the image forming apparatus or the image forming apparatus, and the command issuing means for issuing a command of a print job, the authentication on the command Authentication information insertion means for inserting information, and printing is performed in accordance with the policy printing conditions permitted by the image forming apparatus when authentication is not permitted in the authentication processing based on the authentication information inserted in the command. The image forming apparatus is caused to execute a print job by the command modified to execute the job .

Further, the present invention is an information processing apparatus functioning as a client of the image forming apparatus, the against the server of the image forming apparatus or the image forming apparatus, and the command issuing means for issuing a command of a scan job, the command Authentication information inserting means for inserting authentication information into the command, and if authentication is not permitted in the authentication processing based on the authentication information inserted in the command, the policy scanning condition permitted by the image forming apparatus is met. Then, the image forming apparatus is caused to execute a scan job by the command modified so that the scan job is executed .

In addition, the present invention is an information processing apparatus that functions as a proxy server for a client of an image forming apparatus, wherein the image forming apparatus issued by the client of the image forming apparatus or a print job for the server of the image forming apparatus An authentication information insertion unit that inserts authentication information into a command, and a print job that matches a policy printing condition permitted by the image forming apparatus when authentication is not permitted in the authentication process based on the authentication information inserted into the command. Command transfer means for correcting the command so that the command is executed and transferring the corrected command to the image forming apparatus .

In addition, the present invention is an information processing apparatus that functions as a proxy server for a client of an image forming apparatus, wherein the image forming apparatus issued by the client of the image forming apparatus or a scan job for the server of the image forming apparatus An authentication information insertion unit that inserts authentication information into a command, and a scan job that matches a policy scan condition permitted by the image forming apparatus when authentication is not permitted in the authentication process based on the authentication information inserted into the command. And a command transfer means for correcting the command so that the command is executed and transferring the corrected command to the image forming apparatus .

In the present invention, when authentication is permitted in the authentication process based on the authentication information inserted in the command, it is determined that the user has authority to access the image forming apparatus based on the authentication information included in the command. The print job is executed only when the print job is executed .

In the present invention, when authentication is permitted in the authentication process based on the authentication information inserted in the command, it is determined that the user has authority to access the image forming apparatus based on the authentication information included in the command. In this case, the scan job is executed .

In the present invention, the authentication information inserting means inserts authentication information into the command using a tag.

In the present invention, the authentication information is authentication information acquired by screen input, authentication information acquired by reading a storage medium, or authentication information acquired by biometric authentication.

In the present invention, the command is a command described by XML (extensible Markup Language).

In the present invention, the command is a job generation request command for generating a job.

In the present invention, the authentication process is performed by a server separate from the proxy server.

In the present invention, the policy printing conditions are managed by a server separate from the information processing apparatus.

In the present invention, the policy scan condition is managed by a server separate from the information processing apparatus.

  It is possible to propose a new information processing apparatus related to the authentication process executed when the client of the OA device accesses the OA device.

  Examples of the present invention will be described.

  Examples of the present invention will be described.

  1 and 2 are device arrangement diagrams relating to a PC (personal computer) 301 corresponding to an embodiment of the present invention. The PC 301 in FIG. 1 and the PC 301 in FIG. 2 are the same device, FIG. 1 is a device layout diagram related to a plurality of scanners 101 connected to the PC 301, and FIG. 2 shows a plurality of printers 201 connected to the PC 301. FIG. 1 and 2 is an information processing apparatus that functions as a client terminal of each scanner 101 in FIG. 1 and each printer 201 in FIG.

  In the device layout diagram of FIG. 1, scanners 0, 1, 2, 3L, 3M1, 3M2, and 3M3 are connected to a PC 301. In the device arrangement diagram of FIG. 1, the scanners 3L, 3M1, 3M2, and 3M3 constitute a group scanner 3 having the scanner 3L and the scanners 3M1, 3M2, and 3M3 as group leaders and group members, respectively.

  The PC 301 automatically detects the connection with the scanner 0, the scanner 1, the scanner 2, and the group scanner 3, and generates the logical scanner 0, the logical scanner 1, the logical scanner 2, and the logical scanner 3. The logical scanners 0, 1, and 2 are objects that correspond to the scanners 0, 1, and 2, respectively, and the scanning conditions supported by the scanners 0, 1, and 2 are the logical scanners 0, 1, 2, respectively. Are managed as attributes. The logical scanner 3 is an object that corresponds to the group scanner 3 on a one-to-one basis, and the scanning conditions supported by the scanners 3L, 3M1, 3M2, and 3M3 constituting the group scanner 3 are grouped as attributes of the logical scanner 3. Managed.

  The PC 301 creates a scan condition base using a logical scanner and a fixed condition, and provides a scanner operation UI (user interface) using the scan condition base. Therefore, the user recognizes the scanners 3L, 3M1, 3M2, and 3M3 as one scanner. By utilizing this, for example, by allowing the user to recognize the scanners installed close to each other as one scanner, the operability of the scanner operation UI can be improved. Details of the logic scanner, fixed conditions, and scan condition base will be described later.

  In the device layout diagram of FIG. 2, printers 0, 1, 2, 3L, 3M1, 3M2, and 3M3 are connected to a PC 301. 2, the printers 3L, 3M1, 3M2, and 3M3 constitute the group printer 3 having the printer 3L and the printers 3M1, 3M2, and 3M3 as group leaders and group members, respectively.

  The PC 301 automatically detects connection with the printer 0, the printer 1, the printer 2, and the group printer 3, and generates the logical printer 0, the logical printer 1, the logical printer 2, and the logical printer 3. The logical printers 0, 1, and 2 are objects that correspond one-to-one with the printers 0, 1, and 2, respectively. Are managed as attributes. The logical printer 3 is an object that corresponds to the group printer 3 on a one-to-one basis, and print conditions supported by the printers 3L, 3M1, 3M2, and 3M3 constituting the group printer 3 are collected as attributes of the logical printer 3. Managed.

  The PC 301 creates a print condition base using a logical printer and fixed conditions, and provides a user interface (UI) for printer operation using the print condition base. For this reason, the printers 3L, 3M1, 3M2, and 3M3 are recognized by the user as one printer. Utilizing this, for example, by letting the user recognize printers installed close to each other as one printer, the operability of the UI for printer operation can be improved. Details of the logical printer, fixed conditions, and print condition base will be described later.

  FIG. 3 is a hardware configuration diagram related to the PC 301 of FIGS. 1 and 2 includes a CPU 311, ROM 312, RAM 313, HDD (hard disk drive) 314, operation unit 321, display unit 322, communication unit 323, USB / IF 331, SCSI / IF 332, Centronics / IF 333, and the like. . These hardware components are connected to the system bus 341.

  The CPU 311 is hardware that executes various types of information processing. The ROM 312 is hardware in which the information processing program and the like are stored. The RAM 313 is the information processing memory. The HDD 314 is a storage for the above information processing, and is hardware in which the above information processing program and the like are stored.

  The operation unit 321 is hardware for a user to input to the PC 301, and includes a keyboard, a mouse, and the like. The display unit 322 is hardware for a user to obtain an output from the PC 301, and includes a display or the like. The communication unit 323 is hardware for connecting the PC 301 to a network such as Ethernet (registered trademark) or a telephone line, and includes a NIC, MODEM, or the like.

  The USB / IF 331 is an interface for connecting a cable compliant with the USB standard. The SCSI / IF 332 is an interface for connecting a cable compliant with the SCSI standard. The Centronics IF 333 is an interface for connecting a Centronics specification cable.

  FIG. 4 is a software configuration diagram related to the PC 301 in FIGS. 1 and 2 includes an application 401, a scan system 411, a print system 412, a storage system 413, and the like.

  The application 401 is an application for electronic document management, for example.

  The scan system 411 includes a scan system UI unit 421, a scanner search unit 422, a scan condition base creation unit 423, a scanner selection unit 424, a scanner driver unit 425, a port monitor unit 426, a network control unit 427, a print condition creation unit 431, and a printer. Functional blocks such as a selection request unit 432, a printer adaptation unit 433, a print request unit 434, and a data storage request unit 435 are provided.

  The scan system UI unit 421 is a functional block that provides a UI (user interface) for scanner operation. The scanner search unit 422 is a functional block that issues a scanner search request (broadcast) and executes scanner search (discovery). The scanner search unit 422 automatically detects connection with the scanners 0, 1, 2, etc., and generates logical scanners 0, 1, 2, etc. The scan condition base creation unit 423 is a functional block that creates a scan condition base that is a database related to the correspondence relationship between a scan condition and a scanner that supports the scan condition. The scan condition base creation unit 423 uses the logical scanners 0, 1, 2, etc. stored in the logical scanner data area 461 and the fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 462, A scan condition base 463 is created. The scanner selection unit 424 is a functional block that automatically selects a scanner that supports the scan conditions set by the scanner operation UI.

  The scanner driver unit 425 is a functional block that performs control for causing the scanner to execute scan processing. The port monitor unit 426 is a functional block that monitors the port to which the scanner is connected. The network control unit 427 is a functional block that performs communication control for performing data communication with the scanner via the network. The network control unit 427 includes BMLinkS, UPnP (Universal Plug and Play), SOAP (Simple Object Access Protocol), HTTP (HyperText Transfer Protocol), and TCP (Transmission Protocol UTP). Network protocols such as IP (Internet Protocol) are supported.

  The print condition creating unit 431 is a functional block that creates a print condition by diverting the scan condition set in the scanner operation UI to the print condition. The scan conditions are stored in the scan condition data area 464, and the print conditions are stored in the print condition data area 465. The printer selection request unit 432 is a functional block that requests the print system 412 to automatically select a printer that supports print conditions using the scan conditions set by the scanner operation UI. The printer matching unit 433 will be described later. The print request unit 434 is a functional block that requests the print system 412 to cause the printer to execute print processing. The data storage request unit 435 is a functional block that requests the storage system 413 to cause an OA device such as a scanner, printer, or storage device to execute data storage processing.

  The print system 412 includes functional blocks such as a print system UI unit 441, a printer search unit 442, a print condition base creation unit 443, a printer selection unit 444, a printer driver unit 445, a port monitor unit 446, and a network control unit 447.

  The print system UI unit 441 is a functional block that provides a user interface (UI) for operating the printer. The printer search unit 442 is a functional block that issues a printer search request (broadcast) and executes printer search (discovery). The printer search unit 442 automatically detects connection with the printers 0, 1, 2, etc., and generates logical printers 0, 1, 2, etc. The print condition base creation unit 443 is a functional block that creates a print condition base, which is a database related to the correspondence between the print conditions and the printer that supports the print conditions. The print condition base creation unit 443 uses the logical scanners 0, 1, 2, etc. stored in the logical printer data area 471 and the fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 472, A print condition base 473 is created. The printer selection unit 444 is a functional block that performs automatic selection of a printer that supports print conditions set using a printer operation UI and scan conditions set using a scanner operation UI.

  The printer driver unit 445 is a functional block that performs control for causing the printer to execute print processing. The port monitor unit 446 is a functional block that monitors the port to which the printer is connected. The network control unit 447 is a functional block that performs communication control for performing data communication with the printer via the network. The network control unit 447 includes BMLinkS, UPnP (Universal Plug and Play), SOAP (Simple Object Access Protocol), HTTP (HyperText Transfer Protocol), and TCP (Transmission Protocol UTP). Network protocols such as IP (Internet Protocol) are supported.

  The storage system 413 includes functional blocks such as a storage driver unit 451, a port monitor unit 452, and a network control unit 453.

  The storage driver unit 451 is a functional block that performs control for causing an OA device such as a scanner, printer, or storage device to execute data storage processing. The port monitor unit 452 is a functional block that monitors a port to which the OA device is connected. The network control unit 453 is a functional block that performs communication control for performing data communication with the OA device via the network. The network control unit 453 includes BMLinkS, UPnP (Universal Plug and Play), SOAP (Simple Object Access Protocol), HTTP (Hyper Text Transfer Protocol), TCP (Transmission Protocol UTP), and TCP (Transmission Protocol UTP). Network protocols such as IP (Internet Protocol) are supported.

(Image formation processing)
Based on the above description, the image forming process executed by the device group of FIGS.

  FIG. 5 is a flowchart relating to information processing executed by the PC 301 in FIGS. Step codes A, B, C, etc. in FIG. 5 correspond to codes A, B, C, etc., respectively, in FIG.

  In the PC 301, when a scan condition setting UI display request (Step A) is made from the application 401 to the scan system UI unit 421, the scanner search unit 422 executes scanner search (Step B), and the scan condition base creation unit 423. Thus, a scan condition base is created (step C), and the scan system UI unit 421 displays a screen (step A1) of a scan condition setting UI (see FIG. 21, which will be described later). In the scan condition setting UI, a scan condition setting operation (step A2) is input.

  In the PC 301, when a scanner selection UI display request (step D) is subsequently made from the application 401 to the scan system UI unit 421, the scanner selection UI (see FIG. 22; description will be described later) is performed by the scan system UI unit 421. Screen display (step D1) is performed. A scanner selection operation (step D2) is input through the scanner selection UI.

  In this way, the scan conditions are set by the scan condition setting UI (steps A, A1, A2), and the scanner is manually selected by the scanner selection UI (steps D, D1, D2). When the scanner is automatically selected, there is no need to go through steps D, D1, and D2. Subsequently, when a scan process start operation (step E) is input, the following information processing is executed.

  First, the PC 301 makes preparations for performing the scanning process.

  In the PC 301, when it is set to automatically select a scanner (branch 1), the scan condition set by the scan condition setting UI is stored in the scan condition data area 464 by the scan system UI unit 421 (step F). , And a scan condition storage notification (step G) is made from the scan system UI unit 421 to the application 401. In response to this, the PC 301 issues a scan execution request (step H) from the application 401 to the scan system UI unit 421, and the scanner selection unit 424 supports the scan conditions stored in the scan condition data area 464. Automatic scanner selection (step I) is performed. The PC 301 causes the scanner selected by automatic selection to execute scan processing under the scan conditions stored in the scan condition data area 464.

  Here, when a plurality of scanner candidates for executing the scanning process are automatically selected (branch 2), that is, a plurality of scanners that support the scan conditions stored in the scan condition data area 464 are automatically selected. In the case of (branch 2), the scanner selection UI (see FIG. 22, which will be described later) is displayed on the screen (step D1) by the scan system UI unit 421. A scanner selection operation (step D2) is input through the scanner selection UI. If there are not plural (branch 2), the scan system UI unit 421 displays a scanner selection result (see FIG. 23, which will be described later) on the screen (step D3).

  In the PC 301, when it is not set that the scanner is automatically selected (branch 1), the scanner is manually selected by the scanner selection UI (branch 3), and is manually selected by the scanner selection UI. On the condition that the scanned scanner supports the scan condition set by the scan condition setting UI (branch 4), the scan condition set by the scan condition setting UI by the scan system UI unit 421 is the scan condition data area 464. (Step F), and a scan condition storage notification (Step G) is sent from the scan system UI unit 421 to the application 401. In response to this, the PC 301 makes a scan execution request (step H) from the application 401 to the scan system UI unit 421. The PC 301 causes the scanner selected by manual selection to execute scan processing under the scan conditions stored in the scan condition data area 464.

  Further, the PC 301 appropriately prepares for performing the image data print processing related to the scan processing.

  In the PC 301, when it is set to execute the print processing of the image data related to the scan processing (branch 5), the print condition creation unit 431 prints the print condition diverted from the scan condition stored in the scan condition data area 464. Is created (step J) and stored in the print condition data area 465 (step K), and a print condition storage notification (step L) is sent from the print system UI unit 421 to the application 401. In response to this, the PC 301 issues a print execution request (step M) from the application 401 to the scan system UI unit 421, and the print condition stored in the print condition data area 465 from the printer selection request unit 432 to the print system 412. A request for automatic selection of a printer that supports (Step N) is made. In the print system 412, the automatic selection of the printer that supports the print condition is executed in the same manner as the automatic selection of the scanner executed in the scan system 411. The PC 301 causes the printer selected by automatic selection to execute print processing under the print conditions stored in the print condition data area 465.

  Here, when a plurality of printer candidates to be subjected to print processing are automatically selected (branch 6), that is, a plurality of printers that support the print conditions stored in the print condition data area 465 are automatically selected. In the case of (branch 6), the printer selection process (step O) is performed by the scan system UI unit 421 through the printer adaptation process (step O) by the printer adaptation unit 433 (step P1). ) A printer selection operation (step P2) is input through the printer selection UI. If there are not a plurality of items (branch 6), the scan system UI unit 421 displays a printer selection result (see FIG. 25, which will be described later) on the screen (step P3). Note that the information processing in steps O, P1, and P3 may be executed not on the scan system 411 side but on the print system 412 side.

  If the PC 301 is set to execute the print processing of the image data related to the scan processing (branch 5), the scanner 301 executes the scan processing (step α) by the scanner driver 425 and the print request unit In response to a print request from 434 to the print system 412, the printer driver 445 causes the printer to execute print processing (step β). That is, in response to the scanning process start operation (step E), not only “scan processing” for reading image data from a read document is executed (step α), but also “print processing” for printing the image data on printing paper. "Is executed (step β). When it is not set to execute the image data print process related to the scan process (branch 5), the scanner driver 425 causes the scanner to execute the scan process (step α).

  The same applies to the setting to execute the data storage process of the image data related to the scan process. If the PC 301 is set to perform data storage processing of image data related to scanning processing, the PC 301 causes the scanner driver 425 to execute scanning processing, and from the data storage request unit 435 to the storage system 413. Under the data save request, the storage driver 451 causes the OA device to execute data save processing. That is, not only “scan processing” for reading image data from a read original but also “data storage processing” for storing the image data in a storage is executed in response to a scan processing start operation. When it is not set to execute the image data saving process related to the scan process, the scanner driver 425 causes the scanner to execute the scan process.

  FIG. 6 is a flowchart describing details of Step J in FIG.

  In step J, the print condition creation unit 431 determines whether or not each item (S101) of the scan condition stored in the scan condition data area 464 can be diverted to the print condition (S102). The print condition creating unit 431 converts the scan condition into the print condition for each item of the scan condition determined to be divertable as the print condition in order to divert the scan condition into the print condition (S103). For example, print conditions such as the print size, print orientation, print surface, and print resolution when the printer performs print processing such as scan size, read orientation, read surface, and read resolution when the scanner performs scan processing. Convert to condition.

  FIG. 7 is a flowchart showing details of step O in FIG.

  In step O, the printer adaptation unit 433 selects, for a plurality of printers selected by automatic selection, a printer suitable for performing scanning processing and printing processing together with a scanner selected by automatic selection or manual selection. “Adaptive processing”. Details of the printer adaptation process will be described below.

  If the setting for not performing the printer adaptation process (S201), the printer adaptation unit 433 sets all printers selected by the automatic selection as screen display targets of the printer selection UI (S211), and ends Step O.

  The printer adaptation unit 433 is selected by automatic selection when the scanner selected by automatic selection or manual selection is a multifunction device or a multifunction peripheral (S202) in the case of setting to perform printer adaptation processing (S201). Among these printers, the printer of the same model and the same installation position as the scanner selected by automatic selection or manual selection is selected as the screen display target of the printer selection UI (S212), and step O is ended.

  When the scanner selected by the automatic selection or the manual selection is not a multifunction peripheral or a multifunction peripheral (S202), the printer adaptation unit 433 does not have a printer on the same floor as the scanner selected by the automatic selection or the manual selection (S203). In this case, all printers selected by automatic selection are set as screen display targets of the printer selection UI (S211), and step O is ended.

  When there is a printer on the same floor as the scanner selected by automatic selection or manual selection (S203), the printer adaptation unit 433 does not have a printer of the same manufacturer as the scanner selected by automatic selection or manual selection (S204). In this case, among printers selected by automatic selection, a printer on the same floor as the scanner selected by automatic selection or manual selection is selected as a screen display target of the printer selection UI (S213), and step O is ended.

  When there is a printer of the same manufacturer as the scanner selected by automatic selection or manual selection (S204), the printer adaptation unit 433 selects the scanner selected by automatic selection or manual selection from among the printers selected by automatic selection. The printer of the same manufacturer and the same floor is set as the screen display target of the printer selection UI (S214), and step O is ended.

  In the printer adaptation process, when there is one printer to be displayed on the screen of the printer selection UI, steps P3 and P4 are executed after step O instead of steps P1 and P2.

  FIG. 8 is a flowchart describing details of step B in FIG.

  In step B, the scanner search unit 422 first issues a scanner search request (broadcast) to perform scanner search (discovery) (S301). Based on the scanner search response issued from each scanner in response to the scanner search request, the scanner search unit 422 executes existence confirmation of a scanner that satisfies the search conditions (S302). The scanner search unit 422 acquires profile information (S303) and creates a logical scanner (S304) for the scanner (S302) that satisfies the search conditions.

  As search levels for scanner search, there are “detailed search level” for requesting scanner profile information and hardware conditions, and “simple search level” for requesting only scanner profile information. The profile information is information such as scanner identification information and a network address, and the hardware conditions are information on conditions that the scanner has as a hardware configuration. In the above scanner search request, the profile information is inquired at both the detailed search level and the simple search level, but the hardware condition is not inquired. Therefore, when the search level is the detailed search level, the hardware condition is inquired.

  When the search level is the detailed search level (S305), the scanner search unit 422 requests hardware conditions for a scanner that satisfies the search conditions (S306). When the scanner search unit 422 acquires the hardware condition before the timeout (S307), the scanner search unit 422 converts the data format of the hardware condition (S308), and adds the hardware condition to the logical scanner (S309).

  FIG. 9 is a flowchart describing details of Step C in FIG.

  In step C, the scan condition base creation unit 423 first determines whether a fixed condition exists in the fixed condition data area 462 (S401). If a fixed condition exists in the fixed condition data area 462, the scan condition base creation unit 423 converts the data format of the fixed condition (S402), and adds the fixed condition to the scan condition base 463 (S403). .

  Subsequently, the scan condition base creation unit 423 determines whether a logical scanner exists in the logical scanner data area 461 (S411). If there is no logical scanner in the logical scanner data area 461, the scan condition base creation unit 423 causes the scanner search unit 422 to execute a scanner search (S412).

  Subsequently, the scan condition base creation unit 423 determines whether there is a logical scanner to be added in the logical scanner data area 461 (S421). If there is a logical scanner to be added in the logical scanner data area 461, the scan condition base creation unit 423 converts the data format of the logical scanner (S422), and adds the logical scanner to the scan condition base 463. (S423).

  FIG. 10 is a flowchart relating to the registration process of the logical scanner.

  In the logical scanner registration process, the logical scanner is registered in the scan system 411. The logic scanner registration process (S501) includes a logic scanner registration process (aspect 1) created by scanner search, a logic scanner registration process (aspect 2) created from data input on the screen, and There is a logic scanner registration process (mode 3) created from the downloaded data. In aspect 1, a logical scanner to be registered is selected from logical scanners created by scanner search (S502). In aspect 2, a logical scanner to be registered is created from data input on the screen (S503). In the aspect 3, the logical scanner to be registered is created from the downloaded data (S504). These logical scanners are registered in the scan system 411 with the storage attribute (store the scanner logically even when the scanner does not physically exist) turned on (S505). The logical printer registration process is the same as the logical scanner registration process.

  FIG. 11 is a flowchart relating to the registration process of the fixed condition.

  In the fixed condition registration process, the fixed condition is registered in the scan system 411. The fixed condition registration process mode (S601) includes a registration process (mode 1) for generating and registering a new fixed condition from a logical scanner, and a new fixed condition generated and registered from screen input data. There is a registration process (mode 2) and a registration process (mode 3) in which a registered fixed condition is changed by data input on the screen and re-registered. In the aspect 1, a logic scanner for generating a new fixed condition is selected (S602), a hardware condition is selected from the selected logic scanner (S603), and the new fixed condition is selected as the selected hardware condition. Is generated (S604). In aspect 2, a new fixed condition is generated from the data input on the screen (S605). In the aspect 3, the registered fixed condition is changed by the data input on the screen (S606). These fixed conditions are registered in the scan system 411 (S607). The registration process for the fixed condition related to the print condition is the same as the registration process for the fixed condition related to the scan condition.

  12 shows the data structure of the scan condition base 463 in FIG. 4, the data structure of the logical scanner stored in the logical scanner data area 461 in FIG. 4, and the data structure of the fixed condition stored in the fixed condition data area 462 in FIG. Represents.

  The scan condition base (FIG. 12A) is a database relating to a correspondence relationship between a scan condition and a scanner that supports the scan condition (a scan process can be executed under the scan condition). The scan condition base 463 in FIG. 4 is an aggregate of scan condition base objects (FIG. 12A) that exist for each scan condition. The scan condition base object in FIG. 12A is an object in which a class defining a scan condition base data structure is instantiated.

  As shown in FIG. 12A, the scanning condition base object includes 1) “condition name” such as reading size, reading direction, reading surface, reading resolution, reading method, endorser, etc., and 2) list (setting method is selected from the list). Or “condition type” of numerical value (setting method is input of numerical value) and 3) a sub-object for each setting item. As shown in FIG. 12A, the sub-object is set as follows: 1) A4 (reading size), vertical (reading direction), double-sided (reading side), 600 dpi (reading resolution), ADF (reading method), ON (endorser), etc. Item ”and 2) a list of scanners that support the setting item.

  The logical scanner (FIG. 12B) is an object that has a one-to-one correspondence with a scanner or a group scanner. The logical scanners 0, 1, 2, etc. stored in the logical scanner data area 461 in FIG. 4 are objects (logical scanner objects in FIG. 12B) that instantiate a class that defines the data structure of the logical scanner.

  As shown in FIG. 12B, the logical scanner object includes 1) “scanner name” such as scanner 0, scanner 1, and scanner 2; 2) “model name” such as model A, model B, and model C; and 3) IP. "Network address" such as address, 4) "Installation position" such as installation floor and installation block, 5) "Driver name" such as driver 0, driver 1, driver 2, etc. 6) Online or offline "connection" "Status", 7) "save attribute" indicating whether or not the scanner is logically stored even when the scanner does not physically exist, 8) last update time, and n) for each hardware condition It consists of sub-objects. As shown in FIG. 12B, the sub-object includes 1) “condition name” such as reading size, reading direction, reading surface, reading resolution, reading method, endorser, etc., and 2) list (setting method is selected from the list) or numerical value. “Condition type” (setting method is numeric input), 3) a list of supported setting items, 4) a list of exclusive conditions that are hardware conditions that cannot be combined, and the like.

  The fixed condition (FIG. 12C) is a standard scan condition supported by all scanners. Each of the fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 462 in FIG. 4 is an object (fixed condition object in FIG. 12C) that instantiates a class that defines the data structure of the fixed condition.

  As shown in FIG. 12C, the fixed condition object includes 1) a “condition name” such as a reading size, a reading direction, a reading surface, a reading resolution, a reading method, and an endorser, and 2) a list (setting method is selected from the list). It consists of a “condition type” that is a numerical value (setting method is input of a numerical value) and 3) a list of setting items.

  FIG. 13 is a data flow diagram relating to automatic scanner selection executed by the scanner selection unit 424 (see FIG. 4). However, here, it is assumed that the scanner search executed by the scanner search unit 422 (see FIG. 4) is the detailed search level (see FIG. 8) that requires scanner profile information and hardware conditions. In addition, the step code | symbol in FIG. 5 is used suitably in the sentence of FIG.

  In the logical scanner data area 461, logical scanners 0, 1 and 2 are stored. What is characteristic here is that n) “sub-objects for each hardware condition” exists. This is because the scanner search executed by the scanner search unit 422 is a detailed search level that requires scanner profile information and hardware conditions.

  Fixed conditions 0, 1, and 2 are stored in the fixed condition data area 462. With the fixed condition 0, the read sizes “A4”, “A3”, and “B4” become the fixed conditions. According to the fixed condition 1, the reading directions “vertical” and “horizontal” are fixed conditions. According to the fixed condition 2, the reading resolutions “300 dpi” and “600 dpi” are the fixed conditions.

  As shown in FIG. 13, the scan condition base creation unit 423 includes logical scanners 0, 1, 2, etc. stored in the logical scanner data area 461 and fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 462. Are used to create the scan condition base 463 (step C). What is characteristic here is that the “sub-object for each hardware condition” of n) is reflected in the scan condition base 463.

  The scan system UI unit 421 uses the scan condition base 463 to display a scan condition setting UI screen (step A1). In the scan condition setting UI, a scan condition setting operation (step A2) is input, and a scan process start operation is input (step E). As shown in FIG. 13, the scan system UI unit 421 stores the scan condition set by the scan condition setting UI as a scan condition object in the scan condition data area 464 (step F). Here, as shown in FIG. 13, the scan condition “A4” scan direction “vertical” scan plane “double-sided” scan resolution “600 dpi” scan method “ADF” is stored in the scan condition data area 464 as a scan condition object. Has been.

  As described below, the scanner selection unit 424 uses the scan condition base 463 to perform automatic selection (step I) of the scanner for executing the scan processing.

  The scanner selection unit 424 first selects an object corresponding to the scan condition object a1 (reading size: A4) b1 (reading direction: vertical) c1 (reading surface: double-sided) d1 (reading resolution: 600 dpi) e1 (reading method: ADF). Search from the scan condition base 463. As a result, the sub-object a2 (reading size: A4) b2 (reading direction: vertical) c2 (reading surface: double-sided) d2 (reading resolution: 600 dpi) e2 (reading method: ADF) of the scan condition base object Searched from within 463.

  Subsequently, the scanner selection unit 424 displays the “list of scanners that support setting items” of the sub-objects a2, b2, c2, d2, and e2 of the scan condition base object as the scan condition objects a1, b1, c1, d1, and so on. Set in e1. As a result, a list “scanners 0, 1, and 2” of scanners that support the reading size “A4” is set in a1 (reading size: A4). A list of scanners “scanners 0, 1, and 2” that support the reading direction “vertical” is set in b1 (reading direction: vertical). A list of scanners “scanners 1 and 2” supporting the reading surface “both sides” is set in c1 (reading surface: both sides). A list of scanners “scanner 0, 1” that supports the reading resolution “600 dpi” is set in d1 (reading resolution: 600 dpi). A list “scanners 1 and 2” of scanners that support the reading method “ADF” is set in e1 (reading method: ADF).

  Subsequently, the scanner selection unit 424 searches for scanners that are commonly set in the scan condition objects a1, b1, c1, d1, and e1. This means a scanner that supports a reading size “A4”, a reading direction “vertical”, a reading surface “double-sided”, a reading resolution “600 dpi”, and a reading method “ADF”. Thus, the scanner “scanner 1” that supports the scanning condition “A4”, reading direction “vertical” reading surface “double-sided” reading resolution “600 dpi”, and reading method “ADF” is found.

  Finally, the scanner selection unit 424 refers to the logical scanner 1 corresponding to the scanner 1 and if there is no contradiction in setting, the scanner selection unit 424 has a scanner “scanner 1” that supports the scan conditions stored in the scan condition data area 464. The selection result of the automatic selection of the scanner that executes the scanning process under the scanning conditions stored in the scanning condition data area 464 is used. Following this, the information processing of steps D1 and D2 is executed.

  FIG. 14 is a data flow diagram relating to automatic scanner selection executed by the scanner selection unit 424 (see FIG. 4). However, here, it is assumed that the scanner search executed by the scanner search unit 422 (see FIG. 4) is a simple search level (see FIG. 8) that requires only the scanner profile information. In addition, the step code | symbol in FIG. 5 is used suitably in the sentence of FIG.

  In the logical scanner data area 461, logical scanners 0, 1 and 2 are stored. What is characteristic here is that the “sub-object for each hardware condition” of n) does not exist. This is because the scanner search executed by the scanner search unit 422 is a simple search level that requires only the scanner profile information.

  Fixed conditions 0, 1, and 2 are stored in the fixed condition data area 462. With the fixed condition 0, the read sizes “A4”, “A3”, and “B4” become the fixed conditions. According to the fixed condition 1, the reading directions “vertical” and “horizontal” are fixed conditions. According to the fixed condition 2, the reading resolutions “300 dpi” and “600 dpi” are the fixed conditions.

  As shown in FIG. 14, the scan condition base creation unit 423 includes logical scanners 0, 1, 2, etc. stored in the logical scanner data area 461 and fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 462. Are used to create the scan condition base 463 (step C). What is characteristic here is that the fixed conditions 0, 1, and 2 are reflected in the scan condition base 463.

  The scan system UI unit 421 uses the scan condition base 463 to display a scan condition setting UI screen (step A1). In the scan condition setting UI, a scan condition setting operation (step A2) is input, and a scan process start operation is input (step E). As shown in FIG. 14, the scan system UI unit 421 stores the scan condition set by the scan condition setting UI in the scan condition data area 464 as a scan condition object (step F). Here, as shown in FIG. 14, a scanning condition of a reading size “A4” reading direction “vertical” reading resolution “600 dpi” is stored in the scanning condition data area 464 as a scanning condition object.

  As described below, the scanner selection unit 424 uses the scan condition base 463 to perform automatic selection (step I) of the scanner for executing the scan processing.

  First, the scanner selection unit 424 searches the scan condition base 463 for an object corresponding to the scan condition object a1 (reading size: A4) b1 (reading direction: vertical) c1 (reading resolution: 600 dpi). As a result, the sub-object a2 (reading size: A4) b2 (reading direction: vertical) c2 (reading resolution: 600 dpi) of the scan condition base object is found from the scan condition base 463.

  Subsequently, the scanner selection unit 424 sets “a list of scanners that support setting items” of the sub-objects a2, b2, and c2 of the scan condition base object in the scan condition objects a1, b1, and c1. As a result, a list “scanners 0, 1, and 2” of scanners that support the reading size “A4” is set in a1 (reading size: A4). A list of scanners “scanners 0, 1, and 2” that support the reading direction “vertical” is set in b1 (reading direction: vertical). A list of scanners “scanners 0, 1, and 2” that support the reading resolution “600 dpi” is set in c1 (reading resolution: 600 dpi).

  Subsequently, the scanner selection unit 424 searches for scanners that are commonly set in the scan condition objects a1, b1, and c1. This means a scanner that supports the reading size “A4”, the reading direction “vertical”, and the reading resolution “600 dpi”. In this way, the scanner “scanners 0, 1, and 2” that supports the scanning condition of the reading size “A4” reading direction “vertical” reading resolution “600 dpi” is found.

  Finally, the scanner selection unit 424 has a scanner “scanners 0, 1 and 2” supporting the scan conditions stored in the scan condition data area 464 and performs a scan process with the scan conditions stored in the scan condition data area 464. This is a selection result of automatic selection of a scanner (candidate) to be executed. Following this, the information processing in steps D3 and D4 is executed.

  In the automatic selection of the scanner, the “connection state” of the logical scanner object may be taken into consideration. As a result, offline scanners are excluded from automatic selection.

  15 shows the data structure of the print condition base 473 in FIG. 4, the data structure of the logical printer stored in the logical printer data area 471 in FIG. 4, and the data structure of the fixed conditions stored in the fixed condition data area 472 in FIG. Represents.

  The print condition base (FIG. 15A) is a database relating to a correspondence relationship between a print condition and a printer that supports the print condition (print processing can be executed under the print condition). The print condition base 473 in FIG. 4 is a collection of print condition base objects (FIG. 15A) that exist for each print condition. The print condition base object in FIG. 15A is an object in which a class defining a print condition base data structure is instantiated.

  As shown in FIG. 15A, the print condition base object includes 1) “condition name” such as print size, print orientation, print surface, print resolution, punch, and staple, and 2) a list (setting method is selected from the list). “Condition type” of a numerical value (setting method is a numerical value input) and 3) a sub-object for each setting item. As shown in FIG. 15A, sub-objects are: 1) “A4 (print size), vertical (print direction), double-side (print side), 600 dpi (print resolution), left two places (punch), left (staple), etc. “Setting item” and 2) a list of printers that support the setting item.

  A logical printer (FIG. 15B) is an object that has a one-to-one correspondence with a printer or a group printer. Each of the logical printers 0, 1, 2, etc. stored in the logical printer data area 471 in FIG. 4 is an object (logical printer object in FIG. 15B) that instantiates a class that defines the data structure of the logical printer.

  As shown in FIG. 15B, the logical printer object includes 1) “printer names” such as printer 0, printer 1, and printer 2; 2) “model names” such as model A, model B, and model C; and 3) IP. "Network address" such as address, 4) "Installation position" such as installation floor and installation block, 5) "Driver name" such as driver 0, driver 1, driver 2, etc. 6) Online or offline "connection" "Status", 7) "Storage attribute" indicating whether or not the printer is logically stored even when the printer does not physically exist, 8) Last update time, and n) For each hardware condition It consists of sub-objects. As shown in FIG. 15B, the sub-object includes 1) “condition name” such as print size, print orientation, print surface, print resolution, punch, staple, and 2) a list (setting method is selected from the list) or a numerical value ( The setting method consists of “condition type” (inputting numerical values), 3) a list of supported setting items, 4) a list of exclusive conditions that are hardware conditions that cannot be combined, and the like.

  The fixed conditions (FIG. 15C) are standard print conditions supported by all printers. Each of the fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 472 in FIG. 4 is an object that instantiates a class that defines the data structure of the fixed condition (fixed condition object in FIG. 15C).

  As shown in FIG. 15C, the fixed condition object includes 1) “condition name” such as print size, print orientation, print surface, print resolution, punch, and staple, and 2) a list (setting method is selected from the list) or a numerical value. “Condition type” (setting method is numeric input) and 3) a list of setting items.

  FIG. 16 is a data flow diagram relating to automatic printer selection executed by the printer selection unit 444 (see FIG. 4). However, here, it is assumed that the printer search executed by the printer search unit 442 (see FIG. 4) is a detailed search level (see FIG. 8) that requires printer profile information and hardware conditions. In the sentence of FIG. 16, the step codes in FIG. 5 are used as appropriate.

  In the logical printer data area 471, logical printers 0, 1, and 2 are stored. What is characteristic here is that n) “sub-objects for each hardware condition” exists. This is because the printer search executed by the printer search unit 442 is a detailed search level requesting printer profile information and hardware conditions.

  Fixed conditions 0, 1, and 2 are stored in the fixed condition data area 472. With the fixed condition 0, the print sizes “A4”, “A3”, and “B4” become the fixed conditions. According to the fixed condition 1, the printing orientations “vertical” and “horizontal” are fixed conditions. According to the fixed condition 2, the printing resolutions “300 dpi” and “600 dpi” are the fixed conditions.

  As shown in FIG. 16, the print condition base creation unit 443 includes logical printers 0, 1, 2, etc. stored in the logical printer data area 471 and fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 472. Are used to create a print condition base 473. What is characteristic here is that the “sub-object for each hardware condition” of n) is reflected in the print condition base 473.

  The print condition creating unit 431 creates a print condition that diverts the scan condition stored in the scan condition data area 464 (step J). As shown in FIG. 16, the print condition creating unit 431 stores the print condition obtained by diverting the scan condition stored in the scan condition data area 464 as a print condition object in the print condition data area 465 (step K). Here, as shown in FIG. 16, the print condition “A4”, print orientation “vertical”, print surface “double-sided”, print resolution “600 dpi” is stored in the print condition data area 465 as a print condition object.

  The printer selection unit 444 uses the print condition base 473 to perform print processing under an automatic selection request (step N) for a printer that supports the print conditions stored in the print condition data area 465 as follows. The automatic selection of the printer that executes is executed.

  First, the printer selection unit 444 selects an object corresponding to the print condition object a1 (print size: A4) b1 (print direction: portrait) c1 (print surface: both sides) d1 (print resolution: 600 dpi) from the print condition base 473. Find out. Thus, the sub-object a2 (print size: A4) b2 (printing direction: vertical) c2 (printing surface: double-sided) d2 (printing resolution: 600 dpi) of the printing condition base object is searched from the printing condition base 473.

  Subsequently, the printer selection unit 444 sets “a list of scanners that support setting items” of the sub-objects a2, b2, c2, and d2 of the print condition base object in the print condition objects a1, b1, c1, and d1. To do. As a result, a list of printers “printers 0, 1, and 2” that support the print size “A4” is set in a1 (print size: A4). In b1 (printing direction: vertical), a list of printers “printers 0, 1, 2” supporting the printing direction “vertical” is set. A list “printers 1 and 2” of printers that support the printing surface “both sides” is set in c1 (printing surface: both sides). In d1 (print resolution: 600 dpi), a list of printers “printer 0, 1” that supports the print resolution “600 dpi” is set.

  Subsequently, the printer selection unit 444 searches for printers set in common in the print condition objects a1, b1, c1, and d1. This means a printer that supports the print size “A4”, the print orientation “vertical”, the print surface “double-sided”, and the print resolution “600 dpi”. Thus, the printer “printer 1” that supports the print condition “print size“ A4 ”, print direction“ vertical ”, print surface“ double-sided ”, print resolution“ 600 dpi ”is found.

  Finally, the printer selection unit 444 refers to the logical printer 1 corresponding to the printer 1 and if there is no contradiction in setting, the printer selection unit 444 has a printer “printer 1” that supports the print conditions stored in the print condition data area 465. This is a selection result of automatic selection of a printer that executes print processing under the print conditions stored in the print condition data area 465. Following this, the information processing of steps P1 and P2 is executed.

  FIG. 17 is a data flow diagram relating to automatic printer selection executed by the printer selection unit 444 (see FIG. 4). However, here, it is assumed that the printer search executed by the printer search unit 442 (see FIG. 4) is the simple search level (see FIG. 8) that requires only the printer profile information. Note that step symbols in FIG. 5 are appropriately used in the sentence of FIG.

  In the logical printer data area 471, logical printers 0, 1, and 2 are stored. What is characteristic here is that the “sub-object for each hardware condition” of n) does not exist. This is because the printer search executed by the printer search unit 442 is a simple search level that requires only the profile information of the printer.

  Fixed conditions 0, 1, and 2 are stored in the fixed condition data area 472. With the fixed condition 0, the print sizes “A4”, “A3”, and “B4” become the fixed conditions. According to the fixed condition 1, the printing orientations “vertical” and “horizontal” are fixed conditions. According to the fixed condition 2, the printing resolutions “300 dpi” and “600 dpi” are the fixed conditions.

  As shown in FIG. 17, the print condition base creation unit 443 includes logical scanners 0, 1, 2, etc. stored in the logical printer data area 471 and fixed conditions 0, 1, 2, etc. stored in the fixed condition data area 472. Are used to create a print condition base 473. What is characteristic here is that the fixed conditions 0, 1, and 2 are reflected in the scan condition base 473.

  The print condition creating unit 431 creates a print condition that diverts the scan condition stored in the scan condition data area 464 (step J). As shown in FIG. 17, the print condition creating unit 431 stores the print condition obtained by diverting the scan condition stored in the scan condition data area 464 as a print condition object in the print condition data area 465 (step K). Here, as shown in FIG. 17, the print condition “A4”, print direction “vertical”, print resolution “600 dpi” is stored in the print condition data area 465 as a print condition object.

  The printer selection unit 444 uses the print condition base 473 to perform print processing under an automatic selection request (step N) for a printer that supports the print conditions stored in the print condition data area 465 as follows. The automatic selection of the printer that executes is executed.

  First, the printer selection unit 444 searches the print condition base 473 for an object corresponding to the print condition object a1 (print size: A4) b1 (print direction: vertical) c1 (print resolution: 600 dpi). As a result, the sub-object a2 (print size: A4) b2 (print direction: vertical) c2 (print resolution: 600 dpi) of the print condition base object is found from the print condition base 473.

  Subsequently, the printer selection unit 444 sets “a list of scanners that support setting items” of the sub-objects a2, b2, and c2 of the print condition base object in the print condition objects a1, b1, and c1. As a result, a list of printers “printers 0, 1, and 2” that support the print size “A4” is set in a1 (print size: A4). A list “printers 0, 1, and 2” of printers that support the printing direction “vertical” is set in b1 (printing direction: vertical). A list “printers 0, 1, and 2” of printers that support the print resolution “600 dpi” is set in c1 (print resolution: 600 dpi).

  Subsequently, the printer selection unit 444 searches for printers that are commonly set in the print condition objects a1, b1, and c1. This means a printer that supports the print size “A4”, the print orientation “vertical”, and the print resolution “600 dpi”. In this way, the printers “printers 0, 1, and 2” that support the print condition of the print size “A4”, the print direction “vertical”, and the print resolution “600 dpi” are found.

  Finally, the printer selection unit 444 uses the printers “printers 0, 1, and 2” that support the print conditions stored in the print condition data area 465 to perform print processing with the print conditions stored in the print condition data area 465. This is a selection result of automatic selection of a printer (candidate) to be executed. Following this, the information processing of steps P3 and P4 is executed.

  In the automatic selection of the printer, the “connection state” of the logical printer object may be taken into consideration. As a result, offline printers (such as printers that have run out of toner, printers that have jammed) are excluded from the targets of automatic selection.

  FIG. 18 is a data flow diagram relating to print condition creation processing executed by the print condition creation unit 431 (see FIG. 4). Note that step symbols in FIG. 5 are appropriately used in the sentence of FIG.

  In steps J and K, the print condition creating unit 431 uses the scan condition stored in the scan condition data area 464 as shown in FIG. 18 in order to divert the scan condition stored in the scan condition data area 464 to the print condition. Is converted into print conditions (see FIG. 6) and stored in the print condition data area 465. At this time, the determination of which item of the scanning condition is converted to which item of the printing condition, that is, the determination of which item of the scanning condition can be diverted to which item of the printing condition is performed based on the common setting list. The As shown in FIG. 18, the common setting list is stored in the common setting list data area 481 as a common setting list object.

  In the common setting list of FIG. 18, a) the scanning condition item “reading size” can be diverted to the printing condition item “printing size”, and b) the scanning condition item “reading direction” is the printing condition item “printing direction”. C) The scanning condition item “reading surface” can be diverted to the printing condition item “printing surface”, and d) the scanning condition item “reading resolution” can be diverted to the printing condition item “printing resolution”. It is prescribed that there is. As a result, as shown in FIG. 18, the scanning size “A4” scanning direction “vertical” scanning surface “double-sided” scanning resolution “600 dpi” scanning method “ADF” has the scanning condition “printing size“ A4 ”printing direction“ vertical ”printing surface. This is converted into a printing condition of “double-sided” printing resolution “600 dpi”. It is not specified that the scan condition item “reading method” can be diverted to the print condition item, and the scan condition “ADF” is not converted into the print condition.

  FIG. 19 shows a logical scanner registration screen 501 displayed on the screen of the PC 301 in FIGS. On the logical scanner registration screen 501, screen input operation of “mode 2” referred to in the logical scanner registration processing of FIG. 10 is possible.

  The logical scanner registration screen 501 includes a scanner name input field 511, a model name input field 512, a network address input field 513, an installation position input field 514, a driver name input field 515, a scanner selection button 521, a driver download button 522, and a registration button. 531 and a cancel button 532 exist.

  The scanner name input field 511 is an input field for inputting the scanner name of the scanner associated with the logical scanner. The model name input field 512 is an input field for inputting the model name of the scanner associated with the logical scanner. The network address input field 513 is an input field for inputting the network address of the scanner associated with the logical scanner. The installation position input field 514 is an input field for inputting the installation position of the scanner associated with the logical scanner. A driver name input field 515 is an input field for inputting a driver name of a scanner driver to be associated with the logical scanner.

  The scanner selection button 521 is a button for selecting a scanner to be associated with the logical scanner. The driver download button 522 is a button for downloading a driver of a scanner associated with the logical scanner.

  When the registration button 531 is clicked, the PC 301 creates a logical scanner from data input on the logical scanner registration screen 501 and registers the logical scanner in the scan system 411. When the cancel button 532 is clicked, the PC 301 cancels the data input on the logical scanner registration screen 501. The logical printer registration screen is the same as the logical scanner registration screen 501 in FIG.

  FIG. 20 shows a fixed condition registration screen 601 displayed on the screen of the PC 301 in FIGS. On the fixed condition registration screen 601, a screen input operation of “mode 2” referred to in the fixed condition registration processing of FIG.

  The fixed condition registration screen 601 includes a condition name input field 611, a condition type selection field 612, a setting item input field 613, a setting item display field 614, a setting item addition button 615, a setting item deletion button 616, a logical scanner selection button 621, There are a fixed condition selection button 622, a registration button 631, and a cancel button 632.

  The condition name input field 611 is an input field for inputting a condition name of a scan condition that is a fixed condition. The condition type selection field 612 is a selection field for selecting a condition type of a scan condition that is a fixed condition. The setting item input field 613 is an input field for inputting a setting item to be added. The setting item display field 614 is a display field for displaying the added setting item. The setting item addition button 615 is a button for adding a setting item input to the setting item input field 613. The setting item deletion button 616 is a button for deleting the setting item selected in the setting item display field 614.

  When the registration button 631 is clicked, the PC 301 creates a fixed condition from the data input on the fixed condition registration screen 601 and registers the fixed condition in the scan system 411. When the cancel button 632 is clicked, the PC 301 cancels the data input on the fixed condition registration screen 601. The fixed condition registration screen related to the print condition is the same as the fixed condition registration screen 601 related to the scan condition of FIG.

  FIG. 21 shows a scan condition setting UI 701 displayed on the screen of the PC 301 in FIGS. This is the UI that appeared in step A1 of FIG.

  The scan condition setting UI 701 includes a scan condition setting field 711, an automatic scanner selection request input field 712, a scanner manual selection button 713, a print request input field 721, a data storage request input field 722, a start button 731, and a cancel button 732. .

  A scan condition setting field 711 is a setting field for setting a scan condition for causing the scanner to execute a scan process. The scanning condition setting UI 701 in FIG. 21 includes a reading size setting field 711a, a reading direction setting field 711b, a reading surface setting field 711c, a reading resolution setting field 711d, a reading method setting field 711e, and an endorser setting field 711f. There exists a scan condition setting column 711 such as. In the scan condition setting UI 701 of FIG. 21, “A4” is set in the reading size setting field, “vertical” is set in the reading direction setting field, “double-sided” is set in the reading surface setting field, and “600 dpi” is set in the reading resolution setting field. “ADF” is set in the reading method setting field, and “ON” is set in the endorser setting field. The scan system UI 421 uses the scan condition base 463 to display the condition names and setting items in the setting fields on the screen.

  The scanner automatic selection request input field 712 is an input field for inputting that the scanner for executing the scanning process is selected by automatic selection. As shown in FIG. 21, when the scanner automatic selection input field 712 is checked, the scanner for executing the scanning process is selected by automatic selection.

  The scanner manual selection button 713 is a button for manually selecting a scanner for executing a scanning process. When the scanner manual selection button 713 is clicked, a scanner selection UI 801 as shown in FIG. 22 is displayed on the screen. The scanner selection UI 801 will be described later.

  The print request input field 721 is an input field for inputting a request to execute the image data print process related to the scan process. As shown in FIG. 21, when the print request input field 721 is checked, image data print processing related to scan processing is performed. As an application example of the print request input field 721, a fax transmission request input field (an input field for inputting that a request for performing a fax transmission process of image data related to a scan process) may be considered.

  The data storage request input field 722 is an input field for inputting a request to perform data storage processing of image data related to scan processing. As shown in FIG. 21, when the data storage request input field 722 is checked, the data storage process of the image data related to the scan process is performed based on the file name input in the file name input field. As an application example of the data storage request input field 722, an e-mail distribution request input field (an input field for inputting a request to perform mail distribution processing of image data related to scan processing) may be considered.

  When the start button 731 is clicked, the PC 301 causes the scanner to execute scan processing under the scan conditions set in the scan condition setting field 711. When the cancel button 732 is clicked, the PC 301 cancels the data input on the screen using the scan condition setting UI 701.

  As described above, the scan condition setting UI 701 is a unified UI that is commonly used for different scanners. This unifies scan condition setting operations for different scanners, and improves the operability of the scanner operation UI. The difference will be understood when compared with the case of using a different UI for each scanner driver.

  In addition, a scanner that supports the scan condition set in the scan condition setting column 711 is automatically selected as a scanner that executes the scan process with the scan condition set in the scan condition setting column 711. The user who wants the scanner to execute the scanning process under the scanning condition does not need to identify the scanner that supports the scanning condition. The user only has to concentrate on the scan condition setting operation.

  Furthermore, as a printer that executes a print process of image data related to the scan process, a printer that supports a print condition that uses the scan condition set in the scan condition setting field 711 is automatically selected, so that the user However, there is no need to perform a printer selection operation or a print condition setting operation for executing print processing. If the user executes both the scan condition setting operation and the print condition setting operation, the reading size and the print size, the reading direction and the printing direction, the reading surface and the printing surface, the reading resolution and the printing resolution, Setting operations for similar items (items that can be diverted in this embodiment) are executed, which is useless.

  FIG. 22 shows a scanner selection UI 801 displayed on the screen of the PC 301 in FIGS. This is the UI that appeared in step D1 of FIG.

  The scanner selection UI 801 includes a scanner selection field 811, an OK button 821, and a cancel button 831.

  The scanner selection column 811 is a selection column for manually selecting a scanner for executing a scan process. In the scanner selection field 811 of FIG. 22, “scanner 0”, “scanner 1”, and “scanner 2” are displayed together with the installation positions as candidate scanners for executing the scan processing. When the OK button 821 is clicked, the PC 301 causes the scanner selected by manual selection in the scanner selection field 811 to execute the scan process (if the scan process is not started yet, the PC 301 temporarily returns to the scan condition setting UI 701). )

  FIG. 23 shows a scanner selection result notification UI 802 displayed on the screen of the PC 301 in FIGS. This is the UI that appeared in step D3 of FIG.

  An OK button 822 exists in the scanner selection result notification UI 802.

  The scanner selection result notification UI 802 displays the selection result of the scanner that executes the scanning process. In the scanner selection result notification UI 802 of FIG. 23, “scanner 1” is displayed together with the installation position as a scanner for executing the scanning process. When the OK button 822 is clicked, the PC 301 causes the scanner selected by automatic selection to execute the scanning process.

  FIG. 24 shows a printer selection UI 901 displayed on the screen of the PC 301 in FIGS. This is the UI that appeared in Step P1 of FIG.

  The printer selection UI 901 includes a scanner selection field 911, an OK button 921, and a cancel button 931.

  The printer selection column 911 is a selection column for manually selecting a printer for executing print processing. In the printer selection field 911 of FIG. 24, “printer 0”, “printer 1”, and “printer 2” are displayed together with the installation positions as printer candidates for executing print processing. When the OK button 921 is clicked, the PC 301 causes the printer selected by manual selection in the printer selection field 911 to execute print processing.

  FIG. 25 shows a printer selection result notification UI 902 displayed on the screen of the PC 301 in FIGS. This is the UI that appeared in Step P3 of FIG.

  The printer selection result notification UI 902 includes an OK button 922.

  The printer selection result notification UI 902 displays the selection result of the printer that executes the printing process. In the scanner selection result notification UI 902 in FIG. 25, “printer 1” is displayed together with the installation position as a printer for executing print processing. When the OK button 922 is clicked, the PC 301 causes the printer selected by automatic selection to execute print processing.

(Modification)
1 corresponds to the embodiment of the present invention (information processing apparatus), and the software of FIG. 4 existing in the PC 301 of FIGS. 1 and 2 corresponds to the embodiment of the present invention (information processing program). . Information processing executed by the PC 301 in FIGS. 1 and 2 corresponds to an embodiment of the present invention (information processing method), and the CD-ROM on which the software in FIG. 4 is recorded is an embodiment of the present invention (recording medium). It corresponds to. 1 and 2 corresponds to an embodiment of the present invention (image forming method). As can be seen from FIG. 7, each scanner 101 in FIG. 1 or each printer 201 in FIG. Absent.

  FIG. 26 is a device layout diagram related to a network to which OA devices are connected. In FIG. 26, a printer 1101, a scanner 1102, a storage device 1103, an authentication server 1111, an ACL (Access Control List) server 1112, a policy server 1113, a PC (Personal Computer) 1121, and a proxy server 1122 are interconnected by a network 1131. . The PC 1121 is an information processing apparatus that functions as a client terminal for the printer 1101, the scanner 1102, and the storage apparatus 1103. The proxy server 1122 is an information processing apparatus that functions as a proxy server for the PC 1121.

  Each OA device in FIG. 26 is an OA device compliant with BMLinkS. The printer 1101 has a print service 1104, the scanner 1102 has a scan service 1105, and the storage apparatus 1103 has a storage service 1106. In the PC 1121, BMLinkS drivers such as a printer driver, a scanner driver, and a storage driver are installed.

  Note that each of the printer 1101 and the scanner 1102 may be a multifunction device or a multifunction device that functions as a printer, or a multifunction device or a multifunction device that functions as a scanner. Also, instead of connecting the printer 1101, the scanner 1102, and the storage device 1103 to the network 1131 as shown in FIG. 26, the scan connected to the print server 1107 and the scanner 1102 connected to the printer 1101, as shown in FIG. The storage server 1109 connected to the server 1108 and the storage apparatus 1103 may be connected to the network 1131, respectively. Instead of connecting the OA device to the network 1131, the server of the OA device is connected to the network 1131. The print server 1107 has a print service 1104, the scan server 1108 has a scan service 1105, and the storage server 1109 has a storage service 1106.

  FIG. 28 is a hardware configuration diagram related to the printer 1101 of FIGS. 26 and 27 includes a CPU 1301, a ROM 1302, a RAM 1303, an HDD (Hard Disk Drive) 1304, a print unit 1311, an operation display unit 1312, a communication unit 1313, a USBIF 1321, a Centronics IF 1322, and the like. ing. These hardware components are connected to the system bus 1331.

  The CPU 1301 is hardware that executes information processing such as control of the printer 1101. The ROM 1302 is hardware in which the information processing program and the like are stored. A RAM 1303 is a memory for information processing described above. The HDD 1304 is the information processing storage described above, and is hardware in which the information processing program and the like are stored.

  The print unit 1311 is hardware for executing print processing, and includes a printer engine or the like. The operation display unit 1312 is hardware for the user to input to the printer 1101, and is hardware for the user to obtain output from the printer 1101, and includes an operation panel or the like. The communication unit 1313 is hardware for connecting the printer 1101 to a network such as Ethernet (registered trademark) or a telephone line, and includes a NIC, a MODEM, or the like.

  The USBIF 1321 is an interface for connecting a cable compliant with the USB standard. The Centronics IF 1322 is an interface for connecting a Centronics specification cable.

  FIG. 29 is a hardware configuration diagram relating to the scanner 1102 of FIGS. 26 and 27 includes a CPU 1401, a ROM 1402, a RAM 1403, an HDD (hard disk drive) 1404, a scan unit 1411, an operation display unit 1412, a communication unit 1413, a USBIF 1421, a SCSI IF 1423, and the like. ing. These hardware components are connected to the system bus 1431.

  The CPU 1401 is hardware that executes information processing such as control of the scanner 1102. The ROM 1402 is hardware that stores the information processing program and the like. A RAM 1403 is a memory for information processing described above. The HDD 1404 is the information processing storage described above, and is hardware in which the information processing program and the like are stored.

  The scan unit 1411 is hardware for executing scan processing, and includes a scanner engine or the like. The operation display unit 1412 is hardware for the user to input to the scanner 1102, and is hardware for the user to obtain an output from the scanner 1102, and includes an operation panel or the like. The communication unit 1413 is hardware for connecting the scanner 1102 to a network such as Ethernet (registered trademark) or a telephone line, and is configured by a NIC, a MODEM, or the like.

  The USBIF 1421 is an interface for connecting a cable compliant with the USB standard. The SCSI IF 1423 is an interface for connecting a cable compliant with the SCSI standard.

  FIG. 30 is a hardware configuration diagram related to the storage apparatus 1103 of FIGS. 26 and 27 includes a CPU 1501, a ROM 1502, a RAM 1503, an HDD (Hard Disk Drive) 1504, an operation display unit 1512, a communication unit 1513, a USBIF 1521, and the like. These hardware components are connected to the system bus 1531. The roles and the like of these hardware components are the same as those of the printer 1101 and the scanner 1102.

  FIG. 31 is a hardware configuration diagram according to the PC 1121 of FIGS. 26 and 27 includes a CPU 1601, a ROM 1602, a RAM 1603, an HDD (hard disk drive) 1604, an operation unit 1611, a display unit 1612, a communication unit 1613, a USBIF 1621, a Centronics IF 1622, a SCSI IF 1623, and the like. These hardware components are connected to the system bus 1631.

  The CPU 1601 is hardware that executes information processing such as various controls. The ROM 1602 is hardware that stores the information processing program and the like. A RAM 1603 is the information processing memory. The HDD 1604 is the information processing storage described above, and is hardware in which the information processing program and the like are stored.

  The operation unit 1611 is hardware for a user to input to the PC 1121, and is configured by a keyboard, a mouse, and the like. The display unit 1612 is hardware for a user to obtain an output from the PC 1121, and is configured by a display or the like. The communication unit 1613 is hardware for connecting the PC 1121 to a network such as Ethernet (registered trademark) or a telephone line, and includes a NIC, MODEM, or the like.

  The USBIF 1621 is an interface for connecting a cable compliant with the USB standard. The Centronics IF 1622 is an interface for connecting a Centronics specification cable. The SCSI IF 1623 is an interface for connecting a cable compliant with the SCSI standard.

  FIG. 32 is a hardware configuration diagram according to the proxy server 1122 of FIGS. 26 and 27 includes a CPU 1701, a ROM 1702, a RAM 1703, an HDD (hard disk drive) 1704, an operation unit 1711, a display unit 1712, a communication unit 1713, a USBIF 1721, and the like. These hardware components are connected to the system bus 1731.

  The CPU 1701 is hardware that executes information processing such as various controls. The ROM 1702 is hardware that stores the information processing program and the like. A RAM 1703 is a memory for information processing described above. The HDD 1704 is a storage for the above information processing, and is hardware in which the above information processing program and the like are stored.

  The operation unit 1711 is hardware for a user to input to the proxy server 1122 and includes a keyboard, a mouse, and the like. The display unit 1712 is hardware for a user to obtain an output from the proxy server 1122, and includes a display or the like. The communication unit 1713 is hardware for connecting the proxy server 1122 to a network such as Ethernet (registered trademark) or a telephone line, and is configured by NIC, MODEM, or the like.

  The USBIF 1721 is an interface for connecting a cable compliant with the USB standard.

  FIG. 33 is a hardware configuration diagram related to the print server 1107 of FIG. 27 includes a CPU 1801, ROM 1802, RAM 1803, HDD (hard disk drive) 1804, operation unit 1811, display unit 1812, communication unit 1813, USBIF 1821, Centronics IF 1822, and the like. These hardware components are connected to the system bus 1831. The roles and the like of these hardware components are the same as those of the PC 1121 and the proxy server 1122.

  FIG. 34 is a hardware configuration diagram according to the scan server 1108 of FIG. 27 includes a CPU 1901, a ROM 1902, a RAM 1903, an HDD (hard disk drive) 1904, an operation unit 1911, a display unit 1912, a communication unit 1913, a USBIF 1921, a SCSIIF 1923, and the like. These hardware components are connected to the system bus 1931. The roles and the like of these hardware components are the same as those of the PC 1121 and the proxy server 1122.

  FIG. 35 is a hardware configuration diagram related to the storage server 1109 of FIG. 27 includes a CPU 2001, a ROM 2002, a RAM 2003, an HDD (hard disk drive) 2004, an operation unit 2011, a display unit 2012, a communication unit 2013, a USBIF 2021, and the like. These hardware components are connected to the system bus 2031. The roles and the like of these hardware components are the same as those of the PC 1121 and the proxy server 1122.

(Document processing)
Based on the above description, document processing executed in the document processing system of FIG. 26 will be described. The document processing may be executed in the document processing system in FIG. 27 in the same manner as in the document processing system in FIG.

  When an input operation for printing document data is performed, the PC 1121 issues a job generation request command for generating a print job and accesses the printer 1101. The printer 1101 prints the document data (executes the print job) by executing a job generation request command for generating a print job on the condition that the authentication is permitted in the authentication process. The authentication information used in the authentication process is exchanged in a state inserted in the job generation request command. Hereinafter, command issue processing and command execution processing will be described.

(1) Command Issuance Processing FIG. 36 shows a printer operation screen 2101 displayed on the PC 1121 screen. FIG. 37 shows an authentication information setting screen 2201 displayed on the screen of the PC 1121. A printer driver is installed in the PC 1121, and a printer operation screen 2101 and an authentication information setting screen 2201 are displayed by the printer driver.

  On the printer operation screen 2101, it is possible to set which printer is used for printing and under what printing conditions. When an authentication information setting button 2121 is clicked on the printer operation screen 2101, the screen moves to the authentication information setting screen 2201. On the authentication information setting screen 2201, authentication information “organization name”, “department name”, and “title” can be set together with the user information “Requesting User Name”. When an OK button 2211 is clicked on the authentication information setting screen 2201, the screen returns to the printer operation screen 2101 and authentication information is set. When an OK button 2111 is clicked on the printer operation screen 2101, a job generation request command for generating a print job is issued.

  38 and 39 show an example of a script of a command for a job generation request (create_job). The SOAP (Simple Object Access Protocol) envelope is omitted. FIG. 38 shows a command before inserting authentication information, and FIG. 39 shows a command after inserting authentication information. Descriptions 38 and 39 are descriptions related to the BMLinkS command “create_job”, and are described in XML (extensible Markup Language). Descriptions 38-1 and 39-1 are the user name “Yamada Taro”. Descriptions 38-2 and 39-2 are job names “sample-job”. Description 39-3 is authentication information inserted into the command using a unique tag.

  Let's talk about tags. In the present embodiment, as tags for inserting authentication information into a command, an organization name tag <x-ORG-name>, a department name tag <x-ORG-group-name>, a department name 1 Tag <x-ORG-group-name-1>, department name tag 2 <x-ORG-group-name-2>, department name tag 3 <x-ORG-group-name-3> In addition, a tag <x-ORG-group-name-4> of the department name 4 and a title tag <x-ORG-title> are defined. The insertion positions of these tags are immediately after the user information tag <requesting-user-name> exists, and immediately after the user information tag <requesting-user-name> does not exist <job-instruction>. And the same level.

  FIG. 40 shows an example of a script for a job generation response (create_jobRESPONSE). The SOAP (Simple Object Access Protocol) envelope is omitted. The description 40 is a description related to the BMLinkS command response “create_jobRESPONSE”, and is described in XML (extensible Markup Language). Description 40-1 is “ok” for the job generation request. The description 40-2 is the job ID “001”. A description 40-3 is a URI “http://192.168.1.4/spool/job-001” as a transfer destination of document data.

  FIG. 41 is a diagram for explaining an execution subject of the authentication information insertion process.

  FIG. 41A is a diagram when the printer driver 2601 in the PC 1121 is the execution subject of the authentication information insertion process. In FIG. 41A, the printer driver 2601 in the PC 1121 has an authentication information acquisition function and an authentication information insertion function. In FIG. 41A, the printer driver 2601 in the PC 1121 issues a job generation request command to the print service 1104 in the printer 1101, and the printer driver 2601 in the PC 1121 acquires the authentication information and adds the command to the command. The authentication information is inserted using a tag.

  FIG. 41B is a diagram in the case where the proxy service 2602 in the PC 1121 is the execution subject of the authentication information insertion process. In FIG. 41B, the proxy service 2602 in the PC 1121 has an authentication information acquisition function and an authentication information insertion function. In FIG. 41B, the printer driver 2601 in the PC 1121 issues a job generation request command to the print service 1104 in the printer 1101, and the proxy service 2602 in the PC 1121 acquires the authentication information, and The authentication information is inserted using a tag.

  FIG. 41C is a diagram when the proxy service 2602 in the proxy server 1122 is the execution subject of the authentication information insertion process. In FIG. 41C, the proxy service 2602 in the proxy server 1122 has an authentication information acquisition function and an authentication information insertion function. In FIG. 41B, the printer driver 2601 in the PC 1121 issues a job generation request command to the print service 1104 in the printer 1101, and the proxy service 2602 in the proxy server 1122 sends the command to the print service 1104 in the printer 1101. At the same time, the proxy service 2602 in the proxy server 1122 acquires the authentication information and inserts the authentication information into the command using a tag.

  41B and 41C have an advantage that the printer driver 2601 may be a standard driver without an authentication information acquisition function or an authentication information insertion function as compared with FIG. 41A. Compared with FIG. 41B, FIG. 41C has an advantage that a plurality of clients can share one proxy.

  As an aspect of the authentication information acquisition process, 1) an aspect of acquiring authentication information by screen input, 2) an aspect of acquiring authentication information by reading a storage medium such as an IC card, and 3) reading of biological information such as a fingerprint or an iris The aspect which acquires authentication information by the biometric authentication using ID is mentioned.

  In the aspect 1, authentication information is input on the screen through the operation display unit 2611 (corresponding to the operation units 1611 and 1711 and the display units 1612 and 1712) of the PC 1121 or the proxy server 1122. The authentication information screen is input on the authentication information setting screen 2201 in FIG. In the case of FIG. 41A, the authentication information setting screen 2201 of FIG. 37 is displayed on the screen of the PC 1121 by the printer driver 2601 in the PC 1121 as described above. In the case of FIG. 41B, the authentication information setting screen 2201 of FIG. 37 is displayed on the screen of the PC 1121 by the proxy service 2602 in the PC 1121. In the case of FIG. 41C, the authentication information setting screen 2201 of FIG. 37 is displayed on the screen of the proxy server 1122 by the proxy service 2602 in the proxy server 1122.

  In aspect 2, the authentication information stored in the IC card set in the IC card IF 2612 of the PC 1121 or the proxy server 1122 is read. The IC card IF 2612 is provided as an optional product such as a printer 1101.

  In the aspect 3, authentication information is acquired through biometric authentication executed by the biometric authentication unit 2613 of the PC 1121 or the proxy server 1122. The biometric authentication unit 2613 is provided as an optional product such as the printer 1101.

  The authentication information acquisition process may be executed before the OK button 2111 is clicked on the printer operation screen 2101 in FIG. 36 (referred to as “pre-acquisition”). There are also cases where it is executed after being called (called post-acquisition). When the authentication information setting button 2121 is clicked on the printer operation screen 2101 in FIG. 36, the authentication information setting screen 2201 in FIG. 37 is displayed. This corresponds to a specific example of pre-acquisition (mode 1). In the case of FIG. 41A, the authentication information acquired in advance is obtained by the printer driver 2601 in the PC 1121, in the case of FIG. 41B by the proxy service 2602 in the PC 1121, and in the case of FIG. 41C, the proxy information in the proxy server 1122 is obtained. Managed by the service 2602. The authentication information acquired in advance is managed in a table as shown in FIG. 42 in the case of FIGS. 41B and 41C. The table in FIG. 42 is a table related to the correspondence between the client IP address and the client authentication information. Using this correspondence, authentication information corresponding to the IP address is inserted into a command including the IP address.

  It is assumed that the authentication information insertion process is executed according to a predetermined setting. When the setting is “preliminary acquisition”, authentication information insertion processing based on the authentication information acquired by prior acquisition is executed. When the setting is “post-acquisition”, authentication information insertion processing is performed using the authentication information acquired by the post-acquisition. If the setting is “not implemented”, the authentication information insertion process is not executed.

  FIG. 43 is a flowchart relating to authentication information insertion processing executed by the printer driver 2601. When the OK button 2111 is clicked on the printer operation screen 2101 in FIG. 36, the printer driver 2601 issues a job generation request command for generating a print job. At this time, if the setting of the authentication information insertion process is “preliminary acquisition” (S1111), authentication based on the authentication information acquired by the prior acquisition is only performed when the prior acquisition of authentication information has been executed (S1121). An information insertion process is executed (S1122). When the setting of the authentication information insertion process is “subsequent acquisition” (S1111), the authentication information acquisition process is executed (S1131), and the authentication information insertion process using the authentication information acquired by the subsequent acquisition is executed (S1132). Is done. After passing through these processes, the printer driver 2601 issues the above command (S1141).

  FIG. 44 is a flowchart relating to authentication information insertion processing executed by the proxy service 2602. The proxy service 2602 receives a job generation request command for generating a print job from the printer driver 2601 and transfers it to the print service 1104 in the printer 1101. At this time, if the setting of the authentication information insertion process is “preliminary acquisition” (S1211), the authentication based on the authentication information acquired by the prior acquisition is only performed when the authentication information is previously acquired (S1221). Information insertion processing is executed (S1222). If not executed (S1221), an authentication information acquisition process is executed (S1223), and an authentication information insertion process using the authentication information acquired by the subsequent acquisition is executed (S1224). Even when the setting of the authentication information insertion process is “subsequent acquisition” (S1211), the authentication information acquisition process is executed (S1231), and the authentication information insertion process using the authentication information acquired by the subsequent acquisition is executed (S1232). The If the authentication information has already been inserted (S1201), these processes are not necessary. After passing through these processes, the proxy service 2602 transfers the above command to the print service 1104 in the printer 1101 (S1241).

  FIG. 45 is a flowchart relating to authentication information acquisition processing executed by the printer driver 2601 and the proxy service 2602. S1131 in FIG. 43 and S1223 and S1231 in FIG. 44 correspond to this.

  When the setting of the authentication information acquisition process is mode 1 (authentication information is acquired by screen input) (S1301 Yes), the authentication information setting screen 2201 of FIG. 37 is displayed (S1311). The authentication information is input on the authentication information setting screen 2201 in FIG. In this way, authentication information is acquired (S1313). If the authentication information acquisition process is canceled (S1312), the authentication information becomes “none”.

  When the setting of the authentication information acquisition process is mode 2 (authentication information is acquired by reading the storage medium) (S1302 Yes), a message prompting to set the IC card is displayed (S1321). The IC card is set according to the message. The authentication information stored in the IC card set according to the message is read (S1323), and the authentication information is acquired (S1324). Then, the authentication information setting screen 2201 of FIG. 37 is displayed as a confirmation screen for the authentication information acquisition result (S1325). If the authentication information acquisition process is canceled (S1322), the authentication information becomes “none”. The same applies when reading of the storage medium fails.

  When the setting of the authentication information acquisition process is mode 3 (acquired by biometric authentication using reading of biometric information) (S1303 Yes), a message prompting an operation for reading biometric information is displayed (S1331). An operation for reading biometric information is performed according to the message. When the biometric information is read (S 1333), the personal identification information is acquired (S 1334) through collation with an internal database related to the correspondence between the biometric information and the personal identification information and further the authentication information, and further the authentication information is acquired. (S1335). Then, the authentication information setting screen 2201 of FIG. 37 is displayed as a confirmation screen for the authentication information acquisition result (S1336). If the authentication information acquisition process is canceled (S1332), the authentication information becomes “none”. The same applies when biometric information reading or database matching fails.

(2) Function Information Providing Process The print service 1104 in the printer 1101 can provide information relating to what function it supports. Specifically, in response to a command requesting that information relating to what function is supported (referred to as a function information provision request), a response including the information relating to what function is supported (function It is called an information provision response).

  FIG. 46 shows an example of the command script for the function information provision request. The SOAP envelope is omitted. A description 46 is a description related to the BMLinkS command and is described in XML. The description 46-1 is the user name “Yamada Taro”.

  FIG. 47 shows an example of the function information provision response script. The SOAP envelope is omitted. Description 47 is a description related to the BMLinkS command response and is described in XML. The description 47-2 is the user name “Yamada Taro”. Description 47-2 is information relating to what “standard function” is supported. Here, it can be seen that stapling is not supported, color is supported, and single-sided printing, horizontal folding duplex printing, and vertical folding duplex printing are supported. That is, it can be understood what printing conditions are supported. Description 47-3 is information relating to what “extended function” is supported. Here, support for the organization name tag, support for the department tag, support for the department 1 tag, support for the department 2 tag It can be seen that the tag of the department name 3 is not supported, the tag of the department name 4 is not supported, and the title tag is supported. That is, it can be understood what authentication information is supported. Note that these tags and authentication information are also called extension tags and extended authentication information after the extended function.

  The print service 1104 in the printer 1101 manages information on what “standard functions” are supported and information on what “extended functions” are supported in separate tables. It is possible to restrict the provision of information related to what “extended function” is supported according to a predetermined setting. When the setting is “restricted”, a description such as description 47-3 is not attached to the function information provision response in FIG. When the setting is “unrestricted”, a description such as description 47-3 is attached to the function information provision response in FIG. By setting the setting to “restricted”, it is possible to prevent misuse of the extension function by a user who does not understand the extension function and abuse of the extension function by a malicious user.

  FIG. 48 is a flowchart relating to function information providing processing executed by the print service 1104. When the print service 1104 receives the function information provision request command issued by the PC 1121, it issues a function information provision response to the PC 1121. At this time, if the print service 1104 supports the extended function (S1401) and the setting for providing function information related to the extended function is “unrestricted” (S1402), what “standard function” is selected. A function information providing response including information related to support and information related to what “extended function” is supported is issued (S1403). On the other hand, when the print service 1104 does not support the extended function (S1401) or when the function information provision setting related to the extended function is “restricted” (S1402), what “standard function” is supported? A function information providing response is issued (S1404) that includes such information but does not include information on what “extended function” is supported.

(3) Command Execution Processing A command for the print service 1104 issued (command issue processing) by the PC 1121 is executed (command execution processing) by the print service 1104. In section 1, command issue processing has been described, but in section 3, command execution processing will be described.

  When the print service 1104 receives a job generation request command for generating a print job, the print service 1104 issues an “authentication request” to the authentication server 1111 for executing authentication processing based on the authentication information inserted in the command. To do. This is because that the authentication is permitted in the authentication process is a condition for executing the command.

  The print service 1104 issues an “access authority determination request” to the ACL server 1112 to determine whether or not there is an authority (access authority) to execute the print job when authentication is permitted in the authentication process. To do. This is because it is a condition for executing the above command that the presence of the authority to execute the above print job is confirmed in addition to the authentication being permitted in the above authentication processing. When the print service 1104 confirms the presence of the authority to execute the print job, the print service 1104 executes the command and generates the print job. The printer 1101 executes the print job generated by the print service 1104 and prints document data.

  The print service 1104 issues a “policy information provision request” to the policy server 1113 to provide information relating to the policy of the printer 1101 when the authentication is not permitted in the above authentication processing. This is because the command is corrected based on information relating to the policy of the printer 1101. The print service 1104 corrects the above command so that the document data is printed (print job is executed) under a print condition (print job execution condition) that matches the policy of the printer 1101, and then the corrected command To generate a print job. Commands that cannot be executed as they are are modified and executed so that they can be executed. The printer 1101 executes the print job generated by the print service 1104 and prints document data.

  Note that the processes executed by the three servers of the authentication server 1111, the ACL server 1112, and the policy server 1113 may be executed collectively by one or two servers. Further, the processing executed by the authentication server 1111 separate from the printer 1101 is performed by the authentication service in the printer 1101, and the processing executed by the ACL server 1112 separate from the printer 1101 is performed by the ACL service in the printer 1101 and separated from the printer 1101. The processing executed by the policy server 1113 may be executed by the policy service in the printer 1101.

  FIG. 49 shows an example of an authentication request command script. The SOAP envelope is omitted. A description 49 is a description related to the BMLinkS command, which is described in XML. The description 49-1 is the user name “Yamada Taro”. The description 49-2 is authentication information exchanged in a state of being inserted into a job generation request command using a unique tag.

  50 and 51 show examples of authentication response scripts. The SOAP envelope is omitted. FIG. 50 shows an authentication response when authentication is successful (when authentication is permitted), and FIG. 51 shows an authentication response when authentication fails (when authentication is not permitted). Descriptions 50 and 51 are descriptions related to the BMLinkS command response, and are described in XML.

  FIG. 52 shows an example of an ACL (Access Control List) managed by the ACL server 1112. “+” And “−” in the access authority column mean presence / absence of access authority to the print service 1104 (printer 1101). For example, + r and −r respectively indicate the presence or absence of a read authority for the print service 1104, that is, the presence or absence of an authority to acquire status information from the printer 1101. For example, + w and −w respectively indicate the presence / absence of a write authority for the print service 1104, that is, the authority for executing a print job in the printer 1101.

  The description 52-1 means that when the authentication information “x-ORG-name” is “*** Corporation”, both the Read authority and the Write authority for the sales department printer (name of the printer 1101) are provided. ing. The description 52-2 indicates that when the authentication information “x-ORG-group-name” is “... Sales Department”, both the Read authority and the Write authority for the sales department printer (name of the printer 1101) are provided. I mean. The description 52-3 means that when the authentication information “x-ORG-title” is “section manager”, there is neither Read authority nor Write authority for the sales department printer (name of the printer 1101).

  Upon receiving the access authority determination request issued by the print service 1104, the ACL server 1112 determines the presence or absence of access authority based on the ACL as shown in FIG. 52, and sends an access authority determination response including the determination result to the print service. Issued to 1104. The print service 1104 confirms the existence of the access authority with reference to the determination result.

  FIG. 53 shows an example of a command script for a policy information provision request. The SOAP envelope is omitted. A description 53 is a description related to the BMLinkS command, and is described in XML. The description 53-1 is the user name “Yamada Taro”. Description 53-2 is authentication information exchanged in a state inserted in a job generation request command using a unique tag. The description 53-3 is a description indicating that a policy related to a job generation request command is an information providing target.

  FIG. 54 shows an example of a policy information provision response script. The SOAP envelope is omitted. A description 54 is a description related to the BMLinkS command response, and is described in XML. A description 54-1 is information provision content related to a policy related to a job generation request command. Here, it is understood that monochrome is essential for the printing color, horizontal folding duplex printing is essential for the printing surface, 2up is essential for the layout, and the maximum allowable number of pages is 6 pages. . As described above, the policy server 1113 manages policies relating to various printing conditions (print job execution conditions) as policies relating to job generation request commands.

  55 and 56 show an example of a script of a command of a job generation request (create_job) received by the print service 1104. FIG. The SOAP envelope is omitted. FIG. 55 shows a command before correction based on the policy, and FIG. 56 shows a command after correction based on the policy. Descriptions 55 and 56 are descriptions related to the BMLinkS command, and are described in XML. Condition 1 “printing color” is corrected from color to monochrome, and condition 2 “printing surface” is corrected from single-sided printing to horizontal folding double-sided printing. This is because, according to the policy shown in FIG. 54, the printing color is indispensable for monochrome, and the printing surface is indispensable for horizontal folding duplex printing.

  FIG. 57 is a flowchart relating to command execution processing executed by the print service 1104.

  When the print service 1104 receives a job generation request command for generating a print job, if authentication information is inserted in the command (S1501), the print service 1104 performs authentication processing based on the authentication information inserted in the command. An “authentication request” for execution is issued to the authentication server 1111 (S1502). Authentication information in the job generation request command, Requesting User Name, and the like are attached to the authentication request.

  If the authentication is successful in the authentication process (S1503), the print service 1104 sends an “access authority determination request” for determining whether or not the authority to execute the print job (access authority) is present to the ACL server 1112. (S1511). The access authority determination request includes information on what is the access target to be determined (in this case, the printer 1101), information on what is the access authority to be determined (in this case, the Write authority), and the job generation request command The authentication information is attached. The print service 1104 executes the above command (S1541) when the existence of the authority to execute the above print job is confirmed (S1512). If not confirmed (S1512), the above command is rejected (the process may be shifted to S1521).

  If the authentication fails in the above authentication process (S1503), the print service 1104 issues a “policy information provision request” to the policy server 1113 to provide information related to the policy of the printer 1101 (S1521). To do. The policy information provision request is attached with information on what the policy is the information provision target (here, the policy regarding the command of the job generation request). Upon receiving the policy information provision response (S1522), the print service 1104 prints the document data (print job is executed) under the print conditions (print job execution conditions) that match the policy of the printer 1101. The command is corrected (S1523), and the corrected command is executed (S1541).

  On the other hand, if authentication information is not inserted in the command (S1501), the print service 1104 is included in the list of Requesting User Names managed by the print service 1104 only when the access control is set (S1531). Then, it is determined whether or not the Requesting User Name in the job generation request command is listed (S1532). If it is listed, the above command is executed (S1541), and if it is not listed, the above command is rejected (the process may be shifted to S1521). If the setting is such that access control is not performed (S1531), access is free and the above command is executed (S1541).

  FIG. 58 is a flowchart relating to command correction processing executed by the print service 1104. S1523 in FIG. 57 corresponds to this.

  If there is a policy related to “stapling” in the policy of the printer 1101 (S1601), the printing condition related to “staple” in the command of the job generation request matches the policy within the limit that can be corrected (S1602). (S1603). If it cannot be corrected (S1602), the command is rejected.

  If there is a policy related to “print color” in the policy of the printer 1101 (S1611), the print condition related to “print color” of the command of the job generation request matches the policy within the limit that can be corrected (S1612). It corrects so that (S1613). If it cannot be corrected (S1612), the command is rejected.

  If there is a policy related to “printing surface” in the policy of the printer 1101 (S1621), the printing condition related to “printing surface” of the command of the job generation request matches the policy within the limit that can be corrected (S1622). It corrects so that (S1623). If it cannot be corrected (S1622), the command is rejected.

  If a policy related to “layout” exists in the policy of the printer 1101 (S1631), the print conditions related to “layout” of the command of the job generation request are matched with the policy within the limit that can be corrected (S1632). (S1633). If it cannot be corrected (S1632), the command is rejected.

  If there is a policy related to “number of pages” in the policy of the printer 1101 (S1641), the print condition related to “number of pages” of the command of the job generation request matches the policy within the limit that can be corrected (S1642). It corrects (S1643). If it cannot be corrected (S1642), the command is rejected.

  In the third section, a case has been described in which the print service 1104 in the printer 1101 issues an authentication request, an access authority determination request, a policy information provision request, or the like as part of the command execution process. FIG. 57 corresponds to the flowchart. As a modification, a case where the proxy service 2602 in the proxy server 1122 issues an authentication request, an access authority determination request, a policy information provision request, or the like as part of the command transfer process will be described. 59 and 60 are used for the description.

  FIG. 59 is a flowchart relating to command transfer processing executed by the proxy service 2602 in the proxy server 1122. FIG. 59 corresponds to the modified example of FIG. 44. Equivalent to. However, the difference from FIG. 44 is that the process of S1751 is executed before the process of S1741. That is, after going through the process of FIG. 60 (S1751), the command is transferred (S1741).

  FIG. 60 is a flowchart relating to command transfer processing executed by the proxy service 2602 in the proxy server 1122. FIG. 60 corresponds to the modification of FIG. 57, and S1801, S1802, S1803, S1811, S1812, S1821, S1822, S1823, S1831, and S1832 are S1501, S1502, S1503, S1511, S1512, S1521, S1522, S1523, respectively. This corresponds to S1531 and S1532. The difference from FIG. 57 is that there is no processing corresponding to “command execution” in S1541. A process that exists instead is “command transfer” in S1741 of FIG.

  The processing from “START” to “END” in FIG. 60 corresponds to the processing in S1751 in FIG.

  Note that the description from the first section to the third section is valid even if the printer 1101 and the print service 1104 are replaced with the scanner 1102, the scan service 1105, the storage device 1103, and the storage service 1106. That is, the command for the scan service 1105 issued by the PC 1121 is executed by the scan service 1105 and issued by the PC 1121 in the same manner as the command for the print service 1104 issued by the PC 1121 is executed by the print service 1104. The command for the storage service 1106 is executed by the storage service 1106. In this case, a job generation request command for generating a print job includes a job generation request command for generating a scan job, a file generation request command for generating a file, and a data read request for reading data. Command, a data write request command for writing data, and the like. The printer driver is replaced with a scanner driver or a storage driver.

  Further, the description from the first section to the third section is valid even if the print service 1104 in the printer 1101 in FIG. 26 is replaced with the print service 1104 in the print server 1107 in FIG. That is, the command for “print service 1104 in the print server 1107” issued by the PC 1121 is executed in the same manner as the command for “print service 1104 in the printer 1101” issued by the PC 1121 is executed by the print service 1104. Is executed by the print service 1104. In this case, the print job is generated by the print server 1107 and executed by the printer 1101. By combining the description in this paragraph and the description in the previous paragraph, it is clear that the same can be said for the scan service 1105 in the scan server 1108 in FIG. 27 and the storage service 1106 in the storage server 1109 in FIG. .

(Modification)
The PC 1121 in FIGS. 26 and 27 corresponds to an embodiment of the present invention (information processing apparatus), and the information processing executed by the PC 1121 in FIGS. 26 and 27 corresponds to an embodiment of the present invention (information processing method). To do. The PC 1121 in FIGS. 26 and 27 is, for example, a personal computer in which a computer program for causing the computer to execute the information processing is installed. The computer program corresponds to an embodiment of the present invention (information processing program), and the CD-ROM on which the computer program is recorded corresponds to an embodiment of the present invention (recording medium). The PC 1121 in FIGS. 26 and 27 is, for example, a personal computer in which the computer program recorded on the CD-ROM is installed.

  The proxy server 1122 in FIG. 26 and FIG. 27 corresponds to the embodiment of the present invention (information processing apparatus), and the information processing executed by the proxy server 1122 in FIG. 26 and FIG. This corresponds to the example. The proxy server 1122 in FIGS. 26 and 27 is, for example, a personal computer in which a computer program that causes the computer to execute the information processing is installed. The computer program corresponds to an embodiment of the present invention (information processing program), and the CD-ROM on which the computer program is recorded corresponds to an embodiment of the present invention (recording medium). The proxy server 1122 in FIGS. 26 and 27 is, for example, a personal computer in which the computer program recorded on the CD-ROM is installed.

  The best mode for carrying out the present invention will be described with reference to the drawings.

  As shown in the block diagram of the printing system shown in FIG. 61, the image processing apparatus according to the present embodiment is connected to a host computer (personal computer) 3 to which the printer 1 is connected indirectly or directly via a network 2 or the like. An application example is shown. The printing method of the printer 1 is arbitrary and may be a laser printer or the like, but in this embodiment, for example, an ink jet printer capable of full-color duplex printing as shown in FIG. 62 is used.

  The host computer 3 includes a CPU (Central Processing Unit) 4 that is a main part of the computer and controls each part centrally. The CPU 4 includes various ROMs (Read Only Memory) and RAMs (Random Access). A memory 5, which is a memory medium, a predetermined communication interface 6 that communicates with the network 2, and an operation panel 7 such as a keyboard that receives various operations from a user are connected via a bus 8. .

  Furthermore, a display 9 that is a display device such as a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display), an HDD (Hard Disk Drive) 10 that is an external storage device, and computer software that is a distributed program are stored. And a drive 12 that is a mechanism for reading computer software from the storage medium 11. The display 9, the HDD 10, and the drive 12 are also connected to the CPU 4 via the bus 8.

  In the memory 5 (ROM) of the host computer 3 having such a configuration, in addition to the control program, software such as an application program and a printer driver is stored.

  As the storage medium 11, various types of media such as various optical disks such as CD and DVD, various magneto-optical disks, various magnetic disks such as FD, and semiconductor memory can be used. Alternatively, the program may be downloaded from the network 2 and installed in the memory 5. Note that the program may operate on a predetermined OS (Operating System), and in that case, the OS may take over the execution of some of the various processes described later, It may be included as a part of a group of program files constituting the application software or OS.

  FIG. 62 is a schematic side view mainly showing a sheet conveyance path of the inkjet printer 1 capable of full-color duplex printing. The printer 1 used in the present embodiment includes, for example, a two-stage sheet cassette 13 that can be selected on the lower side of the apparatus body, and each of the sheets 14 accommodated in these sheet cassettes 13 corresponds to the corresponding sheet supply cassette 13. The paper can be transported to a printing position facing the ink head 19 via a transport path 18 having a paper roller 15 and common transport rollers 16 and 17. The ink head 19 has ink (black ink: pigment, color ink: dye) and can perform full color printing on the paper 14 conveyed on the paper discharge tray 20, and is in the main scanning direction (front and back direction on the paper surface). It can be moved back and forth freely. A waste liquid tank 21 is provided below the paper discharge tray 20. A paper reversing unit 22 is provided adjacent to the transport path 18. The sheet reversing unit 22 includes a large-diameter reversing roller 23 and a guide roller 24 provided around the reversing roller 23 to guide the sheet 14 onto the reversing roller 23 surface. Here, in the single-sided printing mode, the paper 14 is transported from the paper feed cassette 13 through the transport path 18 to the position of the ink head 19 and discharged as it is onto the paper discharge tray 20 while undergoing a printing operation. On the other hand, in the double-sided printing mode, the paper 14 on which one side is printed by the ink head 19 is pulled back to the reversing roller 23 side by the reverse rotation of the transport roller 17 and the like, and passes around the reversing roller 23 that is rotated counterclockwise. The back side printing is performed by transporting the ink head 19 again to the ink head 19 for printing, and the result printed on both the front and back sides is discharged onto the discharge tray 20.

  FIG. 63 shows a software configuration diagram of the printing system shown in FIG. As shown in FIG. 63, the software in the host computer 3 includes a plurality of application programs 31 for various drawing data and a printer driver 32. The printer 1 includes a printer engine 33 mainly including the ink head 19 and a storage unit. 34 and a printer controller 35. Actually, an OS module is interposed between the application program 31 and the printer driver 32.

  Here, a basic operation from a print instruction on the application program 31 until normal printing is performed by the printer 1 will be briefly described. When the user gives a print instruction to the application program 31 running on the host computer 3, the application program 31 uses a common procedure that does not depend on the software to render the drawing data held therein as text data as pixels. The data is output to the printer driver 32 every time. The printer driver 32 converts the instruction and drawing data input from the application program 31 into a code format that can be understood by the printer 1, and outputs this to the printer controller 35. The printer controller 35 sequentially interprets the drawing data input from the printer driver 32, forms a bitmap image according to the data, and outputs the bitmap image to the printer engine 33 to perform a printing operation.

  Under such a premise, it is possible to perform printing in the density reduction mode by performing a process of reducing the print density according to the type of the target object according to the setting of the density reduction mode for the image data requested to be printed. A functional block diagram of the printer driver 32 of this embodiment is shown in FIG. The printer driver 32 generally includes a UI (User Interface) setting unit 41 and a graphic processing unit 42. The UI setting unit 41 functions as a user interface, and has a density setting unit 43 for performing various settings related to a density reduction mode, which will be described later, and is a block for performing UI processing of the printer driver 32. In addition to this, the UI setting unit 41 can specify various print settings related to printing in general.

  The graphic processing unit 42 is a block for creating a print image of the printer driver 32. In the case of the present embodiment, the object separation unit 44, the image processing unit 45, the graphic processing unit 46, the character processing unit 47, the density. A correction unit 48 and an ink ejection image creation unit 49 are provided. The object separation unit 44 is an existing functional unit that performs processing for recognizing an object and separating it for each object in order to proceed with processing for each object in response to a print request from the OS. The processing units of the image processing unit 45, the graphic processing unit 46, and the character processing unit 47 are existing functional units that perform object-specific processing in order to create a print image for each object. The density correction unit 48 is one of the characteristic functional units according to the present embodiment, and a process for correcting the print density with respect to the color information held for each object, specifically, a density reduction mode is set. The function unit that performs the correction process for the density reduction set for each target object (the ratio of the printing material to the print pixels, here, the process of changing the size of the ink droplets). is there. The ink ejection image creation unit 49 is a functional unit that rearranges and converts the data (final dot image pattern) in the order of ejection for ejecting ink from the ink head 19 from the print image after the correction processing. The dot image pattern data created by the ink ejection image creation unit 49 is data transmitted to the printer 1 via the OS spooler. In some cases, processing such as processing data may be performed.

  Here, an outline of the mechanism of object separation used in the present embodiment will be described with reference to FIG. First, there are three types of objects based on text, images, and graphics defined by the OS. In the present embodiment, these three types of objects are targeted. Of course, there are two types of graphics objects: a fill that fills a defined area and a line that is a line drawing. When the OS specifies N types of objects (N is an integer of 2 or more), the N types of objects may be targeted. First, the printer driver 32 that has received a print image as shown in FIG. 65A from the OS performs processing for recognizing and separating each object of text, image, and graphic as shown in FIG. 65B. Next, as shown in FIG. 65 (c), information of the text, image, and graphic objects is organized. Here, the types of objects and RGB color information are illustrated as an example, but the types of information are not limited to those illustrated, and there is of course an optimum information type for each object. .

  More practically, separating the objects means, for example, processing in the printer driver 32 as in the present embodiment, an infinite number of object drawing commands for describing pages from the upper OS module. For example, “graphic line drawing command 1” shown in FIG. 66 (a) (for example, a black line with a thickness of N can be written from the start point (x1, y1) to (x2, y2)),. Command 1 ”(for example, write the character“ Aiueo ”in black in the Mincho style from the start point (x3, y3)),…,“ Graphic line drawing command 2 ”,“ Graphic line drawing command 3 ”,“ Image line drawing ” Command 1 ”,... Such drawing commands are processed by the object separation unit 44 recognizing the object, separating and extracting each object as shown in FIG. 66 (b), and accumulating each object.

  In such a configuration, in the present embodiment, the printer driver 32 selectively sets a density reduction mode for reducing the print density of image data requested for printing according to the type of object of the image data. And a function for recognizing and separating the object with respect to the image data, and a process for reducing the print density of the separated image data according to the type of the target object according to the setting of the density reduction mode. And a function of creating a dot image pattern based on the processed image data and outputting it to the printer. That is, when there is a print request from the application program 31, the printer driver 32 is responsible for print processing via the OS module. At this time, in this embodiment, the object separation unit 44 performs object processing on the image data in the page. Are recognized and separated to extract each object (text, image, graphic), and the density correction unit 48 performs a process of changing the RGB color density as a process of reducing the print density. Whether or not to change the color density as a process for reducing the print density depends on the setting of the density reduction mode for each object. Even if the automatic mode setting based on a certain definition on the program is used, the UI setting is performed. It may be based on a setting operation from the user on the setting screen using the unit 41. For an object for which the density reduction mode is not set, the print density is left unchanged as the original data. The process for reducing the print density basically means that the print position of any object, that is, the print data itself is not changed (the amount of information is not reduced), the size thereof, and the case of an inkjet printer. If so, this means that the size of the ejected droplets ejected from the ink head 19 is changed to at least two stages or more, which is completely different from the thinning-out method as in Patent Document 1.

  That is, in the case of the ink jet printer 1 as in the present embodiment, assuming that the black circles shown in FIG. 67 represent the size of the ejected droplets of the ink head 19, the density at which the print density reduction process is not performed. In the case of 100%, printing is performed with the maximum dot size as shown in FIG. 67 (a). However, in the case where printing with a density of 70% is performed as a printing density reduction process, the printing is shown in FIG. 67 (b). As described above, there is no change in the dot center position (printing position), but the density is lowered as a whole by reducing the dot size. That is, by reducing the dot size while maintaining the dot center interval (printing interval) at a constant interval, the overall density is lowered.

  As an example of the adjustment process for reducing the print density in this case, for example, the set density parameter (%) is reflected in the calculated density value, and the RGB value is converted by the density conversion parameter calculated from the calculated value. It is possible to adopt a method of finally generating bitmap data for printing based on the converted RGB values. That is, as shown in FIGS. 67 (a) and 67 (b), the dot arrangement interval on the bitmap is adjusted by the density parameter (%) so that the interval decreases as the density decreases and the interval decreases as the density increases. When the dot size is taken into consideration, the result is bitmap data in which the dot center position is not changed.

  As shown in FIG. 66C, such processing for reducing the print density is selectively performed for each object according to the mode setting.

  By the way, the setting of the density reduction mode for determining whether or not to reduce the printing density for each object is arbitrary, but in the case of the present embodiment, various modes can be adopted as the mode of the density reduction mode.

  One of them is a density reduction mode in which the print density is reduced for all three types of objects, text, graphics, and images. According to this aspect, it is possible to greatly save ink while avoiding image quality deterioration due to a decrease in the amount of information. In particular, if the density reduction mode of the aspect is set in the full-color duplex printing mode in the case of the inkjet printer 1 capable of duplex printing according to the present embodiment, show-through, show-through, etc., while saving ink. A double-sided printed product with few defects can be obtained.

As another example of the density reduction mode, the print density is reduced only for two or one of the three types of objects of text, graphics, and images, and the density is set for the remaining one or two types of objects. This is a mode of the concentration reduction mode in which is set as a deferred. In particular,
a. Density reduction mode that reduces the printing density only for graphic and image objects b. Density reduction mode for reducing the printing density only for image and text objects c. Density reduction mode by reducing printing density only for text and graphic objects d. Density reduction mode for reducing the printing density only for text objects e. Density reduction mode for reducing printing density only for graphics f. A combination example such as a density reduction mode in which only the image is reduced in print density can be given. Which mode is set may be appropriately selected and set according to the print document, the print purpose, and the like.

  For example, when printing a document that is mainly an image image or graphic and whose character information is not important, it is effective to set a density reduction mode for reducing the print density only for text. Alternatively, when printing a document in which the watermark character is set in the print setting (such as an application document having the print setting in the document), the watermark character density is set to a density reduction mode in which only the text is reduced in print density. It is effective to change (decrease) the density so that it does not interfere with the presence of unnecessary information in the document. It is a document composed of objects of characters, graphics, and images. Documents that character information is important and graphics and images can be considered to play a supplemental role (generally office documents) When printing (mostly equivalent), it is effective to set a density reduction mode that reduces the print density of only graphics and images.

  In this case, if the object is further subdivided, the graphic object has a fill and a line. For these objects, it is possible to set a density reduction mode that individually reduces the print density, thereby making the image Depending on the desired print density reduction setting can be made. In other words, if the density reduction mode is set for an object that is a solid image fill, ink can be saved.

  In addition, regarding these objects, it is also effective to be able to set the density reduction mode in relation to other printing factors. For example, in the color image printing mode, if it is possible to set a density reduction mode that reduces the printing density of all objects other than black and white characters in text, it can be used for printing office documents created as color documents, for example. Thus, it is possible to save ink without significantly deteriorating the print image. However, at this time, it is preferable that a specific color, for example, a color that is not conspicuous such as yellow, is excluded from the print density reduction setting target. According to this, the fall of the visibility regarding a specific color can be prevented. Also, in the monochrome printing mode, if a density reduction mode that reduces the printing density of an object other than text can be set, for example, it can be used for printing a business document created as a monochrome document. Ink can be saved without much damage.

  Furthermore, there are various types of paper 14 used for printing, such as plain paper, thick paper, inkjet exclusive paper, OHP, CD-R and other label paper, but the density reduction mode can be freely selected according to the type of paper to be printed. It is also effective to enable setting. For example, when considering the point of show-through, if you do not worry about show-through even when using double-sided printing, the paper is printed as usual without setting the density reduction mode. In the case of a certain plain paper or the like, it is possible to perform a printing process according to the type of paper, such as using a density reduction mode.

  By the way, the setting of the density reduction mode in various modes will be described. This setting is performed when the user operates the operation panel 7 while looking at the display 9 of the host computer 3 using the UI setting unit 41 in the printer driver 32. That is, the print options are set through the setting screen of the printer driver 32 as shown in FIG. This setting screen relates to the density reduction mode. As a basic setting item field, a density adjustment mode setting field 51 for selectively setting whether or not to set the density reduction mode at the time of printing and a density automatically for both sides are set. And a setting field 52 for designating whether or not to make adjustment effective. Thus, basically, when the density adjustment mode setting field 51 is checked, the density reduction mode is set. Similarly, when the setting field 52 is checked, the density reduction mode is automatically enabled in the duplex printing mode. Is set as follows.

  In addition, in order to perform more detailed settings, object-specific setting fields 53a to 53d are provided, and the density reduction mode of any combination mode as described above by checking the desired setting fields 53a to 53d. Can be set. For example, when the density adjustment mode setting field 51 is checked and the setting fields 53a and 53d are checked, the density reduction mode is set for text and image objects. Furthermore, a setting field 54 for designating whether or not to set the density reduction mode for each paper type and for selecting, for example, plain paper, thick paper, inkjet exclusive paper, OHP, CD-R label paper, etc. as the paper type. The selection field 55 is provided, and an individual density reduction mode can be set for each paper type. Furthermore, when setting such a density reduction mode, the degree of density reduction (density%) is set to an automatic density adjustment mode in which a set value set in advance for the printer 1 based on an experimental result or the like is used as it is. A setting field 56a and a setting field 56b for allowing the user to input and set the density% value independently are alternatively provided. In this case, if the setting column 56a is checked, the degree of density reduction in the density reduction mode is automatically set according to the apparatus specification, for example, 70%. If the setting column 56b is checked, the degree of density reduction in the density reduction mode follows the user set value. In this case, the density% value can be arbitrarily set for each object through the setting columns 57a to 57d. Reference numeral 58 denotes an OK key for confirming the setting contents, and 59 denotes a cancel key for canceling the setting contents.

  With reference to FIG. 69, an example of setting contents of the density reduction mode will be described. The density value in the figure is the density value (%) in the order of each object of text / graphic (line) / graphic (fill) / image. The illustrated example is a setting example for the single-sided printing mode and the double-sided printing mode. In the single-sided printing mode, if the density adjustment mode setting field 51 is not checked and is OFF, the density reduction processing is not performed, and therefore, 100/100/100/100 is set. When the density adjustment mode setting field 51 is checked and ON, only the text text setting field 53a is not checked, and when the automatic density setting field 56a is checked and ON, 100 / The setting is 70/70/70. That is, this is a setting example of the density reduction mode in which the density reduction processing is not performed for text. When the individual setting field 56b is checked and turned ON, it depends on the individual setting value. However, the initial value refers to the value when the automatic density is ON. Further, regarding the first side in the duplex printing mode, when all of the setting fields 53a to 53d are checked and the setting field 56a for automatic density is checked and ON, 85/70/70/70. It is set to become. For the second side, as in the case of single-sided printing, when the setting field 56a for automatic density is checked and ON, the setting is 100/70/70/70. When the individual setting field 56b is checked and turned ON, it depends on the individual setting value. Such mode setting contents are held in the density setting unit 43 as a table. The setting of the first side “85/70/70/70” is lower than the setting of the second side “100/70/70/70” by the amount of text. This is for preventing the material from adhering to any part of the film, and for preventing the set-off and the back-through.

  An example of processing control in the density reduction mode under such setting conditions will be described with reference to a schematic flowchart shown in FIG. First, when there is a print request from the OS, the object separation unit 44 recognizes an object (text, graphic, image) and separates the object for each object in order to proceed the process for each object in response to the print request (step S1). . Next, the necessary processing is performed for each object. In the density correction unit 48, the density setting unit 43 together with printing conditions such as the single-sided printing mode / double-sided printing mode (including the first side / second side, etc.). Density parameter information (density%) for each object is acquired as information relating to the density reduction mode (S2). Then, density correction calculation processing is performed on the color information for each object using the acquired density parameter information, and color information (RGB) is determined (S3). The density correction calculation process in this case is, for example, a simple% multiplication process. A page image is created by creating and combining bitmap data for each object using the color information thus determined (S4). In this case, assuming that the density can be corrected in three stages and one pixel is expressed by 2 bits, the density is 100%: 11, the density is 85%: 10, the density is 70%: 01, and the density is 0% (not printed): It is converted into bitmap data such as 00. The ink ejection image creation unit 49 converts the data of the page image thus prompted into head information for the ink head 19 and performs data compression processing as necessary (S5). Then, the converted data is transferred and output to the printer 1 (there are many systems that are transferred on the OS side) (S6), and printing by the printer 1 is executed (S7).

  FIG. 71 shows a specific print output example. FIG. 71 (a) shows an example of print output at a density of 100% (see the dot pattern example on the right side of the figure) based on an office document containing text and image objects. In this example, the text is all black and the image is a full color photograph. On the other hand, FIG. 71 (b) shows an example of a print output when such an office document is set to a density reduction mode in which the density of the image object is reduced to, for example, 70% (see the dot pattern example on the right side of the figure). Indicates. The print density of the text portion is 100% and is unchanged. In this case, as compared with the print output example of the image portion in FIG. 71A, the print density is lowered as a whole (the amount of ink consumption is reduced) in a state where there is no missing dot (a state where there is no reduction in the amount of information). The output state has not changed so as to give the user a sense of incongruity, and the contents can be sufficiently grasped.

  FIG. 72 shows another specific print output example. FIG. 72A shows a print output example at a density of 100% (see the dot pattern example on the right side of the figure) based on an office document in which text, image, and graphic objects are mixed. In this example, the text is white characters, black characters, color characters, the image is a full-color photograph, and the graphic is a color graph. On the other hand, FIG. 72B shows a case in which such an office document is set to a density reduction mode in which the density of the image and graphic objects is reduced to, for example, a density of 70% (see the dot pattern example on the lower side of the figure). An example of print output is shown. The print density of the text portion is 100% and is unchanged. In this case, as compared with the print output example of the image portion and the graphic portion in FIG. 72A, the print density is lowered as a whole in a state where there is no missing dot (a state where there is no reduction in the amount of information) (ink). The amount of consumption is saved), and the output state does not change so as to give the user a sense of incongruity, and the contents can be sufficiently grasped.

FIG. 3 is a device layout diagram (scanner related) related to a PC corresponding to an embodiment of the present invention; 1 is a device layout diagram (related to a printer) related to a PC corresponding to an embodiment of the present invention; FIG. It is a hardware block diagram concerning PC of FIGS. It is a software block diagram concerning PC of FIGS. It is a flowchart concerning the information processing performed by PC of FIGS. FIG. 6 is a flowchart describing details of Step J in FIG. 5. FIG. 6 is a flowchart describing details of step O in FIG. 5. FIG. 6 is a flowchart describing details of Step B in FIG. 5. FIG. 6 is a flowchart describing details of Step C in FIG. 5. It is a flowchart concerning the registration process of a logic scanner. It is a flowchart which concerns on the registration process of fixed conditions. Represents data structure of scan condition base, logical scanner, and fixed condition. It is a data flow figure (detailed search level) concerning automatic selection of a scanner. It is a data flow figure (simple search level) concerning the automatic selection of a scanner. Represents the data structure of the print condition base, logical printer, and fixed conditions. It is a data flow figure (detailed search level) concerning automatic selection of a printer. FIG. 6 is a data flow diagram (simple search level) related to automatic selection of a printer. FIG. 10 is a data flow diagram related to print condition creation processing. Represents a logical scanner registration screen. Represents the fixed condition registration screen. Represents a scan condition setting UI. Represents a scanner selection UI. Represents a scanner selection result notification UI. Represents a printer selection UI. Represents a printer selection result notification UI. It is an apparatus arrangement | positioning figure which concerns on the network to which the OA apparatus was connected. It is an apparatus arrangement | positioning figure (modification) which concerns on the network to which the OA apparatus was connected. It is a hardware block diagram concerning the printer 1101 of FIGS. It is a hardware block diagram concerning the scanner 1102 of FIGS. It is a hardware block diagram concerning the storage apparatus 1103 of FIG. It is a hardware block diagram concerning PC1121 of FIG. It is a hardware block diagram concerning the proxy server 1122 of FIG. It is a hardware block diagram concerning the print server 1107 of FIG. It is a hardware block diagram concerning the scan server 1108 of FIG. It is a hardware block diagram concerning the storage server 1109 of FIG. A printer operation screen displayed on the screen of the PC is shown. An authentication information setting screen displayed on the PC screen is shown. An example of a script for a job generation request command (before inserting authentication information) is shown. An example of a script for a job generation request command (after inserting authentication information) is shown. An example of a job generation response script is shown. It is a figure for demonstrating the execution main body of an authentication information insertion process. An example of a table for managing authentication information is shown. FIG. 9 is a flowchart relating to authentication information insertion processing executed by a printer driver. It is a flowchart figure which concerns on the authentication information insertion process performed by a proxy service. FIG. 10 is a flowchart relating to authentication information acquisition processing executed by a printer driver or a proxy service. An example of a command script for a function information provision request is shown. An example of a function information provision response script is shown. FIG. 10 is a flowchart relating to a function information providing process executed by a print service. An example of an authentication request command script is shown. An example of a script of an authentication response (when authentication is successful) is shown. An example of an authentication response script (when authentication fails) is shown. An example of ACL is shown. This example shows a script of a policy information provision request command. An example of a policy information provision response script is shown. An example of a script for a job generation request command (before modification) is shown. An example of a script for a job generation request command (before modification) is shown. FIG. 10 is a flowchart relating to command execution processing executed by a print service. FIG. 11 is a flowchart relating to command correction processing executed by the print service. It is a flowchart figure which concerns on the command transfer process performed by the proxy service in a proxy server. It is a flowchart figure which concerns on the command transfer process performed by the proxy service in a proxy server. 1 is a schematic block diagram of a printing system showing an embodiment of the present invention. FIG. 2 is a schematic side view mainly showing a sheet conveyance path of an inkjet printer. It is a schematic block diagram which shows the software structural example. 2 is a functional block diagram of a printer driver. FIG. It is explanatory drawing which shows an object separation process. It is explanatory drawing which shows a more practical object separation process. It is a schematic diagram which shows the example of an ink drop protrusion regarding a density fall. It is a front view which shows the example of a density reduction mode content setting screen. It is explanatory drawing of the table which shows the example of the setting content of density reduction mode. 6 is a schematic flowchart illustrating an example of print processing control. It is explanatory drawing which shows the example of a specific printing output. It is explanatory drawing which shows another specific example of print output.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Printer 3 Image processing apparatus 41 Function to set, Means 44 Function to separate, Means 48 Function to perform processing, Means 49 Function to output, Means 101 Scanner 201 Printer 301 PC
311 CPU
312 ROM
313 RAM
314 HDD
321 Operation unit 322 Display unit 323 Communication unit 331 USB / IF
332 SCSI IF
333 Centronics IF
341 System bus 401 Application 411 Scan system 412 Print system 413 Storage system 421 Scan system UI unit 422 Scanner search unit 423 Scan condition base creation unit 424 Scanner selection unit 425 Scanner driver unit 426 Port monitor unit 427 Network control unit 431 Print condition creation unit 432 Printer selection request unit 433 Printer adaptation unit 434 Print request unit 435 Data storage request unit 441 Print system UI unit 442 Printer search unit 443 Print condition base creation unit 444 Printer selection unit 445 Printer driver unit 446 Port monitor unit 447 Network control unit 451 Storage driver unit 452 Port monitor unit 453 Network control unit 461 Logic Scanner data area 462 Fixed condition data area 463 Scan condition base 464 Scan condition data area 465 Print condition data area 471 Logical printer data area 472 Fixed condition data area 473 Print condition base 481 Common setting list data area 501 Logical scanner registration screen 511 Scanner name Input field 512 Model name input field 513 Network address input field 514 Installation position input field 515 Driver name input field 521 Scanner selection button 522 Driver download button 531 Registration button 532 Cancel button 601 Fixed condition registration screen 611 Condition name input field 612 Condition type selection Field 613 Setting item input field 614 Setting item display field 615 Setting item addition button 616 Setting item deletion button 621 Logical scanner selection Select button 622 Fixed condition selection button 631 Registration button 632 Cancel button 701 Scan condition setting UI
711 Scan condition setting field 712 Scanner automatic selection request input field 713 Scanner manual selection button 721 Print request input field 722 Data storage request input field 731 Start button 732 Cancel button 801 Scanner selection UI
802 Scanner selection result notification UI
811 Scanner selection field 821 OK button 822 OK button 831 Cancel button 901 Printer selection UI
902 Printer selection result notification UI
911 Printer selection field 921 OK button 922 OK button 931 Cancel button 941 Detailed setting button 942 Detailed setting button 1101 Printer 1102 Scanner 1103 Storage device 1104 Print service 1105 Scan service 1106 Storage service 1107 Print server 1108 Scan server 1109 Storage server 1111 Authentication server 1112 ACL server 1113 policy server 1121 PC
1122 Proxy server 1131 Network 1301 CPU
1302 ROM
1303 RAM
1304 HDD
1311 Print unit 1312 Operation display unit 1313 Communication unit 1321 USBIF
1322 Centronics IF
1331 system bus 1401 CPU
1402 ROM
1403 RAM
1404 HDD
1411 Scan unit 1412 Operation display unit 1413 Communication unit 1421 USBIF
1423 SCSIIF
1431 system bus 1501 CPU
1502 ROM
1503 RAM
1504 HDD
1512 Operation display unit 1513 Communication unit 1521 USBIF
1531 system bus 1601 CPU
1602 ROM
1603 RAM
1604 HDD
1611 Operation unit 1612 Display unit 1613 Communication unit 1621 USBIF
1622 Centronics IF
1623 SCSIIF
1631 system bus 1701 CPU
1702 ROM
1703 RAM
1704 HDD
1711 Operation unit 1712 Display unit 1713 Communication unit 1721 USBIF
1731 System bus 1801 CPU
1802 ROM
1803 RAM
1804 HDD
1811 Operation unit 1812 Display unit 1813 Communication unit 1821 USBIF
1822 Centronics IF
1831 system bus 1901 CPU
1902 ROM
1903 RAM
1904 HDD
1911 Operation unit 1912 Display unit 1913 Communication unit 1921 USBIF
1923 SCSIIF
1931 System Bus 2001 CPU
2002 ROM
2003 RAM
2004 HDD
2011 Operation unit 2012 Display unit 2013 Communication unit 2021 USBIF
2031 System Bus 2101 Printer Operation Screen 2111 OK Button 2121 Authentication Information Setting Button 2201 Authentication Information Setting Screen 2211 OK Button 2601 Printer Driver 2602 Proxy Service 2611 Operation Display Unit 2612 IC Card IF
2613 Biometric authentication unit

Claims (13)

An information processing apparatus that functions as a client of an image forming apparatus,
A command issuing unit operable against the server of the image forming apparatus or the image forming apparatus, to issue a command of a print job,
Authentication information insertion means for inserting authentication information into the command,
When the authentication process based on the authentication information inserted in the command does not permit the authentication, the command is modified so that the print job is executed in accordance with the policy printing condition permitted by the image forming apparatus. Causing the image forming apparatus to execute a print job;
An information processing apparatus characterized by that. An information processing apparatus that functions as a client of an image forming apparatus,
The against the server of the image forming apparatus or the image forming apparatus, and the command issuing means for issuing a command of a scan job,
Authentication information insertion means for inserting authentication information into the command,
When the authentication process based on the authentication information inserted in the command does not permit the authentication, the command is modified so that the scan job is executed in accordance with the policy scan condition permitted by the image forming apparatus. Causing the image forming apparatus to execute a scan job;
An information processing apparatus characterized by that. An information processing apparatus that functions as a proxy server for a client of an image forming apparatus,
Authentication information inserting means for inserting authentication information into a command of a print job for the image forming apparatus or the server of the image forming apparatus issued by the client of the image forming apparatus;
When authentication is not permitted in the authentication process based on the authentication information inserted in the command, the command is modified so that the print job is executed in accordance with the policy printing condition permitted by the image forming apparatus, and the modification is performed. Command transfer means for transferring the subsequent command to the image forming apparatus;
An information processing apparatus comprising: An information processing apparatus that functions as a proxy server for a client of an image forming apparatus,
Authentication information inserting means for inserting authentication information into a scan job command issued to the image forming apparatus or a server of the image forming apparatus issued by the client of the image forming apparatus;
If authentication is not permitted in the authentication process based on the authentication information inserted in the command, modify the command so that the scan job is executed in accordance with the policy scan condition permitted by the image forming apparatus, and modify Command transfer means for transferring the subsequent command to the image forming apparatus;
An information processing apparatus characterized by that. When authentication is permitted in the authentication process based on the authentication information inserted in the command,
Based on the authentication information included in the command, the print job is executed only when it is determined that the user has authority to access the image forming apparatus.
The information processing apparatus according to claim 1 or 3 . When authentication is permitted in the authentication process based on the authentication information inserted in the command,
Based on the authentication information included in the command, the scan job is executed only when it is determined that there is an authority to access the image forming apparatus.
The information processing apparatus according to claim 2 or 4 . The authentication information insertion means inserts authentication information into the command using a tag.
The information processing apparatus according to claim 1, wherein: The authentication information is authentication information acquired by screen input, authentication information acquired by reading a storage medium, or authentication information acquired by biometric authentication.
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus. The command is a command described by XML (extensible Markup Language).
The information processing apparatus according to claim 1 , wherein the information processing apparatus is an information processing apparatus. The command is a job generation request command for generating a job.
The information processing apparatus according to any one of claims 1 to 8, wherein the. The authentication process is executed by a server separate from the proxy server.
The information processing apparatus according to claim 3 , wherein the information processing apparatus is an information processing apparatus. The information processing apparatus according to claim 1, wherein the policy printing condition is managed by a server separate from the information processing apparatus. The information processing apparatus according to claim 2, wherein the policy scan condition is managed by a server separate from the information processing apparatus.