US20050097232A1 - Peripheral, peripheral control method, peripheral control system, memory medium for storing peripheral control program, and peripheral control program product - Google Patents

Abstract

An object of the present invention is to provide a multi-function peripheral which is easy for a user to operate. To achieve the object, according to the present invention, there is provided a peripheral connected to an information processing apparatus, which inputs and analyzes a job script constituted of packet data from the information processing apparatus, and subsequently generates an appropriate job file in accordance with the content of the job script.

Description

BACKGROUND OF THE INVENTION
• 1. Field of the Invention
• The present invention relates to peripherals such as a printer, a scanner, a facsimile machine, and a copying machine controlled via a network, IEEE 1394, and other connection forms from an information processing apparatus, a peripheral control method, a peripheral control system, a memory medium in which a peripheral control program is stored, and the peripheral control program.
• 2. Related Background Art
• When jobs are issued to a printer, scanner, facsimile machine, and copying machine connected via a network, and the like from a host computer (information processing apparatus), a plurality of documents are sometimes issued as one job. In this case, control of each document comprises setting the current value of the entire job, and the value is not clearly set, but is implicitly set in the job and each document.
• Therefore, these information concerning the job and document are set or obtained only with the current value. Moreover, the properties of the job and document are not clarified in the set content, and are not distinguished.
• However, the conventional peripheral has following problems in a processing of each document unit in the job.
• (1) Various controls of a job scheduling unit (job execution priority, job execution cancellation, and the like) and each document unit cannot clearly be processed as separate units. Moreover, several documents in the job cannot clearly be constituted as a plurality of units in the job by binding the documents into a unit (binder).
• (2) In a job processing, information such as the processing result of each document unit cannot be obtained. Moreover, information such as the processing result of the unit (binder) obtained by binding some documents cannot be obtained.
• (3) In the job processing, while the job is being executed, new setting or changing cannot be performed on each document unit. Moreover, the setting or changing of the unit (binder) obtained by binding some documents cannot be performed.
• (4) In a print job, media units such as paper to be outputted in one job and finishing units such as stapling cannot be processed as separate units. Moreover, in the print job, the job priority, job cancellation, or the like cannot be processed as the job unit, the stapling or the like cannot be processed as the unit (binder) obtained by binding some documents in the job, and further the paper media to be outputted cannot be processed as the document unit.
• (5) In a scan job, the unit of controlling an original reader and the unit of controlling a scan image cannot be processed as separate units in one job. Moreover, in the scan job, the job priority, job cancellation, or the like cannot be processed as the job unit, the scan original control or the like cannot be processed as the unit (binder) obtained by binding some documents in the job, and further the scan reading control related with the image control cannot be processed as the document unit.
SUMMARY OF THE INVENTION
• Wherefore, an object of the present invention is to provide a multi-function peripheral, a peripheral control method, a peripheral control system, and a memory medium in which a peripheral control program is stored, which are easy for a user to operate.
• To attain the object, according to the present invention, there is provided a peripheral connected to an information processing apparatus, comprising input means for inputting a job script constituted of packet data from the information processing apparatus, and generating means for analyzing the job script obtained by the input means and subsequently generating an appropriate job file in accordance with the content of the job script.
• To attain the object, according to the present invention, there is provided a peripheral control method in a peripheral connected to an information processing apparatus, comprising inputting a job script constituted of packet data from the information processing apparatus, analyzing the job script, and subsequently generating an appropriate job file in accordance with the content of the job script.
• To attain the object, according to the present invention, there is provided a memory medium in which a peripheral control program to be executed in a peripheral connected to an information processing apparatus is stored. The peripheral control program comprises inputting a job script constituted of packet data from the information processing apparatus, analyzing the job script, and subsequently generating an appropriate job file in accordance with the content of the job script.
• To attain the object, according to the present invention, there is provided a peripheral control system provided with an information processing apparatus and a peripheral, comprising output means for outputting a job script constituted of packet data to the peripheral, and generating means for inputting and analyzing the job script, and subsequently generating an appropriate job file in accordance with the content of the job script.
• To attain the object, according to the present invention, there is provided a peripheral control program product to be executed by a peripheral connected to an information processing apparatus, comprising a peripheral control program of inputting a job script constituted of packet data from the information processing apparatus, analyzing the job script, and subsequently generating an appropriate job file in accordance with the content of the job script.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a diagram of a configuration of a multi-function peripheral (MFP) showing an embodiment of the present invention.
• FIG. 2 is a diagram of a system configuration showing the embodiment of the present invention.
• FIG. 3 is a diagram showing a hard configuration of a controller of MFP shown inFIG. 1.
• FIG. 4 is a diagram showing a soft configuration of the controller of MFP shown inFIG. 1.
• FIG. 5 is a diagram showing the soft configuration of the controller of MFP shown inFIG. 1.
• FIG. 6 is a diagram showing the soft configuration of the controller of MFP shown inFIG. 1.
• FIG. 7 is a diagram showing an attribute table ofSupervisor410 shown inFIG. 4.
• FIG. 8 is a diagram showing meanings of attribute ID and type ID of the attribute table ofFIG. 7.
• FIG. 9 is a diagram showing a subaddress to service ID table.
• FIG. 10 is a diagram showing meanings of connection type ID ofFIG. 9.
• FIG. 11 is a diagram showing a service ID to task type table.
• FIG. 12 is a diagram showing meanings of task type ID ofFIG. 11.
• FIG. 13 is a diagram showing a user authentication table.
• FIG. 14 is a diagram showing an access control table.
• FIG. 15 is a diagram showing a security level.
• FIG. 16 is a diagram showing an event setting table.
• FIG. 17 is a diagram showing an event format table.
• FIG. 18 is a diagram showing an attribute table of a print manager.
• FIG. 19 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 18.
• FIG. 20 is a diagram showing a job table.
• FIG. 21 is a diagram showing a job request table.
• FIG. 22 is a diagram showing an attribute table of a scan job manager.
• FIG. 23 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 22.
• FIG. 24 is a diagram showing an attribute table of a copy job manager.
• FIG. 25 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 24.
• FIG. 26 is a diagram showing an attribute table of a font manager.
• FIG. 27 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 26.
• FIG. 28 is a diagram showing a font table.
• FIG. 29 is a diagram showing an attribute table of a form overlay manager.
• FIG. 30 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 29.
• FIG. 31 is a diagram showing a form overlay table.
• FIG. 32 is a diagram showing an attribute table of a log manager.
• FIG. 33 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 32.
• FIG. 34 is a diagram showing a log table.
• FIG. 35 is a diagram showing contents of log data.
• FIG. 36 is a diagram showing a log format table.
• FIG. 37 is a diagram showing an attribute table of a color profile manager.
• FIG. 38 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 37.
• FIG. 39 is a diagram showing a color profile table.
• FIG. 40 is a diagram showing an attribute table of a printer controller.
• FIG. 41 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 40.
• FIG. 42 is a diagram showing a job queue table.
• FIG. 43 is a diagram showing a status ofFIG. 42.
• FIG. 44 is a diagram showing an attribute table of a scanner controller.
• FIG. 45 is a diagram showing meanings of attribute ID and type ID of the attribute table shown inFIG. 44.
• FIG. 46 is a diagram showing a structure of a command packet.
• FIG. 47 is a flowchart showing a processing of the command packet.
• FIG. 48 is a flowchart showing an access processing of the attribute table.
• FIG. 49 is a flowchart of a service ID list inquiry processing.
• FIG. 50 is a flowchart of a subaddress inquiry processing.
• FIG. 51 is a flowchart of an inquiry processing of service ID with a designated task type.
• FIG. 52 is a diagram showing a job structure.
• FIG. 53 is a flowchart of a job script processing in each manager.
• FIG. 54 is a flowchart of the job script processing in each manager.
• FIG. 55 is a flowchart of a job processing in the print job manager.
• FIG. 56 is a flowchart of the job processing in the scan job manager.
• FIG. 57 is a flowchart of the job processing in the copy job manager.
• FIG. 58 is a flowchart of the job processing (download) in the font manager, form overlay manager, log manager, and color profile manager.
• FIG. 59 is a flowchart of the job processing (upload) in the font manager, form overlay manager, log manager, and color profile manager.
• FIG. 60 is a flowchart of job management in each manager.
• FIG. 61 is a flowchart of event transmission.
• FIG. 62 is a flowchart of data (script) transmission from an apparatus.
• FIG. 63 is a diagram showing a hard configuration of Client PC.
• FIG. 64 is a diagram showing a software (control program) configuration of Client PC.
• FIG. 65 is a flowchart of a packet generation/transmission processing.
• FIG. 66 is a flowchart of information obtaining and automatic software (control program) forming on the side of Client.
• FIG. 67 is a flowchart of job issuance with the designated task type.
• FIG. 68 is a diagram showing an event structure.
• FIG. 69 is a flowchart of event transmission.
• FIG. 70 is a flowchart of a log processing.
• FIG. 71 is a flowchart for obtaining/processing charge information.
• FIG. 72 is a flowchart of job issuance (print job, data download).
• FIG. 73 is a flowchart of the job issuance (scan job, data upload).
• FIG. 74 is a flowchart of copy job issuance.
• FIG. 75 is a flowchart of job management command issuance.
• FIG. 76 is a memory map ofDISK315 of MFP.
• FIG. 77 is a memory map ofDISK6009 of Client PC.
• FIG. 78 is a diagram showing a configuration of Client PC.
• FIG. 79 is a diagram showing LBP applicable to a laser beam printer engine of MFP.
• FIG. 80 is a diagram showing IJRA applicable to an ink jet printer engine of MFP.
• FIG. 81 is a diagram showing a sample of a display screen displayed on a display.
• FIG. 82 is a diagram showing a sample of the display screen displayed on the display.
• FIG. 83 is a diagram showing a job structure including a document and a binder.
• FIG. 84 is a diagram showing a document structure including data.
• FIG. 85 is a diagram showing a binder structure including the document.
• FIG. 86 is a flowchart of a job script processing in each manager.
• FIG. 87 is a flowchart of the job script processing (continuation-1) in each manager.
• FIG. 88 is a flowchart of the job script processing (continuation-2) in each manager.
• FIG. 89 is a flowchart of the job script processing (continuation-3) in each manager.
• FIG. 90 is a flowchart of the job script processing (continuation-4) in each manager.
• FIG. 91 is a diagram showing a document table.
• FIG. 92 is a diagram showing a binder table.
• FIG. 93 comprised ofFIGS. 93A and 93B is a diagram showing the job structure including document data of a different data format.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
• (Configuration of Multi-Function Peripheral)
• FIG. 1 is a diagram of a configuration of a multi-function peripheral (MFP) showing an embodiment of the present invention.
• InFIG. 1, acontroller101 for controlling the multi-function peripheral has a hardware configuration shown inFIG. 3, and has a software (control program) configuration shown inDISK315 ofFIG. 76 as a storage medium. Ascanner engine102 is controlled by thecontroller101. Laser beam printer engines (LBP)103,104 are controlled by thecontroller101. The laserbeam printer engine103 is connected to afinisher106, so that a plurality of recording media (e.g., paper) outputted from the printer engine can collectively be stapled (Hotchkiss) and processed. Thefinisher106 is also controlled by thecontroller101. An ink jet printer engine (IJP)105 can also perform color printing, and is controlled by thecontroller101. A network (Ethernet)interface107 provides thecontroller101 with bidirectional communication through the interface. IEEE 1394interface108 provides thecontroller101 with bidirectional communication through the interface. IEEE 1284interface109 provides thecontroller101 with bidirectional communication through the interface. Auser interface110 is constituted of LCD display and a keyboard to display information from thecontroller101 and to transmit an instruction from a user to thecontroller101.
• For the multi-function peripheral configured as described above, a selection is made from three physical printers LBP103 (B/W, with Finisher), LBP104 (B/W), and IJP105 (Color) so that print job issuance is enabled. Moreover, a selection is made from four logical (cluster)printers LBP103+LBP104,LBP104+IJP105,LBP103+IJP105,LBP103+LBP104+IJP105 so that the print job issuance is enabled. Furthermore, an automatic selection is made from the sevenprinters LBP103,LBP104,IJP105,LBP103+LBP104,LBP104+IJP105,LBP103+IJP105, andLBP103+LBP104+IJP105 so that the print job issuance is enabled. Furthermore, IJP is used to constitute a logical printer as a printer which can print only white and black so that the print job issue is enabled.
• Moreover, scan job can be issued from the outside, and a color original can be read. Furthermore, a selection is made (automatic selection can also be made) from the scanner and the eightprinters LBP103,LBP104,IJP105,LBP103+LBP104,LBP104+IJP105,LBP103+IJP105,LBP103+LBP104+IJP105, and IJP which can print only white and black so that the copy job can be issued. Furthermore, when only the printer IJP is present, color copy job can be issued.
• Moreover, font, and form overlay can be used in the print job, upload/download can be realized, and resource management can be performed. Moreover, color profile can be used in the print job, scan job, and copy job, upload/download can be realized, and resource management can be performed. Furthermore, log can automatically be generated inside the apparatus and upload can be realized.
• Moreover, all the functions can be used from any interface of Network (Ethernet, TCP/IP), IEEE 1284, and IEEE 1394. Furthermore, each interface is associated with a subaddress, physical/logical devices (printer, scanner, copy) and each resource. By selecting the subaddress, these physical/logical devices and each resource can be selected. To each subaddress of each interface, the job can be issued and download/upload can be instructed at the same time. Moreover, the association of the subaddress with the physical/logical device and the resource can be obtained by inquiring of the apparatus itself. Furthermore, the function can be used via an internal user interface.
• Moreover, by inquiring of Supervisor described later through the above-described interface from the outside, the outlines of provided functions (a type of job to be issued, a type of resource to be utilized, and the like), job issuance, subaddresses for use in download/upload of the resources, and detailed information of each function (the maximum number of copy sheets, PDL supporting a finisher type, the number of output BIN to be designated, and the like) can be obtained. By using the above-described information, software (control program) can automatically be formed on the side of Client. However, Client needs to know beforehand only the subaddress for use in the inquiry in each interface. A manager can limit the above-described various functions by the connection form and user.
• (Entire System Configuration)
• FIG. 2 is a diagram showing a system configuration of the present embodiment. InFIG. 2, numeral201 denotes the multi-function peripheral (MFP) shown inFIG. 1, and the multi-function peripheral201 is connected toClient PC202 to205 (information processing apparatuses) via a network interface cable208 (10 BASE-T), IEEE 1394interface cable206, and IEEE 1284interface cable207, respectively. In each Client PC as shown inFIG. 78, various software (control programs) stored inDISK6009 described later as the storage medium shown inFIG. 77 are operating.Client PC202 and203 connected viaEthernet208 designate ID address and a port number to connect with the multi-function peripheral201, and output IP packet data.Client PC204 connected via IEEE 1394interface206 designates a node ID and LUN (logical unit number) to connect with the multi-function peripheral201, and outputs SBP-2 packet data.Client PC205 connected via IEEE 1284interface207 designates a socket number to connect with the multi-function peripheral201, and outputs IEEE 1284.4 packet data.
• (Hardware Configuration of Controller)
• FIG. 3 is a diagram showing a hardware configuration of thecontroller101 of the embodiment shown inFIG. 1. Inside thecontroller101,CPU301 is connected via abus313 to Memory (RAM)302,LCD display303 and akeyboard304 constituting the user interface (operating portion)110,ROM314, andDISK315. Various programs and data shown inFIG. 76 are stored in DISK315 (storage medium) such as a hard disk, and a floppy disk, sequentially read into Memory (RAM)302 if necessary, and executed byCPU301. TheDISK315 may be detachably attached toMFP201 or incorporated inMFP201. Furthermore, the program shown inFIG. 76 may be configured to be downloaded fromClient PC202 to205 or another MFP via the network interface cable208 (10 BASE-T), IEEE 1394interface cable206, and IEEE 1284interface cable207 and stored inDISK315.
• TheLCD display303 and thekeyboard304 constitute the user interface (operating portion)110 shown inFIG. 1. WhenCPU301 writes data toLCD display303, display is performed. WhenCPU301 reads data from thekeyboard304, the instruction from the user is inputted.
• Moreover, to the bus313 anetwork interface connector305, IEEE 1394interface connector306, and IEEE 1284interface connector307 are connected, and correspond to thenetwork interface107, IEEE 1394interface108, and IEEE 1284interface109 shown inFIG. 1, respectively. Then, Ethernet (10 BASE-T)cable208, IEEE 1394cable206, and IEEE 1284cable207 shown inFIG. 2 are connected. WhenCPU301 reads or writes data from or to these interfaces, communication is performed using the interfaces.
• Furthermore, to thebus313 connected are LaserBeam Printer Engine308,Finisher309,Scanner Engine310, LaserBeam Printer Engine311, and InkJet Printer Engine312. These correspond to LaserBeam Printer Engine103,Finisher106,Scanner Engine102, LaserBeam Printer Engine104, and InkJet Printer Engine105 shown inFIG. 1, respectively. WhenCPU301 performs data reading/writing via these engines, engine operations such as printing and scanning are performed and various statuses are obtained. Additionally, LaserBeam Printer Engine308,Finisher309,Scanner Engine310, LaserBeam Printer Engine311, and InkJet Printer Engine312 are arranged not insideMFP201, but are arranged as separate peripheral units on the network, and may be controlled by thecontroller101 ofMFP201.
• (Software Configuration of Controller101)
• FIG. 4 is a diagram showing a software (control program) configuration ofDISK315 in thecontroller101, and the software (control program) is executed byCPU301. In the drawing, solid lines indicate data and control, while dotted lines indicate setting and ability obtaining.
• Auser interface driver401controls LCD display303 and akeyboard304. A user interface manager (control program)405 interprets input information inputted viaUI driver401 from the user, generates a command packet shown inFIG. 46, and transmits an output to an interpreter (control program)409. Theuser interface manager405 also interprets the command packet inputted via theinterpreter409, and performs display onLCD display303 via UI driver (control program)401.
• A network interface driver (control program)402 controls thenetwork interface connector305, and processes a physical layer of network packet (physical packet) by extracting a transport packet from the physical packet and generating the physical packet from the transport packet. A TCP/IP, UDP/IP processing module406 processes the transport packet outputted from thenetwork interface402, extracts a command packet, and transmits an output to theinterpreter409. Moreover, the module generates the transport packet from the command packet outputted from theinterpreter409, and transmits an output to thenetwork interface402.
• IEEE 1284 driver (control program)403 controls the IEEE 1284interface307. Numeral407 denotes a processing module (control program) of IEEE 1284.4. IEEE 1284.4 is a standard of a transport layer mainly for the purpose of being used in IEEE 1284 interface. A processing module (control program)407 of IEEE 1284.4 processes the transport packet outputted from the IEEE 1284driver403 to extract the command packet and transmits an output to theinterpreter409. Moreover, the module generates the transport packet from the command packet outputted from theinterpreter409, and transmits an output to the IEEE 1284driver403. IEEE 1394 driver (control program)404 controls the IEEE 1394interface306.
• A module (control program)408 processes SBP (serial bus protocol)-2 which is the transport layer in the IEEE 1394. The SBP-2 processing module408 processes the transport packet outputted from the IEEE 1394driver404 to extract the command packet and transmits an output to theinterpreter409. The module also generates the transport packet from the command packet outputted from theinterpreter409, and transmits an output to the IEEE 1394driver404.Numeral409 denotes a packet interpreter which interprets the command packets transmitted from thetransport processors406,407,408 and theuser interface manager405 and generates commands. Thepacket interpreter409 also generates the command packet in response to a request from another module (control program). In accordance with a subaddress to service ID table (FIG. 9) of Supervisor (general administration manager)410, theinterpreter409 processes only the command packet transmitted from the subaddress which is valid, and cancels the command packets transmitted from the other subaddresses.
• Supervisor (general administration manager)410 retains inDISK315 various data shown inFIG. 7 (attribute table),FIG. 9 (subaddress to service ID table),FIG. 11 (service ID to task type table),FIG. 13 (user authentication table),FIG. 14 (access control table),FIG. 16 (event setting table), andFIG. 17 (event format table), and generally manages an operation of thecontroller101. In response to inputted command instructions,Supervisor410 refers to or changes various data retained by itself, various data retained by managers (font manager413,form overlay manager414,log manager415,color profile manager416,print managers501 to509, scanjob manager419 andcopy job managers601 to608), and various data retained by controllers (printer controllers510 to512, scanner controller420).
• For the command packet interpreted by theinterpreter409, in accordance with the user authentication table (FIG. 13) and access control table (FIG. 14) of Supervisor410 (control program), asecurity gate411 limits a command input in such a manner that only the user who possesses a correct right to use can use the multi-function peripheral201. A dispatcher (control program)412 distributes the commands transmitted from theinterpreter409 to the resource managers (font manager413,form overlay manager414,log manager415, color profile manager416) and the job managers (print managers501 to509, scanjob manager419 andcopy job managers601 to608) which are control programs for processing the commands. Thefont manager413 manages fonts. Thefont manager413 retains data as shown inFIG. 26 (attribute table) andFIG. 28 (FONT table) inDISK315. The font (stored inDISK315 or ROM314) managed by thefont manager413 is transferred toPDL rasterizers417 and418, and used during a print job processing.
• Theform overlay manager414 manages form overlays. Theform overlay manager414 retains data as shown inFIG. 29 (attribute table) andFIG. 31 (FORM table) inDISK315. The form overlay (stored inDISK315 or ROM314) managed by theform overlay manager414 is transferred toPDL rasterizers417 and418, and used during the print job processing. Thelog manager415 manages logs. Thelog manager415 retains data as shown inFIG. 32 (attribute table) andFIG. 34 (LOG table) inDISK315. The log is outputted from each manager, and placed under control of the log manager. An execution log file is stored inRAM302 orDISK315 and updated at any time.
• Thecolor profile manager416 manages color profile data for a color scanner or a color printer to perform color matching. Thecolor profile manager416 retains data as shown inFIG. 37 (attribute table) andFIG. 39 (color profile table) inDISK315. Color profiles managed by thecolor profile manager416 are transferred to the printer controllers (control programs)510,511,512 and the scanner controller (control program)420, and used during processing of the print job, copy job and scan job. The PDL rasterizer417 processes document data written in PS (registered trademark) as one type of Page Description Language (PDL), and outputs image data. The PDL rasterizer418 processes document data written in PCL (registered trademark) as one type of Page Description Language (PDL), and outputs image data. Thescan job manager419 manages the scan job. Thescan job manager419 retains data as shown inFIG. 22 (attribute table) inDISK315. Thescan job manager419 instructs thescanner controller420 to execute scanning. Thescanner controller420 controls thescanner engine310.
• Thescanner controller420 retains data indicating a function, state and performance of thescanner engine310 as shown inFIG. 44 (attribute-table) inDISK315. Thescan job manager419 andscanner controller420 have the data indicating the functions and performances (FIGS. 22 and 44), but the functions shown by these data do not need to be the same. By rewriting the data (FIG. 22) retained by thescan job manager419 throughSupervisor410, the function can be limited.
• The above-describedfont manager413,form overlay manager414,log manager415, andcolor profile manager416 are resource management programs, thescan job manager419,print job managers501 to509, thecopy job managers601 to608 are logical device (scanner, printer) control programs, and the laserbeam printer controllers510,511, inkjet printer controller512, andscanner controller420 are physical device (printer, scanner) control programs.
• (Configuration of Print Job Manager)
• FIG. 5 is a diagram which supplements the software (control program) configuration diagram shown inFIG. 4. Adispatcher412 is the same as thedispatcher412 shown inFIG. 4, and distributes the command packets to the print job managers (control programs)501 to509. Theprint job managers501 to509 manage the print job. Each print job manager has data as shown inFIG. 18 (attribute table) inDISK315. For each print job manager, a printer controller for use in processing the print job (LBP Controller510,LBP Controller511,Ink Jet Controller512, or an arbitrary combination of thecontrollers510,511,512) and a print engine connected to the controller are determined, and the type of printer controller (control program) to be used is described in data shown byattribute ID2001 ofFIG. 18. However, only theprint job manager508 has a function of dynamically selecting the print engine for use, and it is described in data (attribute table) of theprint job manager508 that the manager has the function. Each print manager retains the inputted print job, and data indicating the type of printer controller and the type of job to be executed by the printer controller as shown inFIG. 20 (job table) andFIG. 21 (job request table) inDISK315. Theprinter controllers510 to512 control theprint engines308,311 and312. Theprinter controller510 also controls thefinisher309. Each printer controller has data indicating a function, state and performance of the corresponding printer engine as shown inFIG. 40 (attribute table) inDISK315. Each controller retains data indicating a state of inputted print job as shown inFIG. 42 (job queue table) inDISK315.
• Theprint job managers501 to509 and theprinter controllers510 to512 have data indicating the functions and performances as shown inFIG. 18 (attribute table) andFIG. 40 (attribute table) inDISK315. In general the print job manager has a performance equal to a sum of the performances of the controllers for use, and a function corresponding to a common item of the function of each controller. However, some of the functions can be changed by rewriting the data (FIG. 18) of the print job manager throughSupervisor410. For example, since theprint job managers503 and509 use thesame printer controller512, they can present the same performance and function. However, the data of the print job managers can be set by a setting processing described later in such a manner that theprint job manager503 can perform color printing and theprint job manager509 cannot perform the color printing.
• (Configuration of Copy Job Manager)
• FIG. 6 is a diagram which supplements the software (control program) configuration diagram shown inFIGS. 4 and 5.
• Adispatcher412 is the same as thedispatcher412 shown inFIG. 4, and distributes the command packets to the copy job managers (control programs)601 to608. Thecopy job managers601 to608 manage the copy job. Each copy job manager has data as shown inFIG. 24 (attribute table) inDISK315. For each copy job manager, a printer controller and a scanner controller for use in processing the copy job and a print engine and a scanner engine connected to the controllers are determined, and the types of printer controller and scanner controller to be used are described in the data (attribute ID2001) shown inFIG. 24. However, only thecopy job manager608 has a function of dynamically selecting the print engine for use, and it is described in data (attribute ID2002) of thecopy job manager608 that the manager has the function. Each copy manager holds the inputted copy job, and data indicating the type of printer controller or scanner controller and the type of job to be executed by the controller as shown inFIG. 20 (job table) andFIG. 21 (job request table) inDISK315. Theprinter controllers510 to512 control the print engines, and are the same as those shown inFIG. 5.
• (Attribute Table of Supervisor)
• FIG. 7 shows data (attribute table) which Supervisor (control program)410 retains inDISK315 and manages. This table shows a function outline, connection information, security information, and the like of the multi-function peripheral201. In the table, each line shows one information unit (record), and the data is constituted as an aggregate of a plurality of records. Each record is constituted of attribute ID701, type ID702 and attribute value703, and indicates an attribute of Supervisor. The attribute ID701 indicates a type of information, thereby indicating a meaning of the value703. The attribute ID701 is unique inside the apparatus, and the same attribute ID indicates the same information type. The type ID702 indicates a type of data which the value703 has, and is used in interpreting the value703. The type ID is univocally determined by the attribute ID and defined uniquely inside the apparatus. In the embodiment, the attribute ID701 and the type ID702 are both shown in the attribute table, but by retaining an attribute ID to type ID table as data separated from the attribute table, only the attribute ID and value may be shown in the attribute table. The value703 indicates an attribute value in accordance with the attribute ID701.
• FIG. 8 is a diagram showing details of attribute ID701 and type ID702 of the attribute table ofFIG. 7. In the drawing,attribute ID102 “a list of supported security levels” retains a list of security levels which can be set, among security levels required for issuing operation for Supervisor. The security levels will be described in description of an access control table ofFIG. 14. Attribute103 “current security level” indicates a security level which is currently set in Supervisor.Attribute ID401 “current count data” indicates a list of information as count targets in Supervisor, and its meaning is shown byattribute ID402 “count data format”. For example,count data45,78,34,13 indicate the number of print sheets having a paper size shown in the count data format. Theattribute ID402 “count data format” is shown as a list of attribute ID. Since the attribute ID is defined to be unique in the apparatus, by designating the attribute ID, the meaning of the count data can be designated. For example, an attribute value565 ofattribute ID402 means the number of print sheets with a sheet size of A2, an attribute value537 means the number of print sheets with a sheet size of A3, an attribute value545 means the number of print sheets with a sheet size of A4, and an attribute value523 means the number of print sheets with a sheet size of A5. Count limit data ofattribute ID403 shows a maximum value which theattribute ID401 “current count data” can have. When even one of the values of “current count data” exceeds the maximum value, by invalidating a valid flag of the subaddress to service ID table shown inFIG. 9,CPU301 invalidates all the services (by the manager). Count unit price data ofattribute ID404 shows a unit price for every count of the attribute ID retained in theattribute ID402 “count data format” in terms of a currency unit. Current charge data ofattribute ID405 indicates a value obtained by multiplying corresponding values of theattribute ID401 “current count data” andattribute ID404 “count unit price data” and taking a sum.
• Charge limit data ofattribute ID406 shows a maximum value which theattribute ID405 “current charge data” can have. When theattribute ID405 “current charge data” exceeds anattribute ID406 “charge limit data”, by changing a valid flag to an invalid flag in the subaddress to service ID table shown inFIG. 9, theCPU301 invalidates all the services (by the manager). A list of supported events ofattribute ID501 shows events which can be set to be notified to Supervisor by a list of event ID which is univocally defined for every event type. Actual event transmission is set by setting a connection type and addressee of event notification with event ID in the event setting table shown inFIG. 16. For the values of the attribute table ofFIG. 7, description “Table Data” indicates that values (52 to104) are data each having a table format shown by type ID.
• (Subaddress to Service ID Table)
• FIG. 9 shows a subaddress to service ID table. This table is retained inDISK315 as attribute values of an attribute ID1001 (subaddress to SID table) in the attribute table shown inFIG. 7. The subaddress to SID table shows a type of service (e.g., print, font download, and the like) obtained by placing the command packet in a subaddress, and the subaddress. Moreover, in accordance with the valid flag, and the like of the table, theinterpreter409 controls each connection form concerning whether a job service is provided. In the table each line shows one information unit (record), and the data is constituted as an aggregate of a plurality of records. Each record is constituted of aconnection type ID801,subaddress802,service ID803,valid flag804,valid user list805, andinvalid user list806. Theconnection type ID801 indicates an identifier indicating the connection form.FIG. 10 is a diagram showing meanings of connection type ID:0 denotes Internal (user interface);1 denotes TCP/IP (network);2 denotes IEEE 1284.4 (IEEE 1284); and3 denotes SBP-2 (IEEE 1394).
• Thesubaddress802 shows a subaddress of each connection form. Although the user interface has no subaddress, for the sake of convenience the subaddress is allocated to the interface, and the command packet is placed together with subaddress information from the user interface.
• Theservice ID803 is an identifier indicating a service. Theservice ID803 is allocated to each manager shown inFIGS. 4, 5 and6 in one-to-one correspondence.
• Thevalid flag804 shows whether the subaddress is valid. When the value is true (YES), the subaddress is valid, so that the user can issue the command packet to the subaddress. When the value is false (No), the subaddress is invalid, which means that even if the command packet is transmitted to the subaddress, the packet is canceled.FIG. 8 shows that when the connection form of connection type ID2 (IEEE 1284) is used, a service of service ID8 (print job manager) cannot be provided.
• Thevalid user list805 shows a list of user ID which can receive the service when the subaddress is valid. Theinvalid user list806 shows a list of user ID which cannot receive the service even when the subaddress is valid. The value can be set to only one of thevalid user list805 and theinvalid user list806.
• (Service ID to Task Type Table)
• FIG. 11 shows a service ID to task type table. This table is retained inDISK315 as attribute values of attribute ID1002 (SID to Task Type Table) of the attribute table shown inFIG. 7. The service ID to task type table shows the type of service provided by the service ID. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of tasks. Each record is constituted ofservice ID901 andtask type902. Thetask type902 shows the type of service.FIG. 12 is a diagram showing meanings of values of the task type902:0 denotes the service performed by Supervisor;1 denotes print;2 denotes scan;3 denotes copy;101 denotes font;102 denotes form overlay;103 denotes log; and104 denotes color profile. Service ID has a one-to-one correspondence with the manager which provides the service. Therefore, the service ID can be used for accessing a function table of each manager. Since each printer controller or scanner controller also has the function table, in order to access the table, a controller ID equivalent to the service ID is allocated to the printer controller or the scanner controller, and the type of controller shown by the controller ID is managed in the service ID to task type table. Atask type201 denotes a printer controller, and202 denotes a scanner controller. The controller ID has a one-to-one correspondence with each controller shown inFIGS. 4 and 5.
• Meanings of service ID are as follows:
• 0: Supervisor4101: print job manager5012: print job manager5023: print job manager5034: print job manager5045: print job manager5056: print job manager5067: print job manager5078: print job manager5089: print job manager50910: scan job manager41911: copy job manager60112: copy job manager60213: copy job manager60314: copy job manager60415: copy job manager60516: copy job manager60617: copy job manager60718: copy job manager608101: font manager413102: form overlay manager414103: log manager415104: color profile manager41621: printer controller51022: printer controller51123: printer controller51224:scanner controller420
• (User Authentication Table)
• FIG. 13 shows a user authentication table retained by Supervisor, and shows authentication information of users who can use the apparatus. This table is retained inDISK315 as attribute values of attribute ID1003 (user authentication table) of the attribute table shown inFIG. 7. The user authentication table shows a set of valid user ID and password, together with information as to whether the user has a manager privilege. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted ofuser ID1001,password1002 andmanager privilege flag1003. Themanager privilege flag1003 indicates whether the user has a right as a manager.
• (Access Control Table)
• FIG. 14 is an access control table retained by Supervisor, and shows a security level of each service. This table is retained inDISK315 as attribute values of attribute ID1004 (access control table) of the attribute table shown inFIG. 7. The access control table retains the security level necessary for each service ID, and a list of users who are permitted to be given services. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records.
• Each record is constituted ofservice ID1101,security level1102 anduser ID list1103. Thesecurity level1102 shows authentication information necessary for receiving the service designated by theservice ID1101, that is, for issuing the command packet to the manager indicated by theservice ID1101.FIG. 15 shows meanings of security levels:security level 0 shows that user authentication is unnecessary; 1 shows that only the manager is discriminated; 2 shows that the service is available only for an authenticated user, but the user ID is used and no password is used for authentication; and 3 shows that the service is available only for the authenticated user, and the user ID and password are used for the authentication. Theuser ID list1103 shows a list of user ID permitted to use (access) when thesecurity level1102 is 2 or 3.
• (Event Setting Table)
• FIG. 16 shows an event setting table retained by Supervisor. This table is retained inDISK315 as attribute values of attribute ID502 (event setting table) of the attribute table shown inFIG. 7. The event setting table retains, for each event type, a method of transmitting event notification and an addressee when a designated event occurs in the apparatus. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of anevent ID1201,connection type1202 andnotification addressee1203. The addressee is constituted of the connection type and a notification address dependent on the connection type. Theevent ID1201 shows an event type, and is defined to be unique in the apparatus. For example,Event ID200 indicates that there is no paper,ID399 indicates that there is no toner,ID432 indicates that there is no ink, andID234 indicates that a cover of the multi-function peripheral is open. Theconnection type ID1202 shows a connection type by which the event notification is transmitted, and values are the same as those which are used in the subaddress to service ID table ofFIG. 9. The notification addressee1203 shows event notification addressees suitable for theconnection type1202.
• (Event Format Table)
• FIG. 17 is an event format table retained by Supervisor showing event contents. This table is retained inDISK315 as attribute values of attribute ID503 (event format table) of the attribute table shown inFIG. 7. The event format table retains a type of additional data transmitted as the event notification, for each event ID defined to be unique in the apparatus. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted ofevent ID1301 andevent format1302. Theevent format1302 is a type of the additional data transmitted as the event notification, and shown as an attribute ID list. The attribute ID is defined to be unique in the apparatus. Since the type is also univocally determined by the attribute ID, by designating the attribute ID, a format of the additional data can be shown. For example, an attribute ID676 of theevent format1302 indicates a paper size, ID756 indicates a paper type,ID666 indicates a toner type,ID698 indicates an ink type, andID600 indicates a cover position. As described hereinafter, event transmission methods and addressees are set in the data (attribute table) retained by each manager and controller, and the event which occurs in each manager and controller can be notified, but the additional data format of the event is also retained in the event format table shown inFIG. 17. When the designated event occurs, the content defined by the event format is notified with predetermined data for each event ID.
• (Attribute Table of Print Job Manager)
• FIG. 18 shows data (attribute table) retained by each of the print job managers (control programs)501 to509 inDISK315. This table shows performances and functions of print jobs which can be handled by the print job manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and each record is constituted ofattribute ID1401,type ID1402 andvalue1403.FIG. 19 is a diagram showing values ofattribute ID1401 andtype ID1402 of the attribute table ofFIG. 18. Type IDs other than type ID203 (job table type), type ID204 (job request table type), type ID81 (type of inhibited attribute combination list1), type ID82 (type of inhibited attribute combination list2), type ID83 (type of inhibited attribute combination list3), type ID84 (type of inhibited attribute combination list4), and type ID85 (type of inhibited attribute combination list5) are the same as those which are used in the Supervisor attribute table ofFIG. 7.
• Anattribute ID601 “download method for supported data” shows a method of transmitting document data to be printed to the apparatus. In the embodiment supported are amethod 1 which comprises including the document data in the job; and amethod 2 which comprises including a reference pointer (URL: Unified Resource Locator) of the document data in the job, and reading the document data indicated by the reference pointer from the apparatus if necessary.
• Attribute IDs801 to805 are inhibited attributes indicating limits on attributes to be set in the print job placed for the print job manager. These attributes are used to show limit items. For example, when the number of copy sheets exceed100, finisher setting becomes impossible. There are five types of methods of representing the limits in the inhibited attributes. As shown in {attribute ID1: {attribute ID2}}, theattribute ID801 holds a plurality of pairs of lists of anotherattribute ID2 to acertain attribute ID1. This means that when theattribute ID1 is being set, the setting of eachattribute ID2 cannot be performed in a print job script.
• As shown in {attribute ID1: operator identifier: value: {attribute ID2}}, theattribute ID802 retains a plurality of pairs of lists of anotherattribute ID2 relative to a certain attribute ID1, operator identifier and value. This means that in a case where the operator shown by the operator identifier for theattribute ID1 is applied to the value, when a result is true, the setting of eachattribute ID2 cannot be performed in the print job script. The operator identifier has a one-to-one correspondence with calculation of two terms of integer values. For example,0 denotes “=(equal)”.
• As shown in {attribute ID1: operator identifier1: value1: {attribute ID2: operator identifier2: value2}}, theattribute ID803 retains a plurality of pairs of lists of a set of another attribute ID2,operator identifier2 andvalue2 relative to a certain attribute ID1,operator identifier1 andvalue1. This means that in a case where the operator shown by theoperator identifier1 for theattribute ID1 is applied to thevalue1, when a result is true, setting cannot be performed in the print job script in such a manner that a result of application of the operator indicated by theoperator identifier2 for each attribute ID2 to thevalue2 becomes true.
• As shown in {(attribute ID1: operator identifier1: value1): operator identifier3: (attributeID2 operator identifier2: value2): {attribute ID3}}, theattribute ID804 retains a plurality of pairs of lists of still another attribute ID3, relative to a certain attribute ID1,operator identifier1 andvalue1 and theoperator identifier3 and another attribute ID2,operator identifier2 andvalue2. This means that in a case where the result of application of the operator shown by theoperator identifier1 for theattribute ID1 to thevalue1 and the result of application of the operator shown by theoperator identifier2 for theattribute ID2 to thevalue2 are calculated as shown by theoperator identifier3, when a result is true, eachattribute ID3 cannot be set in the print job script.
• As shown in {(attribute ID1: operator identifier1: value1): operator identifier3: (attribute ID2: operator identifier2: value2): {attribute ID4: operator identifier4: value4}}, theattribute ID805 retains a plurality of pairs of lists of a set of still another attribute ID4,operator identifier4 andvalue4, relative to a certain attribute ID1,operator identifier1 andvalue1 and theoperator identifier3 and another attribute ID2,operator identifier2 andvalue2. This means that in a case where the result of application of the operator shown by theoperator identifier1 for theattribute ID1 to thevalue1 and the result of application of the operator shown by theoperator identifier2 for theattribute ID2 to thevalue2 are calculated as shown by theoperator identifier3, when a result is true, setting cannot be performed in the print job script in such a manner that when calculation is performed on eachattribute ID4 and calculation shown by4 is applied to thevalue4, a result becomes true.
• Theattribute ID2001 “list of controller ID (possibly) executing Job” is a list of controller ID of the controller which executes the print job, and the print job managers other than theprint job manager508 are surely on a list of controllers which surely execute the job. Since theprint job manager508 dynamically selects the controller in accordance with the function demanded for the job, the attribute indicates a controller selection range.
• Theattribute ID2002 “controller auto selection is possible or not” indicates whether the print job manager automatically selects the controller. In the embodiment, only theprint job manager508 sets the value to be true. The other attribute IDs are the same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those which are under control of the printer job manager to which the attribute table belongs. For example, anattribute value101 “supported operation” is a list of operations which can be issued to the print job manager, and anattribute value406 “charge limit data” puts a charge limit on the print job executed by the print job manager. For treatment in a case where the charge limit is exceeded, the service of the print job manager is merely invalidated, and services of the other managers are not influenced. Additionally, the attribute table of the print job manager shown inFIG. 18 is an attribute table of service ID4 (print job manager504), and attribute tables ofprint job managers501,502,503,505,506,507,508,509 corresponding toservice IDs1,2,3,5,6,7,8,9, respectively are stored inDISK315 and differ from one another.
• (Job Table)
• FIG. 20 is a diagram showing data (job table) retained by the print job manager, and shows a file name to job ID table in which a job entity managed by the print job manager is retained. The table is retained inRAM302 as attribute values of attribute ID (job table) of the attribute table shown inFIG. 18. The print job manager dynamically changes the job table onRAM302 and stores the table inDISK315 if necessary. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of ajob ID1501 and afile name1502 in which the job entity is retained. Thejob ID1501 is an identifier allocated to the job by the print job manager when the job is transmitted to the print job manager. Thejob file name1502 is a name of the file in which the job entity is retained. As shown inFIG. 52, the job entity is constituted of a plurality of sets of attribute ID, attribute value size and attribute value.
• (Job Request Table)
• FIG. 21 is a diagram showing a job request table retained by the print job manager, and shows a relation between a job managed by the print manager and a job executed by the controller. This table is retained inDISK315 as attribute values of attribute ID2004 (job request table) of the attribute table shown inFIG. 18. The job request table shows a type of controller to execute a job managed by the print job manager and a type of job executed by the controller. In the table each line shows one information unit, and data is constituted as an aggregate of a plurality of records. Each record is constituted of ajob ID1503, acontroller ID1504, and ajob ID1505 allocated in the controller. Thejob ID1503 is an identifier allocated to the job by the print job manager when the job is transmitted to the print job manager, and corresponds to thejob ID1501 in the job table (FIG. 20). Thecontroller ID1504 shows ID of the controller by which the job is executed. Thejob ID1505 is a job identifier allocated by the controller to execute the job.
• (Attribute Table of Scan Job Manager)
• FIG. 22 shows an attribute table which is data retained by thescan job manager419. This table shows performances and functions of scan jobs which can be treated by the scan job manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID1601,type ID1602 andvalue1603.FIG. 23 is a diagram showing values ofattribute ID1601 andtype ID1602 of the attribute table ofFIG. 22. An attribute ID=602 “upload method for supported data” shows a method of transmitting scanned document data to the apparatus. In the embodiment, supported are amethod 1 which comprises including the document data during returning of the job; and amethod 2 which comprises retaining the document data in the apparatus, including a reference pointer (URL: Unified Resource Locator) to the document data during the job returning, and reading the document data indicated by the reference pointer from host (Client) if necessary. An attribute ID=1201 “list of supported image formats” shows data formats of images which can be outputted, and one of the formats can be designated as a data format during issuance of the scan job. A job table of attribute ID=2003 is the same as that retained by the print job manager shown inFIG. 20.
• The other attribute IDs are the same as those used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those which are under control of the scan job manager to which the attribute table belongs. Type IDs other than the type ID203 (job table type) of the attribute table ofFIG. 23 are the same as those which are used in the Supervisor attribute table ofFIG. 7.
• (Attribute Table of Copy Job Manager)
• FIG. 24 shows data (attribute table) retained by each of thecopy job managers601 to608. This table shows performances and functions of copy jobs which can be treated by the copy job manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID1701,type ID1702 andvalue1703.FIG. 25 shows values ofattribute ID1701 andtype ID1702 of the attribute table ofFIG. 24. An attribute ID1302 (color print is possible or not), attribute ID1303 (type of supported finishing), attribute ID1304 (highest resolution that can be set), attribute ID1305 (lowest resolution that can be set), attribute ID2001 (list of controller ID possibly executing Job), attribute ID2002 (controller auto selection is possible or not), and attribute ID2003 (job table) are the same as those which have been shown in descriptions of the print job manager and scan job manager. Moreover, attribute IDs and type IDs other than the attribute ID1302 (color print is possible or not), attribute ID1303 (type of supported finishing), attribute ID1304 (highest resolution that can be set), attribute ID1305 (lowest resolution that can be set), attribute ID2001 (list of controller ID possibly executing Job), attribute ID2002 (controller auto selection is possible or not),attribute ID2003. (job table), and type ID203 (job request table type) are the same as those which are used in the Supervisor attribute table ofFIG. 7. Additionally, the attribute table of the copy job manager shown inFIG. 24 is an attribute table of service ID18 (copy job manager608), and the attribute tables of thecopy job managers601 to607 corresponding to serviceIDs11 to17 are stored inDISK315, respectively, and differ from one another.
• (Attribute Table of Font Manager)
• FIG. 26 shows data (attribute table) retained inDISK315 by thefont manager413. This table shows font types which can be treated by the font manager, a font list currently managed by the font manager, and the like.
• In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID1801,type1802 andvalue1803.
• FIG. 27 shows values ofattribute ID1801 andtype ID1802 of the attribute table ofFIG. 26. Attribute IDs and type IDs other than attribute ID601 (download method for supported data), attribute ID602 (upload method for supported data), attribute ID1501 (list of supported font types), attribute ID1502 (Max. No of retainable fonts), attribute ID1503 (No of currently retained fonts), attribute ID1504 (list of retained fonts), and type ID150 (font table) are the same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those under control of the font manager to which the attribute table belongs. Theattribute ID601 “download method for supported data” andattribute ID602 “upload method for supported data” are the same as those which are described in descriptions of the print job manager and scan job manager, respectively, and show methods of downloading and uploading supported font data.
• (Font Table)
• FIG. 28 shows a font table retained by the font manager. This table is retained inDISK315 as attribute values of the type ID1504 (font table) of the attribute table shown inFIG. 26. The font table shows a type of font which is currently managed by the font manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of afont ID1901, afont type1902, afont name1903, and a file name1904 including font data. The font data is stored inDISK315, and is an identifier allocated to the font by the font manager when the font data is downloaded toRAM302.
• (Attribute Table of form Overlay Manager)
• FIG. 29 shows data (attribute table) retained inDISK315 by theform overlay manager414. This table shows formats of form overlays which can be treated by the form overlay manager, a list of form overlays currently managed by the form overlay manager, and the like. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID2001,type ID2002, andvalue2003.FIG. 30 shows values of the attribute ID and type ID of the attribute table ofFIG. 29. Attribute IDs and type IDs other than the attribute ID601 (download method for supported data), attribute ID602 (upload method for supported data), attribute ID1601 (list of supported form overlay formats), attribute ID1602 (Max. No of retainable form overlays), attribute ID1603 (No of currently retained form overlays), attribute ID1604 (list of retained form overlays) and type ID160 (form table) are the same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those under control of the form overlay manager to which the attribute table belongs. Theattribute ID601 “download method for supported data” andattribute ID602 “upload method for supported data” are the same as those which are described in descriptions of the print job manager and scan job manager, respectively, and show methods of downloading and uploading supported form overlay data.
• (Form Overlay Table)
• FIG. 31 shows a form overlay table retained by theform overlay manager414. This table is retained inDISK315 as attribute values of attribute ID1604 (form overlay table) of the attribute table shown inFIG. 29. The form overlay table shows a type of form overlay which is currently managed by the form overlay manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of aform overlay ID2101, a formoverlay data format2102, aform overlay name2103, and afile name2104 including form overlay data. The form overlay data is stored inDISK315, and theform overlay ID2101 is an identifier allocated to the font by the form overlay manager when the form overlay data is downloaded toRAM302.
• (Attribute Table of Log Manager)
• FIG. 32 shows data (attribute table) retained inDISK315 by thelog manager415. This table shows a list of logs currently managed by the log manager, and the like. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID2201,type ID2202, andvalue2203.FIG. 33 shows values of attribute ID and type ID of the attribute table ofFIG. 32. Attribute IDs and type IDs other than the attribute ID602 (upload method for supported data), attribute ID1703 (No of retained Logs), attribute ID1704 (list of retained logs), attribute ID1705 (Log format table), type ID170 (log table), and type ID171 (log format table type) are the same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those under control of the log manager to which the attribute table belongs.
• (Log Table)
• FIG. 34 shows a log table retained by thelog manager415. This table is retained inDISK315 as attribute values of the attribute ID1704 (log table) of the attribute table shown inFIG. 32. The log table shows a type of log currently managed by the log manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of alog ID2301, and afile name2302 including log data. Thelog ID2301 is a log identifier prescribed beforehand for the type.
• (Contents of Log Data)
• FIG. 35 shows contents of log data managed by the log manager withDISK315. The log data is constituted as an aggregate of log records. Each log record is constituted oflog format ID2401,record date2402 andlog data2403. Thelog format ID2401 refers to log format information recorded in the log format table shown inFIG. 36, and shows formats of thelog data2403. For example, log data “12345, 4, 1.23, “OK”” ofLog Format ID1 means that user ID from which the job is issued to the print job manager ofservice ID1 is 12345, the number of outputted sheets is 4, an amount of used toner is 1.23, and job completion state is OK.
• (Log Format Table)
• FIG. 36 shows a log format table retained by thelog manager415. This table is retained inDISK315 as attribute values of the attribute ID (log format table) of the attribute table shown inFIG. 32. The log format table shows a format of the log recorded in each log data managed by thelog manager415. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted oflog format ID2501, andlog format2502. The log format is shown as a list of a pair of service ID and attribute ID. The attribute ID is defined to be unique in the apparatus, and the type is univocally determined by the attribute ID. Therefore, by designating the attribute ID, the format of log data can be shown. The list of the pair of service ID and attribute ID oflog format2502, and a list of values in thelog data2403 correspond to each other by sequence. For example, a third pair of service ID and attribute ID of the list oflog format2502 means a format of a third value of log data. For example, format “1:701, 1:565, 1:765, 1:777” ofLog Format ID1 shows the user ID from which the job is issued to the print job manager ofservice ID1, the number of outputted sheets, the amount of used toner, and the completion state of the job. Moreover, format “11:701, 11:565, 11:765, 11:777” ofLog Format ID2 shows the user ID from which the job is issued to the print job manager ofservice ID11, the number of outputted sheets, the amount of used toner, and the completion state of the job.
• (Attribute Table of Color Profile Manager)
• FIG. 37 shows data (attribute table) retained inDISK315 by thecolor profile manager416. This table shows formats of color profiles which can be treated by the color profile manager, and a list of color profiles currently managed by the color profile manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID2601,type ID2602, andvalue2603.FIG. 38 shows values of attribute ID and type ID of the attribute table ofFIG. 37. Attribute IDs other than attribute ID601 (download method for supported data), attribute ID602 (upload method for supported data), attribute ID1801 (list of formats of supported color profile data), attribute ID1802 (Max. No of retainable color profiles), attribute ID1803 (list of currently retained color profiles), attribute ID1804 (color profile table), and type ID180 (color profile table type) are the same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those under control of the color profile manager to which the attribute table belongs. Theattribute ID601 “download method for supported data” andattribute ID602 “upload method for supported data” are the same as those which are described in descriptions of the print job manager and scan job manager, respectively, and show methods of downloading and uploading supported font data.
• (Color Profile Table)
• FIG. 39 shows color profiles retained by the color profile manager. This table is retained inDISK315 as attribute values of attribute ID1804 (color profile table) of the attribute table shown inFIG. 37. The color profile table shows a type of color profile currently managed by the color profile manager. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of acolor profile ID2701, acolor profile format2701 and afile name2703 including color profile data. Thecolor profile ID2701 is an identifier allocated to the color profile by the color profile manager when the color profile data is downloaded. The color profile data comprises data transmitted fromScanner Engine102 and correction data for correcting data transmitted to InkJet Printer Engine105 to perform color matching.
• (Attribute Table of Printer Controller)
• FIG. 40 shows data (attribute table) retained inDISK315 by each of theprinter controllers510,511,512. This table shows performances and functions of the print engine and finisher controlled by the printer controller, and values concerning the performances and functions cannot be rewritten. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID2801,type ID2802, andvalue2803.FIG. 41 shows values of attribute ID and type ID of the attribute table ofFIG. 40. Attribute IDs and type IDs other than attribute ID12 (controller type), attribute ID13 (controller ID), attribute ID5001 (color print is possible or not), attribute ID5002 (type of supported finishing), attribute ID5003 (highest resolution that can be set), attribute ID5004 (lowest resolution that can be set), attribute ID5005 (job queue table), and type ID500 (job queue table type) are the same as those used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those under control of the printer controller to which the attribute table belongs.
• Additionally, the attribute table of the printer controller shown inFIG. 40 is an attribute table of service ID21 (printer controller510), and the attribute tables of theprinter controllers511,512 corresponding to serviceIDs22,23 are stored inDISK315, respectively, and differ from each other.
• (Job Queue Table)
• FIG. 42 shows a job queue table retained by the printer controller. This table is retained inDISK315 as attribute values of attribute ID5005 (job queue table) of the attribute table shown inFIG. 40. The job queue table shows a state of the job managed and executed by the printer controller. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record is constituted of ajob ID2901, ajob status2902 and afile name2903 in which a job entity is retained. Thejob ID2901 is an identifier allocated to the job by the printer controller when the job is transmitted to the printer controller.FIG. 43 is a diagram showing the job status2902 (job state) ofFIG. 42:1 denotes that the job is completely executed;2 denotes that the job is being executed by the engine; and3 denotes that the job is on standby. Thejob file name2903 is a name of a file in which the job entity is retained. As shown inFIG. 52, the job entity has a plurality of sets of attribute ID, attribute value size and attribute value.
• (Attribute Table of Scanner Controller)
• FIG. 44 shows data (attribute table) retained inDISK315 by thescanner controller420. This table shows performances and functions of the scanner engine controlled by the scanner controller, and values concerning the performances and functions cannot be rewritten. In the table each line shows one information unit (record), and data is constituted as an aggregate of a plurality of records. Each record content is the same as that of Supervisor shown inFIG. 7, and is constituted ofattribute ID3001,type ID3002, andvalue3003.FIG. 45 shows values of the attribute ID and type ID of the attribute table ofFIG. 44. Attribute IDs other than attribute ID12 (controller type), attribute ID13 (controller ID), attribute ID6001 (color scan is possible or not), attribute ID6002 (maximum original size), attribute ID6003 (highest resolution that can be set), and attribute ID6004 (lowest resolution that can be set) are the same as those which are used in the Supervisor attribute table ofFIG. 7. However, setting ranges and influenced ranges are limited to those under control of the printer controller to which the attribute table belongs.
• (Structure of Command Packet)
• FIG. 46 shows a structure of the command packet transmitted to theinterpreter409 from theuser interface manager405, the TCP/IP, UDP/IP processing module406, the IEEE 1284.4 processing module407 and the SBP-2 processing module408. The command packet also shows structures of a reply packet and an event packet transmitted to theuser interface manager405, the TCP/IP, UDP/IP processing module406, the IEEE 1284.4 processing module407 and the SBP-2 processing module408 from theinterpreter409. The packet comprises apacket header3101 indicating a top of the packet, apacket version3102 indicating a packet structure version, aflag3103 indicating a packet property, anoperation code3104 indicating a type of operation to be performed, ablock number3105 used for Client (PC) to recognize the reply packet, aparameter length3106 indicating a length ofparameter3110,user ID3107 andpassword3108 for use in user authentication, astatus code3109 used only in the reply packet and indicating a general reply state, and aparameter3110 having a format determined for eachoperation code3105.
• Theparameter3110 includes access target service ID, access target attribute ID, and the like.
• Theflag3104 includes aflag3111 indicating that the packet is a command packet, event packet or reply packet, and acontinuous flag3112 indicating that data to be transmitted cannot be included in theparameter3110 and continued data is also included in the packet to be transmitted next. The length of theparameter3110 is limited to a numeral (64 Kbytes) indicative of theparameter length3106. Specifically,Client PC202 and203 connected toEthernet208 designate IP address and port number to connect with the multi-function peripheral201 and output IP packet data to Network Interface305 (107).Client PC204 connected to IEEE 1394interface206 designates node ID and LUN (logical unit number) to connect to the multi-function peripheral201 and output SBP-2 packet data to IEEE 1394 Interface306 (108).Client PC205 connected to IEEE 1284interface207 designates the socket number to connect to the multi-function peripheral201 and outputs IEEE 1284.4 packet data to IEEE 1284 Interface307 (109). ViaNetwork Interface Driver402, IEEE 1284Interface Driver403, and IEEE 1394Interface Driver404, the command packets shown inFIG. 46 with IP Header, 1284 Header, and 1394 Header added to their tops, respectively, are outputted to the TCP/IP, UDP/IP processing module406, the IEEE 1284.4 processing module407, and the SBP-2 processing module408. The TCP/IP, UDP/IP processing module406, the IEEE 1284.4 processing module407, and the SBP-2 processing module408 process the received transport packets to extract the command packets shown inFIG. 46 and transmit outputs to Interpreter/Generator409.
• (Processing of Command Packet)
• FIG. 47 shows a processing flow of the command packet in the multi-function peripheral201. Instep3201, data transmitted from theinterfaces401 to404 are processed by thetransport processing modules405 to408 to extract the command packets shown inFIG. 46. The extracted command packets, together with information of the connection type by which the data is inputted (connection type ID) and the subaddress, are transmitted to theinterpreter409 from the TCP/IP, UDP/IP processing module406, the IEEE 1284.4 processing module407, and the SBP-2 processing module408. Instep3202, theinterpreter409 refers to the subaddress to service ID table (FIG. 9) retained bySupervisor410, and compares the entered connection type ID and subaddress to obtain the service ID and to check whether or not the data input is valid. As a check result, when the data input is not valid, instep3204 the command packet is canceled to end the flow. When the data input is valid, instep3203 the command packet is analyzed based on the packet structure ofFIG. 46. As a result of the packet analysis, each item shown inFIG. 46 is outputted as independent and separate information. Instep3205, by referring to the access control table (FIG. 14) based on the service ID, the security level for the service ID is obtained.
• Instep3206, it is checked whether the security level obtained in thestep3205 is 0 or 1. When the security level is 0 or 1, data is transmitted to thedispatcher412 without checking the security level (security gate411). In thestep3206, when the security level is other than 0 and 1, instep3207 it is checked whether or not the security level is 2. When the security level is 2, instep3209 it is checked whether or not the user ID included in the command packet is in the user authentication table (FIG. 13). When the user ID is not included, it is judged that there is no authority. Instep3210 error reply information is generated, a packet is generated by the interpreter409 (fill thestatus code3109 with error information), and the packet is sent to a command packet sender.
• When the user ID is included, data is transmitted to thedispatcher412. A sender address is extracted from the transport packet (Header).
• Instep3207, when the security level is other than 2, instep3208 it is checked whether the pair of user ID and password included in the command packet is present in the user authentication table (FIG. 13). When the pair of user ID and password is not included, it is judged that there is no authority. Instep3211 the error reply information is generated, the packet is generated by theinterpreter409, and the packet is sent to the command packet sender. When the user ID is included, data is transmitted to thedispatcher412.
• Instep3212 thedispatcher412 determines a distribution addressee manager based on the service ID, and distributes to the determined manager the connection type ID and subaddress to which the data is transmitted, sender address, operation code, block number, flag information, user ID, password, parameter length and parameter. Subsequently, instep3213 each manager processes these information.
• (Access Processing of Attribute Table)
• FIG. 48 shows a processing when Client instructs reading or writing for the attribute table of each manager or controller retained by the multi-function peripheral201.
• The reading and writing for the attribute table retained by each manager or controller are performed by transmitting an appropriate command packet to the subaddress of Supervisor. In the attribute table reading command packet, as parameters, access target service ID and access target attribute ID are included. Moreover, in the attribute table writing command packet, as parameters, access target service ID, access target attribute ID and attribute value corresponding to the attribute ID are included. The packet data transmitted to the multi-function peripheral201 from Client is processed by the flow shown inFIG. 47, and distributed to Supervisor. Instep3301 it is checked whether or not theoperation code3104 is a code for reading the attribute value (“Get”). When the operation code is “Get”, instep3301 based on the service ID the entire attribute table of the access target is obtained. When the service ID is0, the attribute table ofSupervisor410 shown inFIG. 7 is obtained. When the service ID is1,2,3,4,5,6,7,8,9, the attribute table of the print job manager as shown inFIG. 18 is obtained. When the service ID is10, the attribute table of thescan job manager419 as shown inFIG. 22 is obtained. When the service ID is11,12,13,14,15,16,17,18, the attribute table of the copy job manager a shown inFIG. 24 is obtained. When the service ID is101, the attribute table of thefont manager413 as shown inFIG. 26 is obtained. When the service ID is102, the attribute table of theform overlay manager414 as shown inFIG. 29 is obtained. When the service ID is103, the attribute table of thelog manager415 as shown inFIG. 32 is obtained. When the service ID is104, the attribute table of thecolor profile manager416 as shown inFIG. 37 is obtained. When the service ID is21,22,23, the attribute table of the printer controller as shown inFIG. 40 is obtained. When the service ID is24, the attribute table of thescanner controller420 as shown inFIG. 44 is obtained. Additionally, the attribute table of the print job manager shown inFIG. 18 is an attribute table of service ID4 (print job manager504), and the attribute tables ofprint job managers501,502,503,505,506,507,508,509 corresponding to serviceID1,2,3,5,6,7,8,9, respectively, are stored inDISK315. In the same manner, the attribute table of the copy job manager shown inFIG. 24 is an attribute table of service ID18 (copy job manager608), and the attribute tables ofcopy job managers601 to607 corresponding to serviceIDs11 to17, respectively, are stored inDISK315. Furthermore, in the same manner, the attribute table of the printer controller shown inFIG. 40 is an attribute table of service ID21 (printer controller510), and the attribute tables ofprinter controllers511,512 corresponding to serviceIDs22,23, respectively, are stored inDISK315.
• Thereafter, instep3303, it is examined whether or not the designated attribute value can be obtained. The examination is performed by obtaining a value of “attribute ID list available only for the manager” (attribute ID=105) of the target attribute table, and checking whether or not the attribute ID instructed to be obtained is included. When the attribute ID is included, the value cannot be obtained. Therefore, instep3305 the error reply packet is generated, and transmitted, thereby ending the flow. When the attribute ID is not included, instep3304 the attribute table is searched based on the designated attribute ID, and pattern ID having the corresponding attribute ID and attribute value are obtained. Instep3306, based on the pattern ID the reply packet is generated, and instep3307 the reply packet is transmitted, thereby ending the flow. When instep3301 the operation code is not “Get”, instep3308 it is checked whether or not the operation code is an attribute value writing code (“Set”).
• When the operation code is “Set”, instep3309 based on the service ID an access target attribute table is entirely obtained. Thereafter, instep3310, it is examined whether or not the designated attribute value can be set. The examination is performed by obtaining a value of “attribute ID list which can be set only by the manager” (attribute ID=104) of the target attribute table, and checking whether or not the attribute ID instructed to be set is included. When the attribute ID is included, the value cannot be obtained. Therefore, instep3314 the error reply packet is generated, and transmitted, thereby ending the flow. When the attribute ID is not included, instep3311 based on the designated attribute ID the attribute table is searched, and the pattern ID having the corresponding attribute ID and attribute value are obtained. Instep3312, the attribute value designated based on the pattern ID is set, and the reply packet informing that the setting has succeeded is generated. Instep3313 the reply packet is transmitted, thereby ending the flow. Instep3308 when the operation code is not “Set”, anotherprocessing step3315 described later is performed in accordance with the operation code to end the flow.
• (Service ID List Inquiry Processing)
• FIG. 49 shows a processing when Client inquires a list of services (list of service ID) provided by the multi-function peripheral201. The inquiry for the service list is performed by transmitting an appropriate command packet to the subaddress of Supervisor, and reading and processing the subaddress to service ID table shown inFIG. 9. The flow shown inFIG. 49 shows details of the step3315 (processing of other Operation Code) of the flow shown inFIG. 48. Instep3401, it is checked whether or not the operation code is a service list obtaining code (“List Service”). When the operation code is not “List Service”,other processing step3402 described later in accordance with the operation code is performed to end the flow. Instep3401, when the operation code is “List Service”, instep3403, only the service IDs corresponding to the connection type ID used in the inquiry are extracted from the subaddress to service ID table to generate the list. Instep3404, each record of the list prepared in thestep3403 is examined. When thevalid flag804 is valid, and there is a value in thevalid user list805, the record not corresponding to the value for the user ID used in the inquiry is deleted. When there is a value in theinvalid user list806, the record corresponding to the value for the user ID used in the inquiry is deleted from the list. Instep3405, the reply packet including the service ID list updated in thestep3404 is generated, and the generated reply packet is transmitted instep3406.
• (Subaddress Inquiry Processing)
• FIG. 50 shows a processing when Client designates service ID to inquire subaddress information necessary for using the service provided by the multi-function peripheral201. The inquiry of the subaddress is performed by transmitting an appropriate command packet to the subaddress ofSupervisor410, and reading and processing the subaddress to service ID table shown inFIG. 9. The subaddress inquiry command packet includes the service ID as the parameter. The flow shown inFIG. 50 shows details of the step3402 (processing of other Operation Code) of the flow shown inFIG. 49. Instep3501, it is checked whether or not the operation code is a subaddress obtaining code (“Reserve”). When the operation code is not “Reserve”,other processing step3502 described later in accordance with the operation code is performed to end the flow. Instep3501, when the operation code is “Reserve”, instep3502, from the connection type ID used in the inquiry and the service ID designated in the parameter, the subaddress to service ID table is scanned to search for the corresponding record. For the record searched in thestep3504, it is checked whether or not the valid flag is valid. When there is a value in the valid user list, it is checked whether or not the user ID used in the inquiry is in the list. When there is a value in the invalid user list, it is checked whether no user ID used in the inquiry is in the list. As a check result, when answer is not OK, it is judged that there is no right to access (right to use) the designated service. Instep3506 the error reply packet is generated, and instep3507 the packet is sent, thereby ending the flow. As a result of the check in thestep3504, when the answer is all OK, instep3505 the reply packet including the subaddress is generated, and instep3507 the packet is sent, thereby ending the flow.
• (Task Type Designated Service ID Inquiry Processing)
• FIG. 51 shows a processing flow for designating a service type and inquiring an optimum service ID to process the designated type of service, among the services provided by the multi-function peripheral201. The inquiry of the service ID with the designated service type is performed by transmitting an appropriate command packet to the subaddress of Supervisor, and reading and processing the subaddress to service ID table shown inFIG. 9 and the service ID to task type table shown inFIG. 11. The subaddress ID inquiry command packet includes the task type for designating the service type, and a combination (condition information) for limiting the service as parameters. The condition information is shown as a list of a pair of attribute ID and value. The flow shown inFIG. 51 shows details of the step3503 (processing of other Operation Code) of the flow shown inFIG. 50. Instep3601, it is checked whether or not the operation code is a subaddress obtaining code (“Get Service”). When the operation code is not “Get Service”,other processing step3603 described later in accordance with the operation code is performed to end the flow. In thestep3601 when the operation code is “Get Service”, instep3602 from the connection type ID used in the inquiry and the subaddress to service ID table, a service ID list having the connection type ID used in the inquiry is generated. Instep3604, the service ID to task type table is referred to, and a list of service IDs having the designated task type is generated from the above-described list. Instep3605, each record of the list generated in thestep3604 is examined. When thevalid flag804 is valid, and there is a value in thevalid user list805, the record not corresponding to the value for the user ID used in the inquiry is deleted. When there is a value in theinvalid user list806, the record corresponding to the value for the user ID used in the inquiry is deleted from the list. Instep3609, the condition information included in the parameter and the attribute table of each manager for the service ID in the list are compared, and values other than values satisfying the conditions are deleted from the list. Instep3606, the number of records of the list changed in thestep3605 is checked. When the number of records is 0, it is judged that there is no requested service. Instep3611 the error reply packet is generated, and instep3613 the reply packet is sent, thereby ending the flow. In thestep3606 when the number of records is other than 0, instep3607 it is checked whether or not the number of records is 1. When the number of records is 1, instep3612 the reply packet including the obtained service ID is generated, and instep3613 the reply packet is sent, thereby ending the flow. In thestep3607, when the number of records is other than 1, instep3608, the current load state is inquired of each manager for the service ID in the list. The managers return the number of jobs being processed as the load state, and from these the manager having a lowest load is selected. Instep3610, the reply packet including the service ID of the selected manager is generated, and in thestep3613 the reply packet is sent, thereby ending the flow.
• (Job Structure)
• FIG. 52 shows an internal structure of a file (job file) which retains the job entity managed by each manager. The file name of the job file is retained in thefile name1502 of the job table (FIG. 20). The file structure also shows an internal structure of a file retaining the job entity managed by each controller. The file name is retained in thefile name2903 of the job queue table (FIG. 42). The job entity is constituted of a plurality of continuous sets ofattribute ID3701,attribute value size3702 andattribute value3703. When the job includes data, as shown in3707,3708,3709, a value indicating data as the attribute ID, file name size as the attribute value size, and file name of the file retaining the document data as the attribute value are retained. The attribute includes data transmission method, data format (used PDL, and the like), event type and information such as addressee to which event notification is sent when the event occurs, and information dependent on the job type such as, for the print job, the number of copy sheets, finishing processing designation, designation of font for use, designation of form overlay for use, and the like.
• (Job Script Processing in Each Manager)
• FIGS. 53 and 54 show a processing flow of the job script in each manager. The job script is constituted of a series of command packets shown inFIG. 46, and prescribed to start with operation code “Job Start” and end with operation code “Job End”. Each packet constituting the job script is placed in the subaddress shown by the subaddress to service ID table shown inFIG. 9, and distributed to each manager by the command packet processing flow shown inFIG. 47. The processing flow shown inFIG. 53 is a processing flow for processing the command packet distributed to each manager to generate the job file and data file shown inFIG. 52. For the operation distributed to each manager, instep3801 it is checked whether or not the operation code is a supported operation code. The check is performed by comparing with the value of attribute “supported operation” (attribute ID101) retained in the attribute table by each manager. As a result of the check, when the operation is not supported, instep3816 the error reply packet is generated and sent, thereby ending the flow. In thestep3801 when the operation code is supported, instep3802 it is checked whether or not the job is being executed. The check is performed by examining whether or not a job execution flag (flag set in step3806) is true. As a result of the examination, when the job execution flag is false, and the job is not executed, instep3804 it is checked whether or not the operation code is “Job Start”. As a result of the check, when the operation code is not “Job Start”, instep3816 the error reply packet is generated and sent, thereby ending the flow.
• When the answer to thestep3804 is OK, instep3805 the job ID is allocated to add an item to the job table (FIG. 20), and a new job file is generated. Thereafter, instep3806 the job execution flag is set to be true, thereby ending the command packet processing.
• In the check ofstep3802, when the job execution flag is true, instep3803 it is checked whether the operation code is “Send”. The operation code “Send” informs the manager that the parameter includes data constituting the job. In thestep3803 when the operation code is “Send”, in step3807 a continuation flag entered with the command is checked. When the continuation flag is true, in step3808 a new area is added to alreadypresent data file3713, and in3809 the parameter is written in the area, thereby ending the flow. In thestep3807 when the continuation flag is false, instep3810 new data file3713 is generated, and instep3811 the parameter is written in the data file. Thereafter, in step3812 a new area is added to the job file, and instep3813 theattribute ID3707 indicating data, thefile name size3708 and thefile name3709 of the new generated file are written in the area, thereby ending the flow. In thestep3803 when the operation code is not “Send”, instep3814 it is checked whether the operation code is “Job End”. When the operation code is “Job End”, instep3815 job generation processing is terminated, thereby ending the flow. The job generation terminating processing includes processings such as closing of the job file, and the like, and differs with manager types (print job, scan job, copy job, font, form overlay, log, color profile).
• In thestep3814, when the operation code is not “Job End”, instep3817 it is checked whether the operation code is “Set Job”. The operation code “Set Job” informs the manager that the parameter includes the attribute (attribute ID and attribute value) constituting the job.
• When the job operation code is “Set Job”, in step3818 a new area is added to the job file, and instep3819 the attribute ID, attribute value size and attribute value are written in the added area, thereby ending the flow.
• In thestep3817, when the operation code is not “Set Job”, instep3820 it is checked whether the operation code is “Send Request”. The operation code “Send Request” instructs the manager to transmit the data, and the data transmission method is included as the parameter. When the operation code is “Send Request”, in step3821 a processing according to each manager is performed to end the flow. In the processing of thestep3821 for the scan job manager, the scanner controller is instructed to scan the original in accordance with the attribute value retained in the job file, and to transmit obtained data in a designated method. For the font manager, the processing includes transmission of the font data designated as the attribute value in the job file immediately in a designated transmission method. In thestep3820 when the operation code is not “Send Request”, instep3822 other operation codes are processed to end the flow.
• (Structure of Job Including Document and Binder)
• FIG. 83 shows the internal structure of a file (job file) for holding the entity of the job managed by each manager. The file name of the job file is held in thejob file name1502 of the job table (FIG. 20). This file structure also shows the internal structure of the file which holds the entity of the job managed by each controller. This file name is held in thefile name2903 of the job queue table (FIG. 42). The job entity is represented by a plurality of continuous sets ofattribute ID8701,attribute value size8702 andattribute value8703. When the job includes document, as shown by8704,8705,8706, the value indicative of a document file as the attribute ID, the document file name size as the attribute value, and the document file name as the attribute value are held. Moreover, when the job includes a binder, as shown by8710,8711,8712, the value indicative of a binder file as the attribute ID, the binder file name size as the attribute value, and the binder file name as the attribute value are held. The job attribute includes a job title, a job execution priority, event type and event information such as the addressee to which event notification is transmitted when the event is generated, the information concerning the present state of the job, and the information dependent on the job type such as the number of copies in the print job, the designation of a division sheet from other jobs, and the designation of a recovery method when media are eliminated.
• (Structure of Document Including Data)
• FIG. 84 shows the internal structure of the document file held by each job file. The document file name is held in adocument file name4002 in a document table (FIG. 91) stored inDISK315. This file structure also shows the internal structure of the file which holds the entity of the document managed by each controller. The document entity is represented by a plurality of continuous sets ofattribute ID8801,attribute value size8802 andattribute value8803. When the document includes data, as shown by8807,8808,8809, the value indicative of data as the attribute ID, the file name size as the attribute value, and the name of the data holding file as the attribute value are held. The document attribute includes data transmission method, data format (such as PDL to be used), information such as data compression form, and the information dependent on the document type such as the designation of a paper supply tray for print document, the designation of media such as paper, the designation of double-surface print, print quality level, and the designation of binding margin position and amount.
• (Structure of Binder Including Document)
• FIG. 85 shows the internal structure of a binder file held by each job file. The binder file name is held in abinder file name4004 of a binder table (FIG. 92) stored inDISK315. This file structure also shows the internal structure of the file managed by each controller for holding the binder entity. The binder entity is represented by a plurality of continuous sets of anattribute ID8901,attribute value size8902 andattribute value8903. When the binder includes document, as shown by8904,8905,8906 or8910,8911,8912, the value indicative of data as the attribute ID, the file name size as the attribute value, and the name of a document data holding file as the attribute value are held. The binder attribute includes the designation of bin to be outputted for a print binder, the designation of finishing such as stapling and punch hole, the designation of sorting, and the like. Eachdocument file8913,8914 has a structure shown inFIG. 84, and the name of document file is held in thedocument file name4002 of the document table (FIG. 91). This file structure also shows the internal structure of the document entity holding file managed by each controller. The document entity is represented by a plurality of continuous sets of theattribute ID8801,attribute value size8802 andattribute value8803. When the document includes data, as shown in8807,8808,8809, the value indicative of data as the attribute ID, the file name size as the attribute value, and the data holding file name as the attribute value are held. The document attribute includes the data transmission method, data format (PDL for use, and the like), information such as data compression form, information dependent on the document type such as the designation of a paper supply tray for print document, designation of media such as paper, designation of double-surface print, print quality level, designation of binding margin position and amount, and the like.
• (Structure of Job Constituted of Binder Including a Plurality of Documents Different in PDL Used in Description)
• FIGS. 93A and 93B are diagrams showing the internal structure of job file A constituted of a binder including a plurality of documents different in PDL used in description. The name of the job file A is held in thejob file name1502 of the job table (FIG. 20).
• This structure of the job file A also shows the internal structure of the job entity holding file managed by each controller. Additionally, the file name of the job managed by the controller is held in thefile name2903 of the job queue table (FIG. 42).
• The job entity is represented by a plurality of sets of attribute ID A01, attribute value size A02, and attribute value A03. This job includes a binder, and the value indicative of binder file, the size of binder file name, and the name of binder file B are stored in the attribute ID A07, attribute ID size A08, and attribute value A09, respectively. Furthermore, as the job attributes, the job title, job execution priority, information such as the event type and the addressee of the notification when the event is generated, and information of the present state of the job are held. Moreover, the information dependent on the job type such as the number of copies in the print job, the designation of a division sheet for preventing other jobs from being mixed, and the recovery method when media are eliminated are also held.
• The name of the binder file B is stored in thebinder file name4004 of the binder table (FIG. 92) stored inDISK315. The binder file structure also shows the internal structure of the binder entity holding file which is managed by each controller. The binder entity is represented by a plurality of sets of attribute ID B01, attribute value size B02, and attribute value B03. This binder includes a plurality of documents, and the value indicative of the document file, the document file name size, and the name of the file which holds the document file are stored in the attribute IDs B04 and B10, attribute ID sizes B05 and B11, and the attribute values B06 and B12, respectively. Moreover, as the binder attributes, for example, the designation of the bin to be outputted in the print binder, the designation of finishing such as stapling and punched hole, and the designation of sorting are held.
• The names of two document files C and D held by the binder file are stored in thedocument file name4002 of the document table (FIG. 91) stored inDISK315. The document file structure also shows the internal structure of a document entity holding file which is managed by each controller. For example, in the document file C, the document entity is represented by a plurality of sets of attribute ID C01, attribute value size C02, and attribute value C03, and in the document file D, it is represented by a plurality of sets of attribute ID D01, attribute value size D02, and attribute value D03. When the document includes data, the value indicative of data, the size of the data file, and the name of the data holding file are stored in attribute IDs C10 and D10, attribute sizes C11 and D11, and attribute values C12 and D12, respectively. Moreover, some of the document attributes indicate the format of data, such as PDL in which data is described. For example, in the document file C, the value indicative of a data format (PDL) is stored in attribute ID C04, the size of the value indicative of a data format type is stored in attribute value size C05, and the value indicative of a data format type is stored in attribute value C06. Similarly, in the document file D, the value indicative of the data format (PDL) is stored in attribute ID D04, the size of the value indicative of the data format type is stored in attribute value size D05, and the value indicative of the data format type is stored in attribute value D06. Additionally, the data transmission method, the data compression form, and the like are held as the document attributes. Moreover, the information dependent on the document type, such as the designation of the paper supply tray in the print document, the designation of media such as paper, the designation of double-surface print, the designation of the print quality level, the designation of the binding margin position and amount, and the like are held.
• (Job Script Processing in each manager)
• FIGS.86 to90 show a processing flow of a job script in each manager. The job script is constituted of a series of command packets shown inFIG. 46, and is defined to start with “Job Start” operation code and to end with “Job End” operation code. Each packet constituting the job script is executed on the subaddress shown by the subaddress to service ID table ofFIG. 9, and distributed to the managers by the command packet processing flow shown inFIG. 47. In the processing flows shown by FIGS.86 to90, the command packets distributed to the managers are processed to prepare the job file, binder file, document file and data file shown in FIGS.83 to85.
• Instep9101,CPU301 checks whether or not the operation code distributed to each manager is an operation code supported by each manager. The checking is performed by comparing with the value of “Supported Operation” attribute (attribute ID101) held by each manager in the attribute table. As a result of the check, when the operation is not supported, instep9111 an error reply packet is prepared and sent, thereby ending the flow.
• When in thestep9101 the operation code is supported, it is checked instep9102 whether or not job execution flag is ON. The checking is performed by examining whether or not the job execution flag (the flag set in step9106) stored in the predetermined area ofRAM302 is true. Additionally, this job execution flag is set to be false in default. Subsequently, as a result of the examination, when the job execution flag is false, and the job execution flag is not turned on, it is checked instep9104 whether the operation code is “Job Start”. As a result of the check, when the operation code is not “Job Start”, in thestep9111 the error replay packet is prepared and sent, thereby ending the flow. When the check of thestep9104 results in OK, instep9105 the job ID is allocated to add an item to the job table (FIG. 20), so that a new job file is generated inDISK315.
• Subsequently, instep9106, the job execution flag is set to be true, thereby ending the processing of the command packet.
• In the check of thestep9102, when the job execution flag is true, it is checked instep9103 whether the binder is being processed. The checking is performed by examining whether a binder processing flag (the flag set in step9403) stored in the predetermined area ofRAM302 is true. The binder processing flag is set to be false in default. Subsequently, as a result of the examination, when the binder processing flag is true, and the binder is being processed, the step advances to the binder processing of Fog.87. Moreover, as a result of the examination, when the binder processing flag is false, and the binder is not being processed, it is checked instep9107 whether the document is being processed. The checking is performed by examining whether a document processing flag (the flag set in step9406) stored in the predetermined area ofRAM302 is true. This document processing flag is set to be false in default. Subsequently, as a result of the examination, when the document processing flag is true, and the document is being processed, the step advances to the document processing ofFIG. 88. Moreover, as a result of the examination, when the document processing flag is false, and the document is not being processed, it is checked instep9108 whether the operation code is “Set Job”. The operation code “Set Job” instructs to the manager that the attribute (attribute ID and attribute value) constituting the job is included in the parameter. When the job operation code is “Set Job”, in step9109 a new area is added to the job file ofDISK315, and instep9110 the attribute ID, attribute value size and attribute value are written in the added area, thereby ending the flow. In thestep9108, as a check result, when the operation code is not “Set Job”, the flow advances to the processing ofFIG. 89.
• It is checked instep9201 whether the operation code is “Set Binder”. The operation code “Set Binder” instructs to the manager that the attribute (attribute ID and attribute value) constituting the binder is included in the parameter. When the operation code is “Set Binder”, in step9202 a new area is added to the binder file ofDISK315, and instep9203 the attribute ID, attribute value size and attribute value are written in the added area, thereby ending the flow. In thestep9201, as a check result, when the operation code is not “Set Binder”, it is checked instep9204 whether the operation code is “Binder End”. As a check result, when the operation code is “Binder End”, in step9205 a binder generation processing is executed and terminated. As a check result, when the operation code is not “Binder End”, instep9206 other operation processings are executed and terminated.
• It is checked instep9301 whether the operation code is “Set Document”. The operation code “Set Document” instructs to the manager that the attribute (attribute ID and attribute value) constituting the document is included in the parameter. When the operation code is “Set Document”, in step9302 a new area is added to the document file ofDISK315, and instep9303 the attribute ID, attribute value size and attribute value are written in the added area, thereby ending the flow. For example, the value indicative of the format of the data in the document file is written as the attribute ID, the size of the value indicative of the data format type is written as the attribute value size, and the value indicative of the data format type is written as the attribute value.
• In thestep9301, as a check result, when the operation code is not “Set Document”, it is checked instep9304 whether the operation code is “Document End”. As a check result, when the operation code is “Document End”, in step9305 a document file generation processing is executed and terminated. As a check result, when the operation code is not “Document End”, the flow advances to the processing ofFIG. 90.
• It is checked instep9401 whether the operation code is “Binder Start”. As a check result, when the operation code is “Binder Start”, instep9402 the binder ID is allocated to add an item to the job table (FIG. 92) stored inDISK315, so that a new binder file is generated inDISK315. Subsequently, instep9403, a binder processing flag indicating that the binder is being processed is set to be true, thereby ending the processing of the command packet. In thestep9401, when the operation code is not “Binder Start”, it is checked instep9404 whether the operation code is “Document Start”. As a check result, when the operation code is “Document Start”, in step9405 a document ID is allocated, an item is added to the document table (FIG. 91) stored inDISK315, so that a new document file is generated in the document file. Subsequently, instep9406, a document processing flag indicating that the document is being processed is set to be true, thereby ending the command packet processing. When the operation code is not “Document Start” in thestep9404, it is checked instep9407 whether the operation code is “Job End”. When the operation code is “Job End”, the job generation process is executed and terminated instep9408. The job generating/terminating processing includes processings such as the closing of the job file, and differs with the manager type (print job, scan job, copy job, font, form overlay, log, color profile). In thestep9407, as a check result, when the operation code is not “Job End”, instep9409 other operation processings are executed and terminated.
• It is checked instep9501 whether the operation code is “Send”. The operation code “Send” indicates to the manager that the data constituting the document is included in the parameter. When the operation code is “Send”, it is checked instep9502 whether a continuation flag inputted with the command is ON. When the continuation flag is true, in step9503 a new area is added to the already present data file8813 ofDISK315, and instep9504 data is written in the area, thereby ending the flow. When the continuation flag is false in thestep9502, instep9505 new data file8813 is generated inDISK315, and instep9506 the data is written in the data file. Thereafter, in step9507 a new area is added to the document file ofDISK315, and instep9508attribute ID8807 indicating the data,file name size8808 and a new generatedfile name8809 are written in the area, thereby ending the flow. When the operation code is not “Send” in thestep9501, it is checked instep9509 whether the operation code is “Send Request”. The operation code “Send Request” instructs the data transmission to the manager, and includes the data transmission method as the parameter. When the operation code is “Send Request”, instep9510 the job generation process dependent on each manager is executed and terminated. The processing in thestep9510 comprises, for the scan job manager, instructing the scanner controller to scan the original in accordance with the attribute value held in the job file, and transmitting the obtained data in a designated method, and comprises, for the font manager, immediately transmitting the font data designated as the attribute value in the job file in a designated transmission method. When the operation code is not “Send Request” in thestep9509, other operation code processings are executed and terminated instep9511.
• As described above, the job script inputted from Client PC (202 to205) and constituted of the packet data is analyzed by the multi-function peripheral201 to generate the job file. The job script and job file indicate the scanner control script and file for controlling the scanner engine of the multi-function peripheral201. The job script and job file indicate the laser beam printer control script and file for controlling the laser beam printer engine of the multi-function peripheral. The job script and job file further indicate the ink jet printer control script and file for controlling the ink jet printer engine of the multi-function peripheral201. Moreover, the job script can constitute one or a plurality of documents in the job script (two-hierarchy structure), and the multi-function peripheral201 generates the job file after analyzing the job script, and can further generate one or a plurality of document files as the hierarchical structure in the job file. Moreover, the job script, and the job file and document file having the hierarchical structure indicate the scanner job control script and file for performing the scanner control of the multi-function peripheral201. Furthermore, the job script, or the job file and document file having the hierarchical structure indicate the printer job control script and file for performing the laser beam printer control of the multi-function peripheral201. Additionally, the job script, and the job file and document file having the hierarchical structure indicate the printer job control script and file for performing the ink jet printer control of the multi-function peripheral201. Moreover, the job script can constitute one or a plurality of documents in the job script, each binder can constitute one or a plurality of documents (three-hierarchy structure), and the multi-function peripheral201 generates the job file after analyzing the job script, generates one or a plurality of binder files as the hierarchical structure in the job file, or can generate one or a plurality of document files as the hierarchical structure in the job file or the binder file. Moreover, the job script, or the job file and document file having the hierarchical structure indicate the scanner job control script and file for performing the scanner control of the multi-function peripheral201. Furthermore, the job script, and the job file, binder file and document file having the hierarchical structure indicate the printer job control script and file for performing the laser beam printer control of the multi-function peripheral201. Additionally, the job script, and the job file, binder file and document file having the hierarchical structure indicate the printer job control script and file for performing the ink jet printer control of the multi-function peripheral201.
• (Job Processing in Print Job Manager)
• FIG. 55 shows a job processing flow in theprint job managers501 to509 shown inFIG. 5. The print job manager operates a task of constantly monitoring the job table. The print job manager performs the job script processing flow shown inFIG. 54. Subsequently, when it is detected that a new item is added to the job table by input of operation code “Job Start”, the monitor task operates a task having the processing flow shown inFIG. 55 to process the input job.
• The job has the hierarchical structure constituted of the binder and document, and one job can have a plurality of documents. In this case, the data format (e.g., PDL used for describing the document data), and the like of the document data can be set for each binder, or document. Additionally, the following flowchart shows a processing performed by the print job manager for each document data.
• Instep3901 the manager waits until an attribute indicating a PDL (Page Description Language) type used in representation of data (document data) is added to the job file. When the PDL type is determined, the manager waits until PDL Rasterizer for use (PDL Rasterizer417 or418) can be used. In thestep3901 when the PDL Rasterizer becomes ready for use, instep3902 the manager waits until the attribute indicating data reception method is added to the job file. When the attribute indicating the data reception method is added to the job file, instep3903 the data reception method is checked. When the data reception method comprises accessing an external source (e.g., Client PC on the network, and the like) of the multi-function peripheral201, in step3904 a task for reading the designated data is generated to access the external source. Subsequently, in thestep3905 the manager waits for start of the data reading. When in thestep3903 data is included in the job (inFIG. 54 in data reception by operation code “Send”), instep3906 the manager waits for start of data reception.
• When in thestep3905 or3906 the data reading or reception is started, instep3907 data starts to be handed to PDL Rasterizer. Subsequently, instep3908 image data is received from PDL Rasterizer. Instep3909 the printer controller to be used is determined. The determination includes a case where the controller is predetermined by the attribute ID2001 (list of Controller ID executing Job) of the attribute table of theprint job managers501 to507 and509, and a case where attribute ID2002 (Controller automatic selection is possible or not) of theprint job manager508 is designated to be possible and the printer controller necessary for print is dynamically determined by reading the print job file content (attribute ID and attribute value of the job file shown inFIG. 52). In this case, for example, if color printing is designated by the attribute ID and attribute value in the job file, Ink Jet Controller512 (CID23) is determined. When the use of Finisher is designated by the attribute ID and attribute value, LBP Controller510 (CID21) is determined. When the printer controller is determined, instep3910 image data is handed to each printer controller and job ID is received from the printer controller. Instep3911 in the job request table (FIG. 21), the job ID, printer controller ID, and job ID received from the printer controller are recorded as separate record for each printer controller. Subsequently, instep3912 the print job manager waits for job end in each printer controller. When the job end is notified from the printer controller, instep3913 the corresponding record is deleted from the job request table. Instep3914 it is checked whether all the requested jobs of the printer controllers are finished. When the job still remains in the printer controller, the flow returns to thestep3912 to wait for the job end in the printer controller. When in thestep3914 the requested jobs in all the printer controllers are finished, instep3915 the job record is deleted from the job table (FIG. 20). In this case, the event transmission processing shown inFIG. 61 is performed.
• Instep3916, the job file is searched, and instep3917 it is checked whether there is an attribute value instructing the event transmission concerning the job end. If not, the processing ends. When the attribute value is present, instep3918 the attribute value is read to obtain the transmission method and addressee. Instep3919 the event transmission packet is generated, and the event is sent to the designated transmission method and addressee. Instep3920, termination processings such as deletion of the job and data files, and the like are performed, thereby ending the job processing.
• (Job Processing in Scan Job Manager)
• FIG. 56 shows a job processing flow in thescan job manager419. After the handing of the job is finished, the scan job manager starts a job processing. Therefore, the scan job manager starts the job processing ofFIG. 56 as the job termination processing of thestep3815 inFIG. 54. Instep4001, the job is handed to thescanner controller420 and job ID is received. Instep4002, to the job request table (FIG. 21), the job ID, scanner controller ID, and job ID received from thescanner controller420 are recorded. Instep4003 the scan job manager waits for job end from thescanner controller420. When the job end is notified from thescanner controller420, scanned image data is received from thescanner controller420, and instep4004 the job record is deleted from the job table (FIG. 20). In this case, the event transmission processing shown inFIG. 61 is performed. In step4005 the job attribute data is searched for the attribute instructing the data transmission method. When instep4006 for the data transmission method the data is instructed to be sent as a script, instep4008 the data is transmitted with other attribute information as the script. Details of processing for data transmission from the apparatus are shown inFIG. 62. When in thestep4006 reference transmission of data is instructed, instep4007 the data is stored in the apparatus, and reference information for the data is transmitted with the other attribute information as the script. Instep4010 the job file is searched, and instep4011 it is checked whether there is an attribute value instructing the event transmission concerning the job end. If not, the processing ends. When the attribute value is present, instep4012 the attribute value is read to obtain the transmission method and addressee. Instep4013 the event transmission packet is generated, and the event is sent to the designated transmission method and addressee. Instep4014, termination processings such as deletion of the job and data files, and the like are performed, thereby ending the job processing.
• (Job Processing in Copy Job Manager)
• FIG. 57 shows a job processing flow in thecopy job managers601 to608. After the handing of the job is finished, the copy job manager starts a job processing. Therefore, the copy job manager starts the job processing ofFIG. 57 as the job termination processing of thestep3815 inFIG. 53. Instep4101, the job is handed to thescanner controller420 and job ID is received. Instep4102, to the job request table (FIG. 21), the job ID, scanner controller ID, and job ID received from thescanner controller420 are recorded. Instep4103 the manager waits for job end from thescanner controller420. When the job end is notified from thescanner controller420, scanned image data is received from thescanner controller420, and instep4104 the job record is deleted from the job table (FIG. 20). Subsequently, instep4105 the printer controller to be used is determined. The determination includes a case where the controller is predetermined by the attribute ID2001 (list of Controller ID executing Job) of the attribute table of thecopy job managers601 to607 and609, and a case where attribute ID2002 (Controller automatic selection is possible or not) of thecopy job manager608 is designated to be possible and the printer controller necessary for print is dynamically determined by reading the job file content (attribute ID and attribute value of the job file shown inFIG. 52). In this case, for example, if color printing is designated by the attribute ID and attribute value in the job file, Ink Jet Controller512 (CID23) is determined. When the use of Finisher is designated by the attribute ID and attribute value, LBP Controller510 (CID21) is determined. When the printer controller is determined, instep4106 the image data received from thescanner controller420 is handed to each printer controller and job ID is received from the printer controller. Instep4107, to the job request table (FIG. 21), the job ID, printer controller ID, and job ID received from the printer controller are recorded as separate record for each printer controller.
• Subsequently, instep4108 the print job manager waits for job end in each printer controller. When the job end is notified from the printer controller, instep4109 the corresponding record of the finished job is deleted from the job request table. Instep4110 it is checked whether all the requested jobs of the printer controllers are finished. When the job still remains in the printer controller, the flow returns to thestep4108 to wait for the job end in the printer controller.
• When in thestep4110 the requested jobs in all the printer controllers are finished, instep4111 the job record is deleted from the job table (FIG. 20). In this case, the event transmission processing shown inFIG. 61 is performed. Instep4112, the job file is searched, and instep4113 it is checked whether there is an attribute value instructing event transmission concerning the job end. If not, the processing ends. When the attribute value is present, instep4114 the attribute value is read to obtain the transmission method and addressee. Instep4115 the event transmission packet is generated, and the event is sent to the designated transmission method and addressee. Instep4116, termination processings such as deletion of the job and data files, and the like are performed, thereby ending the job processing.
• (Job Processing Download)
• FIG. 58 shows a flow concerning a data download function in the job processing flows in thefont manager413,form overlay manager414,log manager415 andcolor profile manager416. In the job for the managers, the data managed by each manager is downloaded and uploaded. For management such as reference and deletion of the data managed by each manager, the command packet is handed to the subaddress managed bySupervisor410 and the attribute table of each manager is accessed as shown inFIG. 48. After the handing of the job is finished, each manager starts a job processing concerning data download. Therefore, each manager starts the job processing concerning the data download ofFIG. 58 as the job termination processing of thestep3815 inFIG. 53. Instep4201, the job file (FIG. 52) is scanned, and it is checked whether there is an attribute concerning data reception method. As a result of the check, when the attribute concerning the data reception method is not present, it is judged that the job file is for upload and the processing flow shown inFIG. 59 is already performed. In step4208 a termination processing is performed. In the termination processing of thestep4208 the job file is deleted. When in thestep4201 the attribute concerning the data reception method is present, instep4202 the data reception method is checked. When the data reception method is included in the job (in the data reception by operation code “Send” inFIG. 53), data is already received. Therefore, instep4205 the received data is stored as a file. When in the data reception method the data is present outside the apparatus, instep4203 the designated external source is accessed to obtain the data, and instep4205 the obtained data is stored as the file. Instep4206 the file information stored in thestep4205 is registered in the management table managed by each manager (the font table (FIG. 28) by thefont manager413, form overlay table (FIG. 31) by theform overlay manager414, log table (FIG. 34) by thelog manager415, or color profile table (FIG. 39) by the color profile manager416) by writing a new record thereto. Instep4207, termination processings such as deletion of the job and data files, and the like are performed, thereby ending the job processing.
• (Job Processing Upload)
• FIG. 59 shows a flow concerning a data upload function in the job processing flows in thefont manager413,form overlay manager414,log manager415 andcolor profile manager416. When operation code “Send Request” constituting the job script is handed, each manager starts a job processing concerning data upload. Therefore, as a processing dependent on each manager of thestep3821 inFIG. 54, each manager starts the job processing concerning the data upload ofFIG. 59. Instep4301, the attributes in the job file (FIG. 52) are checked for the attribute instructing the data transmission method. When instep4301 the data transmission method instructs transmission of data as the script (No), instep4303 the data designated in the job is transmitted as the script with other attribute information. The data transmission processing from the apparatus is shown in detail inFIG. 62. When in thestep4301 reference transmission of the data is instructed, reference information concerning the data designated in the job is transmitted as the script with the other attribute information.
• (Job Management in Manager)
• FIG. 60 shows a processing flow performed when Client gives an operation instruction (job deletion) for the jobs managed by theprint job managers501 to509, scanjob manager419 andcopy job managers601 to608 in the multi-function peripheral,201. The operation for the job managed by each manager is performed by transmitting an appropriate command packet to the subaddress of Supervisor. The job managing command packet includes a service ID for specifying a target job manager, and a target job ID as parameters. The command packet transmitted to the multi-function peripheral201 from Client is processed by the flow shown inFIG. 47, and distributed toSupervisor410. The processing flow shown inFIG. 60 shows details of the step3603 (processing of other Operation Code) in the flow shown inFIG. 51. Instep4401,Supervisor410 checks whether the operation code is for deleting the job (“Cancel Job”). When the operation code is not “Cancel Job”,other processing step4409 described later in accordance with the operation code is performed to end the flow. When in thestep4401 the operation code is “Cancel Job”, instep4402, in accordance with the service ID designated in the parameter, the parameter is transmitted to each manager corresponding to the service ID. Instep4403, each manager searches the job request table managed by each manager for a designated job ID. When instep4404 the job request table has no designated job ID, it is judged that the job in the controller is already finished. Instep4410 the corresponding record is deleted from the job table, and instep4411 the reply packet is generated and sent, thereby ending the flow. When in thestep4404 the designated job ID is present in the job request table, in step4405 a controller job ID corresponding to the designated job ID and controller ID of the controller executing the job are obtained. Instep4406 the job ID of the controller corresponding to the controller ID is designated to instruct the controller to delete the job. Instep4407, the manager waits for an execution result from the controller. When the execution result is unsuccessful, instep4409 the error reply packet is generated and sent, thereby ending the flow. When in thestep4407, the execution result from the controller is successful, instep4408 the corresponding record is deleted from the job request table, and instep4403 the job request table is searched to again check whether a request for another controller is made.
• (Event Transmission)
• FIG. 61 shows a processing flow of event transmission in each manager. Each manager has the event setting table as shown inFIG. 16 as the value of the attribute table retained by itself. As shown in the description ofFIG. 16, in the table listed are the connection type and addressee to which the event is transmitted when the event occurs are written. When a certain event occurs, each manager recognizes the event ID for the event. Subsequently, instep4501, the event setting table is searched to confirm whether the event ID is registered. When in thestep4502 no event ID is registered, the processing is ended. When in thestep4502 even one event ID is registered, instep4503 the connection type for use in the event transmission and the addressee to which the event is transmitted are obtained from the first record, and instep4504 the event transmission packet is generated. Added to the packet are the parameter prescribed for each event ID and the parameter according to the format of each event ID registered in the event format table (FIG. 17) retained bySupervisor410. Instep4505, the event transmission packet is transmitted to the transmission addressee of the connection type obtained in thestep4503. Subsequently, instep4506 it is judged whether or not all records having event IDs are completed by repeating thesteps4503 to4505. If not, the flow returns to thestep4503. When all the records are processed, the processing is ended.
• (Data Script Transmission from Multi-Function Peripheral)
• FIG. 62 shows a processing flow when data is transmitted as a script of continuous command packet from the multi-function peripheral201. The processing flow is used in thestep4008 of transmitting the image data obtained as the result of the scan job, thestep4303 of transmitting the font data, and the like. Instep4601, a packet including a data attribute is generated and sent. If necessary, thestep4501 is repeated to send a plurality of attributes. Instep4602, designated data for transmission is obtained. Since the command packet has a structure shown inFIG. 46 and the size which can be transmitted as the parameter is limited, in4603 a data length is examined. As a result of examination, when the data length exceeds a limit length (64 Kbytes), instep4606 the data is cut to the limit value of length, and instep4607 the command packet with the obtained data added thereto as the parameter is generated and sent. In the command packet, operation code “Send” is set, and the continuation flag is set to be true. In step4608 a rest of the cut data is obtained, and in thestep4603 the data length is again examined. As a result of the examination of thestep4603, when the data length is within limits of the command packet, instep4604 the command packet with the data added thereto as the parameter is generated and sent. In the command packet, operation code “Send” is set, and the continuation flag is set to be false. In step4605 a command packet including remaining attributes is generated and sent. If necessary, thestep4501 is repeated, and a plurality of attributes are sent, thereby ending the flow.
• (Hard Configuration of Client PC)
• FIG. 63 is a diagram showing a common hardware configuration (controller) ofClient PC202 to205 of the embodiment shown inFIG. 2. Inside the controller,CPU6001 is connected via a bus6010 to Memory (RAM)6002, adisplay6003 such as CRT, apointing device6004 such as a keyboard, a mouse, and the like,ROM6008, andDISK6009. Various programs and data shown inFIG. 77 are stored in DISK6009 (storage medium) such as a hard disk, a floppy disk, and the like, are sequentially read into Memory (RAM)6002 if necessary, and executed byCPU6001. TheDISK6002 may be detachably attached to Client PC or incorporated in Client PC. Furthermore, the program shown inFIG. 77 may be configured to be downloaded from other Client PC orMFP201 via the network interface cable208 (10 BASE-T), IEEE 1394interface cable206, and IEEE 1284interface cable207 and stored inDISK6009. The hardware shown inFIG. 63 constitutes general Client PC shown inFIG. 78. WhenCPU6001 writes data to thedisplay6003, display is performed. WhenCPU6001 reads data from thepointing device6004, the instruction from the user is entered. Moreover, to the bus6010 anetwork interface connector6005, IEEE 1394interface connector6006, and IEEE 1284interface connector6007 are connected. Then, Ethernet (10 BASE-T)cable208, IEEE 1394cable206, and IEEE 1284cable207 shown inFIG. 2 are connected. WhenCPU6001 reads or writes data via these interfaces, communication is performed using the interfaces.
• (Software Configuration of Client PC)
• FIG. 64 shows a part of a block diagram of software (control program) ofClient PCs202 to205 using the multi-function peripheral201. The software (control program) and data used by Client PC are stored inDISK6009 as shown inFIG. 77. Via auser interface501, drivers andutilities505 to514 display information of the multi-function peripheral201 on thedisplay6003. A database502 (DISK6009) retains information (data) of the currently operated multi-function peripheral201. When Client connects to the multi-function peripheral201, anapparatus information obtainer503 obtains all information of the apparatus and retains the information in thedatabase502. A prescribed information database504 (DISK6009) retains meanings of attributes, data pattern for each attribute ID, parameter format prescribed for each event ID, meanings of task types, Supervisor subaddress, and other prescribed information which are used in each attribute table retained by the multi-function peripheral201. The drivers andutilities505 to514 are operated based on the prescribedinformation database504 and theapparatus information database502. Aprinter driver505 generates a print job script by an instruction from application program operating on Client PC. Ascanner driver506 generates a scan job script by an instruction from the application program operating on Client PC. Acopy driver507 generates a copy job script by an instruction from the application program operating on Client PC. Afont management utility508 generates a job for downloading and uploading font data, and generates a command for managing the font data. A formoverlay management utility509 generates a job for downloading and uploading form overlay data, and generates a command for managing the form overlay data. Alog management utility510 generates a job for downloading and uploading log data, and generates a command for managing the log data. A colorprofile management utility511 generates a job for downloading and uploading color profile data, and generates a command for managing the color profile data. Ajob management utility512 generates a command for performing management such as deleting, temporary stopping, and re-executing of the print job, scan job and copy job. Anapparatus management utility513 generate a command for obtaining states of the printer controller and scanner controller. Acharge management utility514 generates a command for obtaining charge data.
• Agenerator515 generates a command packet based on commands generated by the drivers andutilities505 to514. The generated command packet is transmitted to the multi-function peripheral201 usingtransport processing modules517,519,521. Thegenerator515 interprets reply packets and event packets transmitted from thetransport processing modules517,519,521, and distributes the packets to appropriate drivers or utilities. An SBP-2processing module517 is a transport layer of IEEE 1394.Numeral519 denotes a TCP/IP, UDP/IP processing module. An IEEE 1284.4processing module521 is a transport layer of IEEE 1284. Aninterface518 processes an IEEE 1394 physical layer.Numeral520 denotes a network interface. Aninterface522 processes an IEEE 1284 physical layer.FIG. 64 also shows an internal configuration of theuser interface manager405 in the software (control program) block diagram (FIG. 4) of the multi-function peripheral201. In theuser interface manger405, the SBP-2processing module517, TCP/IP, UDP/IP processing module519, IEEE 1284.4processing module521,network interface518,network interface520, and IEEE 1284interface522 inFIG. 64 are not disposed, and thegenerator515 is directly connected to theinterpreter409 inFIG. 4, whereby the command packet, reply packet and event packet are exchanged. The direct connection is not present in the software (control program) configurations ofother Client PCs202 to205.
• (Packet Generation/Transmission Processing)
• FIG. 65 shows a processing flow in which thegenerator515 receives the commands or the job scripts from the drivers andutilities505 to514, generates the command packet shown inFIG. 46 and transmits the packet to the multi-function peripheral201. Before the processing flow, an appropriate subaddress of a multi-function peripheral of a transmission addressee is connected beforehand. Information concerning the subaddress to be connected is obtained by a flow for obtaining apparatus information shown inFIG. 66. The job script is defined by a continuous command. When a processing target is a job script, steps4701 to4706 are repeated until all commands are processed. In the following description, the issuance of the job script means that thesteps4701 to4707 are processed for each command. Instep4701, a length of data to be transmitted with the command is examined. As a result of examination, when a parameter limit value of length (64 Kbytes) is exceeded, instep4702 the data is cut to the limit value of length. For the cut data, in step4703 a continuation flag is set to be true and a packet including an operation code corresponding to the command is generated, and instep4704 the packet is sent. When in thestep4701 the data length is within parameter limits of the length, instep4705 the continuation flag is set to be false and a packet including the operation code corresponding to the command is generated, and instep4706 the packet is sent.
• (Information Obtaining in Client and Software Automatic Configuration)
• FIG. 66 shows a processing flowchart of theapparatus information obtainer503 ofFIG. 64. Immediately after Client connects to the multi-function peripheral201, theapparatus information obtainer503 performs a processing shown inFIG. 66 to obtain the apparatus information and retain the information in the apparatus information database502 (DISK6009). This processing is also performed again when an event for changing the configuration is transmitted from the apparatus. Instep4801, Client PC connects to the multi-function peripheral201.
• Specifically,Client PCs202 and203 connected toEthernet208 designate IP address and port number to connect to the multi-function peripheral201 and output IP packet data.Client PC204 connected to IEEE 1394interface206 designates node ID and LUN (logical unit number) to connect to the multi-function peripheral201 and outputs SBP-2 packet data.Client PC205 connected to IEEE 1284interface207 designates the socket number to connect to the multi-function peripheral201 and outputs IEEE 1284.4 packet data. For the subaddress of the connection addressee, the subaddress for Supervisor prescribed beforehand for each connection type used in connection is used. The prescribed value is obtained from the prescribed information database504 (DISK6009). Instep4802, a value of attribute ID100 (list of attribute ID) of Supervisor attribute table shown inFIG. 7 is obtained. The attribute value is obtained by generating an attribute value obtaining command (Get) by the use of Supervisor service ID and attribute ID as parameters, and transmitting the command to thegenerator515. Thegenerator515 performs the processing flow ofFIG. 65, and transmits the command packet for obtaining the attribute value to the multi-function peripheral201. The multi-function peripheral201 receives the command packet, and returns to Client the attribute value of the attribute ID designated by performing the processing flow ofFIGS. 47 and 48. Client analyzes the reply packet by the generator, and transmits the packet to the apparatus information obtainer. Additionally, the attribute ofattribute ID100 is a list of all attribute IDs in the Supervisor attribute table. Instep4803 the attribute ID is designated to obtain the attribute value, the processing is repeated until the attribute values of all the attribute IDs are obtained instep4804, and the attribute values are stored together with the attribute IDs in theapparatus information database502. In the above steps the attribute tables (FIG. 7) of Supervisor are all stored in theapparatus information database502.
• Subsequently, in step4805 a service ID list (the SID to TASK TYPE table shown inFIG. 11) is obtained from the attribute table stored in the apparatus information database502 (DISK6009). Additionally, the service ID may also be obtained by generating a service ID list inquiry command (LIST SERVICE), and transmitting the command to thegenerator515. In this case, the multi-function peripheral201 executes the processing flow shown in FIGS.47 to49. Insteps4806 to4811, each manager information is obtained for each service ID obtained in thestep4805. Instep4806 from the list shown inFIG. 11, a service. ID1 (print job manager501) as a first service ID of service IDs except Supervisor (service ID0) is obtained. Instep4807 the subaddress corresponding to the service ID is obtained. The subaddress is obtained by generating a command (Reserve) for obtaining the subaddress using the service ID as the parameter, and handing the command to thegenerator515. In this case, in the multi-function peripheral201, the processing flow shown in FIGS.47 to50 is executed. The obtained subaddress is stored in theapparatus information database502. Instep4808, the value of attribute ID100 (list of attribute ID) of each manager attribute table is obtained. The attribute value is obtained by designating service ID and attribute ID for each manager as the parameters, generating a command (Get) for obtaining the attribute value, and transmitting the command to thegenerator515. Instep4809 the attribute ID is designated to obtain the attribute value, instep4810 processing is repeatedly performed until the attribute values of all attribute IDs are obtained, and the attribute values are stored with the attribute IDs in theapparatus information database502. Instep4811 it is judged whether or not the service ID is a final service ID in the list. When the service ID is not final, instep4812 the next service ID is obtained from the list and the processing is repeated from thestep4807. Instep4811 the attribute values of all the service IDs (print job managers501 to509, scanjob manager419,copy managers601 to608,font manager413,form overlay manager414,log manager415,color profile manager416,printer controllers510 to512, scanner controller420) of the service ID list are stored with the attribute IDs in theapparatus information database502. Subsequently, instep4813, based on the apparatus information (data) stored in the apparatus information database502 (DISK6009), user interfaces are automatically formed for managers corresponding to the drivers and utilities (control program)505 to514. The processing of the automatic formingstep4813 includes updating of the user interface, and display of set screen (user interface) is changed in accordance with the drivers and utilities. For example, as shown inFIGS. 81 and 82 showing display screens on thedisplay6003, the printer driver user interface changes displays of supported PDL list based on the attribute value ofattribute ID1101 of each print job manager (501 to509), availability of color printing based onattribute ID1102, supported Finishing type based on the attribute value ofattribute ID1103, settable highest resolution based on the attribute value ofattribute ID1104, and settable lowest resolution based onattribute ID1105.
• Likewise, displays of the user interface for theother drivers506,507,utilities508 to514 are changed in accordance with the attributes. Furthermore, icons of the drivers and utilities (print manager, copy job manager, and the like) are displayed in such a manner that they can be distinguished. Finally, instep4814,Supervisor410 is disconnected, and the processing is ended.
• (Job Issuance with designated Task Type)
• FIG. 67 shows a processing when each application or utility issues a job script with a designated task type. The job with a designated service ID is issued by searching theapparatus information database502 using the service ID as a key, and transmitting an appropriate job script to the obtained subaddress. When only the task type is designated by an instruction from the user, however, a request for introduction of service ID to be used needs to be made for the multi-function peripheral201.FIG. 67 shows a processing for this case. Instep4901, the task type is designated, an attribute value obtaining command is generated to obtain the service ID, and the command is transmitted to thegenerator515. In the multi-function peripheral201 the processing flow shown in FIGS.47 to51 is executed. Instep4902, based on the service ID obtained in thestep4901 theapparatus information database502 is searched, and the job script is transmitted to the obtained subaddress.
• (Event Structure)
• FIG. 68 shows a structure of the event transmitted to Client from the multi-function peripheral201. The event packet has the same structure as that of the command packet shown inFIG. 46.FIG. 68 shows a structure of thepacket parameter3110.Numeral5001 denotes an event ID indicating an event type, and5002 denotes parameter data prescribed for each event ID. A format of the data is retained beforehand in the prescribedinformation database504.Numeral5003 denotes parameter data whose format is determined for each event ID in the apparatus. The data format is retained as the event format table (FIG. 17) in theapparatus information database502 by executing the processing flow ofFIG. 66.
• (Event Processing)
• FIG. 69 shows a processing flow when each driver or utility of Client receives the event from the multi-function peripheral201. Each driver or utility registers a desired event beforehand in thegenerator515 using the event ID as a key. When the event is transmitted to Client from the multi-function peripheral201, thegenerator515 distributes the event to each registered driver or utility.FIG. 69 shows the processing after the event is distributed to each driver or utility. Instep5101, based on the format information obtained from the prescribedinformation database504 the prescribedparameter data5002 is analyzed. Instep5102, using the event ID (5001) as the key, theevent format1302 for the event ID is obtained from the event format table (FIG. 17) retained in theapparatus information database502. Instep5103, based on the obtained event format, the event format dependent on the apparatus (event format attribute ID676: sheet size, ID756: paper type, ID666: toner type, ID698: ink type, ID600: cover position) is analyzed. Subsequently, instep5104 the analyzed parameter and event ID (event ID200: no paper, ID399: no toner, ID432: no ink, ID234: multi-function peripheral cover opened) are processed and displayed for the event (e.g., no paper, cover open, no toner, and other user interfaces are displayed on the display6003).
• (Log Processing)
• FIG. 70 shows a flow in which thelog management utility510 obtains and processes the log retained by the multi-function peripheral201. Instep5201, log data is obtained. The log data is obtained by generating a job script for obtaining the log data, and sending the script to the multi-function peripheral201. In the multi-function peripheral201, the processing flow shown inFIGS. 47, 53,59 is executed, and the log data is sent to Client. For example, log data “12345, 4, 1.23, “OK”” ofLog Format ID1, 98/1/31:23 shown inFIG. 35 means that the user ID from which the job is issued to the print job manager ofservice ID1 is 12345, the number of outputted sheets is 4, the amount of used toner is 1.23, and the job completion state is OK. Instep5202, the log format table (FIG. 36) is obtained from theapparatus information database502. Instep5203,log format ID2401 on the top of each record of the log data is obtained, and from the value thelog format2502 is obtained from the log format table (FIG. 36). For example, format “1:701, 1:565, 1:765, 1:777” ofLog Format ID1 indicates the user ID from which the job is issued to the print job manager ofservice ID1, the number of outputted sheets, the amount of used toner, and the job completion state. Moreover, format “11:701, 11:565, 11:765, 11:777” ofLog Format ID2 indicates the user ID from which the job is issued to the print job manager ofservice ID11, the number of outputted sheets, the amount of used toner, and the job completion state. Instep5204, thelog data2403 is analyzed in accordance with thelog format2502, and the analyzed data is processed (log sorting, and the like) withlog occurrence time2402. Subsequently, instep5205 it is judged whether or not each record log data is analyzed. When the data is not analyzed, the processing from thestep5203 is repeatedly executed. When all the data is analyzed, the processing is ended.
• (Obtaining and Processing of Charge Information)
• FIG. 71 shows a flow in which thecharge management utility514 obtains and processes charge data retained in the multi-function peripheral201. The charge data is shown as count data retained by each manager. The count data is retained as values ofattribute ID401 in the attribute table (FIGS. 7, 18,22,24,26,29,32,27,40,44), and the values constitute a list of integer values. Integer value meanings are shown as values of the attribute (attribute ID402) of the count data format in the attribute table of each manager, and the values constitute a list of attribute ID. The count data list and the count data format list correspond to each other by sequence in each list. For example, the third value of the count data means the information of the third attribute ID of the count data format.FIG. 71 shows the flow for obtaining and processing the count data retained by each manager. Instep5301, a target manager service ID is designated, and the values of attribute ID401 (count data values) are obtained. For example, the value of attribute ID401 (45,78,34,13) shows the number of print sheets with a sheet size represented by the count data format of theattribute ID402. The value of theattribute ID401 is obtained by using the service ID and attribute ID as parameters, generating the command for obtaining the attribute value, and transmitting the command to thegenerator515. Instep5302, the same service ID is designated, and the value of the attribute ID402 (count data format value) is obtained. For example, attribute value565 of theattribute ID402 means the number of printed sheets with a sheet size A2, attribute value537 means the number of printed sheets with a sheet size A3, attribute value545 means the number of printed sheets with a sheet size A4, and attribute value523 means the number of printed sheets with a sheet size A5. The value may be obtained from theapparatus information database502. Instep5303, the obtained count data format is used to analyze the count data. Instep5304, the analyzed count data is used to process and generate charge data, for example, for each service ID, each user ID, and each division, thereby ending the flow.
• (Issuance of Print Job, Data Download Job)
• FIG. 72 shows processings for issuing a print job by theprinter driver505, a font data download job script by thefont management utility508, a form overlay data download job script by theform overlay utility509, a log data download job script by thelog management utility510, and a color profile data download job script by the colorprofile management utility511. The processing flow by each software (control program) as described above is common. Print target document data and the above-described types of download target data (font data, form data, color profile data, log data) are referred to as “data” inFIG. 72 and the following description. During the job issuance, the data to be printed or to be downloaded are designated with a plurality of attribute values set in the job script. Instep5401, theapparatus information database502 is accessed to obtain apparatus information. Instep5402, referring to the attribute table of each manager (e.g., the print manager to designate printing for the print target document data) as the data transmission target, it is checked whether the designated attribute value is within a range of the attribute values set in the attribute table. As a result of the check, when even one value is not in the range, in step5405 a processing to reject the job issuance is performed such as displaying of an error dialogue on the user interface, thereby ending the flow.
• As a result of the check ofstep5402, when all the attributes are within the range of the attribute values in the attribute table of the manager, instep5403 it is checked whether there is an inhibited attribute (attribute ID801 to805) in the manager attribute table. When the manager attribute table has the inhibited attribute, instep5404 it is checked whether the job attribute designated for each inhibited attribute of the manager attribute table is a combination of inhibited values. As a check result, when there is a combination of inhibited attribute values, instep5405 the processing to reject the job issuance is performed to end the flow. When as a result of the check ofstep5403 the manager has no inhibited attribute, and when as a result of the check ofstep5404 the job attribute is not a combination of inhibited values, in step5406 a data location is checked. The data location is designated by designating an address by the user or by generating the address by the application. When the data is inside Client issuing the job, in step5407, attribute value601 (supported data download method) of the relevant manager attribute table in theapparatus information database502 is checked.
• When in the check of step5407 the method of including data in the job is supported, in step5408 a job script including the data in the job is generated, the packet generating processing shown inFIG. 65 is performed, and the packet is transmitted to the multi-function peripheral201. When in the check of step5407, the method of including the data in the job is not supported, in step5409 a job script including the reference pointer (URL: Unified Resource Locator) of the data in the apparatus into the job is generated and transmitted. When in the check ofstep5406 the data is present outside Client issuing the job, instep5410 attribute value601 (supported data download method) of each relevant manager attribute table in the apparatus information data is checked. When in the check of step5410 a method of including the reference pointer in the job and reading data by the apparatus itself is supported, a job script including the reference pointer to the data into the job is generated and transmitted. When in the check ofstep5410 the method of including the reference pointer in the job and reading the data by the apparatus itself is not supported, instep5412 the data is once read into the apparatus from the outside. Subsequently, in step5413 a job script including the read data in the job is generated and transmitted. Each manager of the multi-function peripheral201, which has received the job script, performs the processing shown inFIGS. 53, 54,55 (print job manager) or inFIGS. 53, 54,58 (font manager, form overlay manager, log manager, color profile manager), and processes the instructed job.
• (Issuance of Scan job, Data Upload Job).
• FIG. 73 shows processings for issuing a scan job by thescanner driver506, a font data upload job script by thefont management utility508, a form overlay data upload job script by theform overlay utility509, a log data upload job script by thelog management utility510, and a color profile data upload job script by the colorprofile management utility511. The processing flow of each software (control program) described above is common. Document data obtained as a scanning result and the above-described types of upload target data (font data, form data, color profile data, log data) are referred to as “data” inFIG. 73 and the following description. During the job issuance, an indicator to indicate the data is designated with a plurality of attribute values set in the job script. Instep5501, theapparatus information database502 is accessed to obtain apparatus information. Instep5502, referring to the attribute table of each manager (e.g., for font data, the font manager to manage the font data) designating data as the upload target, it is checked whether the designated attribute value is within a range of the attribute values set in the attribute table. As a result of the check, when even one value is not in the range, in step5505 a processing to reject the job issuance is performed such as displaying of an error dialogue on the user interface, thereby ending the flow. As a result of the check ofstep5502, when all the attributes are within the range of the attribute values in the attribute table of the manager, instep5503 it is checked whether there is an inhibited attribute (attributeIDs801 to805) in the manager attributes. When the manager attribute table has the inhibited attribute, instep5504 it is checked whether the job attribute designated for each inhibited attribute of the manager attribute table is a combination of inhibited values. As a check result, when there is a combination of inhibited attribute values, instep5505 the processing to reject the job issuance is performed to end the flow.
• When as a result of the check ofstep5503 the manager has no inhibited attribute, and when as a result of the check ofstep5504 the job attribute is not a combination of inhibited values, instep5506 data transmission addressee (storage position) is checked. When the data transmission addressee is outside the apparatus, instep5507, the data transmission addressee is again checked. When the data transmission addressee is Client issuing the job, instep5508 attribute value602 (supported data upload method) of the relevant manager attribute table in the apparatus information data is checked. When as a result of the check ofstep5508 data transmission is supported, in step5509 a job script instructing data transmission is issued, and instep5510 data reception is performed. When as a result of the check ofstep5508, the data transmission is not supported (NO), instep5511 issued is a job script instructing reference transmission which means that data is transmitted to the apparatus using a reference pointer to retained data as a reply. Using information of the returned reference pointer, instep5512 data is obtained. When in thestep5507 the data transmission addressee is other than Client issuing the job, instep5513 attribute value602 (supported data upload method) of each relevant manager attribute table in the apparatus information data is checked. When as a result of the check ofstep5513 the reference transmission is supported, in step5514 a job script instructing the reference transmission by the use of the transmission addressee as the parameter is issued. Instep5515 by informing the data transmission addressee that data is transmitted from the multi-function peripheral201, an instruction for obtaining the data is transmitted. When as a result of the check ofstep5513 the reference transmission is not supported, in step5516 a job script instructing the data transmission is issued. Instep5517 data is received, and the data is again transmitted to the transmission addressee. When as a result of the check of thestep5506 the transmission addressee is inside the apparatus, instep5518 attribute value602 (supported data upload method) of each relevant manager attribute table in the apparatus information data is checked. When as a result of the check ofstep5518 the reference transmission is supported, in step5519 a job script instructing the reference transmission by the use of the addressee inside the apparatus as the parameter is issued. When as a result of the check ofstep5518 the reference transmission is not supported, in step5520 a job script instructing the data transmission is issued. After instep5521 Client receives the data, the data is again returned to the apparatus. Each manager of the multi-function peripheral201, which has received the job script, performs the processing shown inFIGS. 53, 54,56 (scan job manager) or inFIGS. 53, 54,59 (font manager, form overlay manager, log manager, color profile manager), and processes the instructed job.
• (Issuance of Copy Job)
• FIG. 74 shows a processing for issuing a copy job. As an instruction of the copy job issuance, a plurality of attribute values to be set in the job script are designated. Instep5601, theapparatus information database502 is accessed to obtain apparatus information. Instep5602, the attribute table of the copy manager is referred to, and it is checked whether the designated attribute values are within a range of attribute values set in the attribute table. As a result of the check, when even one value is not in the range, in step5605 a processing to reject the job issuance is performed such as displaying of an error dialogue on the user interface, thereby ending the flow. As a result of the check ofstep5602, when all the attributes are within the range of the attribute values in the attribute table of the copy manager, instep5603 it is checked whether there is an inhibited attribute (attributeIDs801 to805) in the copy manager attribute table. When the copy manager attribute table has the inhibited attribute, instep5604 it is checked whether the job attribute designated for each inhibited attribute in the attribute table of the copy manager is a combination of inhibited values. As a check result, when there is a combination of inhibited attribute values, instep5605 the processing to reject the job issuance is performed to end the flow. When as a result of the check ofstep5603 the manager has no inhibited attribute, and when as a. result of the check ofstep5604 the job attribute is not a combination of inhibited values, instep5606 the job script is generated and issued, thereby ending the flow. The copy job manager of the multi-function peripheral201 which has received the job script performs the processing shown inFIGS. 53, 54,57, and manages the instructed job.
• (Issuance of Job Management Command)
• FIG. 75 is a processing flow when thejob management utility512 issues a job management command. Instep5701 the service ID of the target manager is used as the parameter to obtain the job table (FIG. 20) retained by the manager fromMFP201. Instep5702, the job ID owned by the management target job is selected from the job list included in the obtained job table in an appropriate method. Selecting means includes a method which comprises displaying the job list on thedisplay6003 via theuser interface501 so that the user selects the job ID, and other methods. Instep5703 the designated job ID is used as the parameter to generate the command for managing the job, and the command is issued, thereby ending the flow. Supervisor of the multi-function peripheral201 which has received the job management command performs the processing shown in FIGS.47 to51 and60, and manages the instructed job.
• Additionally, the present invention may be applied to a system constituted of a copying machine, a printer, a scanner, and other single units, or may be applied to a device constituted of one apparatus (e.g., a copying machine, a facsimile device, and the like). Moreover, the object of the present invention is attained by providing the system with the storage medium (FIGS. 76, 77) in which the program code of software (control program) for realizing the above-described embodiment function is recorded as shown inFIG. 2, and reading and executing the program code stored in the storage medium by the device of the system (CPU301 or CPU6001). As a method of providing Client PC with the program or data shown inFIG. 77, a method of providingPC body7001 withfloppy disc FD7000 with the program stored therein as shown inFIG. 78 is also general. In this case, the program code itself read from the storage medium realizes the function of the above-described embodiment, and the storage medium in which the program code is stored constitutes the present invention.
• As the storage medium for supplying the program code, for example, in addition to the floppy disc or the hard disc, an optical disc, an optical magnetic disc, CD-ROM, CD-R, a magnetic tape, a nonvolatile memory card, ROM, and the like can be used. Moreover, by executing the program code read by the computer, the function of the above-mentioned embodiment is realized, but additionally, based on the instruction of the program code, OS (operating system) operating on the computer, and the like perform a part or the whole of the actual processing. Needless to say, by the processing the function of the above-mentioned embodiment is also realized. Furthermore, after the program code read from the storage medium is written in a memory mounted on a function expansion board inserted into the computer or a function expansion unit connected to the computer, based on the instruction of the program code, the CPU, and the like mounted on the function expansion board or the function expansion unit perform a part or the whole of the actual processing.
• Needless to say, by the processing the function of the above-mentioned embodiment is also realized.
• FIG. 79 is a sectional view showing an internal structure of a laser beam printer (hereinafter abbreviated as LBP) which can be applied to the laserbeam printer engines103 and104 ofFIG. 1, and the LBP can perform printing on a recording sheet by the input of character pattern data, and the like. InFIG. 79,LBP body8012 forms an image on the recording sheet as recording medium based on the supplied character pattern, and the like.Numeral8000 denotes an operation panel on which an operating switch, LED display, and the like are arranged, and8001 denotes a printer control unit which entirely controlsLBP8012 and analyzes the character pattern information, and the like. Theprinter control unit8001 mainly converts the character pattern information into a video signal and transmits an output to alaser driver8002. Thelaser driver8002 is a circuit for driving asemiconductor laser8003, and switches on or off alaser beam8004 emitted from thesemiconductor laser8003 in response to the entered video signal. Thelaser beam8004 is swung horizontally by a rotatingpolygonal mirror8005 to scan on anelectrostatic drum8006. Thereby, an electrostatic latent image of a character pattern is formed on theelectrostatic drum8006. After the latent image is developed by a developingunit8007 around theelectrostatic drum8006, the image is transferred to the recording sheet. In the recording sheets, cut sheets are used, and the cut recording sheets are stored in a plurality ofsheet cassettes8008 attached toLBP8012 for accommodating a plurality of types of sheets. The sheets are taken into the apparatus by asheet feed roller8009 and conveyingrollers8010 and8011, and supplied to theelectrostatic drum8006.
• FIG. 80 is a diagrammatic view of an ink jet recording apparatus IJRA which can be applied to the inkjet printer engine105 ofFIG. 1. In the drawing, a carriage HC is engaged in aspiral groove9003 of alead screw9004 rotating via drive force transmission gears9010,9008 with forward/reverse rotation of adrive motor9011, has a pin (not shown), and is reciprocated/moved in directions of arrows a, b. On the carriage HC, an ink jet cartridge IJC is mounted. Asheet press plate9001 presses the sheet against aplaten9000 over a moving direction of the carriage. Photo-couplers9006,9007 are home position detecting means which confirm the presence of acarriage lever9005 in this area and switch a rotating direction of themotor9011. Amember9013 supports acap member9019 for capping a front surface of a recording head, and suction means9012 for sucking the inside of the cap performs suction recovering of the recording head via anopening9020 inside the cap. Acleaning blade9014, and amember9016 which can move the blade back and forth are supported by abody support plate9015. The blade is not limited to this form, and needless to say, a known cleaning blade can be applied to the example. Moreover, alever9018 starts suction for the suction recovering, and moves as acam9017 engaged with the carriage moves. The movement is controlled by controlling a drive force from the drive motor by a known transmission means such as a clutch switchover, and the like. For the capping, cleaning, and suction recovering operations, when the carriage reaches an area on the side of the home position, a desired operation can be performed in the corresponding position by action of thelead screw9004. By performing the desired operation at a known timing, the operations can be applied in the example.
• As described above, according to the embodiment, by using the logical device control program (scanjob manager419,print job managers501 to509,copy job managers601 to608) retaining the function of the logical device to which the job is transmitted from the information processing apparatus and managing the job transmitted to the logical device, and the physical device control program (scanner controller420,LBP controllers510,511, Ink Jet controller512) retaining the function of the device engine of the peripheral and managing the job in the device engine, the job can be analyzed.
• Here, the physical device control program is a scanner control program (scanner controller420) which controls the scanner engine of the peripheral. The physical device control program is a laser beam printer control program (LBP controllers510,511) which controls the laser beam printer engine of the peripheral. The physical device control program is an ink jet printer control program (Ink Jet printer controller512) which controls the ink jet printer engine of the peripheral. Moreover, the logical device control program is a print job control program (print job managers501 to509) which controls the laser beam printer control program, or the ink jet printer control program, or the laser beam printer control program and the ink jet printer control program of the peripheral. Furthermore, the logical device control program is a scanner job control program (scan job manager419) which controls the scanner control program of the peripheral. Additionally, the logical device control program is a copy job control program (copy job managers601 to608) which controls the scanner control program and laser beam printer control program, or the ink jet printer control program, or the laser beam printer control program and ink jet printer control program of the peripheral.
• By the configuration, the logical device control program can retain a relation with at least one device engine which is used by the logical device to execute the job. Moreover, based on the job transmitted to the logical device, the device engine to be used for actually executing the job can be determined. Moreover, the function retained by the logical device control program can be changed. The job transmitted to the logical device can be associated with the job managed by the physical device which actually executes the job, and managed. Additionally, there are a plurality of logical device control programs, and by comparing load states of a plurality of logical device control programs, an optimum logical device control program can be selected. Moreover, there are provided a plurality of logical device control programs and a general program (Supervisor410) which administers the plurality of logical device control programs. In the general program, the subaddress and connection interface type used in transmitting the job to the logical device control program can be associated with the logical device control program and retained. Moreover, the general program retains a list of information indicating whether the subaddress is valid or invalid. When the job is transmitted to the invalid subaddress, the job can be canceled. Furthermore, the general program retains a list of usable user authentication information, and can notify a job error when the user information included in the entered job is not included in the list of the authentication information. Additionally, the general program can retain the list of security levels indicating types of authentication judgment processings of users who can use the program. Moreover, the logical device control program can retain a list of connection interfaces and transmission addressees for transmitting event data to the information processing apparatus when the event occurs during the job analysis. Furthermore, in the logical device control program, when the event occurs during the job analysis, by referring to the list of connection interfaces and transmission addressees for the transmission to the information processing apparatus, the event data can be transmitted. Moreover, as described above, according to the present embodiment, in accordance with the function (attribute value) obtained from the peripheral, the user interface of the control program for controlling the peripheral can automatically be formed (step4813). Furthermore, the display (FIGS. 81, 82) of the user interface for the peripheral can be controlled in accordance with the obtained function. Additionally, the information (attribute value) concerning the setting range of the function of the peripheral can be obtained. Moreover, the information concerning the setting range is represented by the combination of job-setting inhibited attributes (attributeIDs801 to805). Furthermore, the information (attribute value) concerning the function choices of the peripheral can be obtained. When the attribute list (attribute table) indicating the functions of the peripheral is obtained from the peripheral, and the attribute ID of the attribute list is designated, the attribute value can be obtained. Moreover, the attribute list (attribute table) indicating the functions of the physical device control program, logical device control program, resource control program and general control program for generalizing the programs of the peripheral can be obtained from the peripheral. Furthermore, the physical device control program is the scanner control program for controlling the scanner engine of the peripheral. Additionally, the physical device control program is the laser beam printer control program for controlling the laser beam printer engine of the peripheral.
• Moreover, the physical device control program is the ink jet printer control program for controlling the ink jet printer engine of the peripheral. Furthermore, the logical device control program is the print job control program for controlling the laser beam printer control program, the ink jet printer control program, or the laser beam printer control program and ink jet printer control program of the peripheral. Additionally, the logical device control program is the scanner job control program for controlling the scanner control program of the peripheral. Moreover, the logical device control program is the copy job control program for controlling the scanner control program and laser beam printer control program, or the ink jet printer control program, or the laser beam printer control program and ink jet printer control program of the peripheral. Furthermore, the resource control program is the font control program for managing the font of the peripheral. Additionally, the resource control program is the form overlay control program for managing the form overlay of the peripheral. Moreover, the resource control program is the log control program for managing the log of the peripheral. Furthermore, the resource control program is the color profile control program for managing the color profile.
• Moreover, as described above, according to the embodiment, by judging based on the function obtained from the peripheral (MFP201) whether the job script can be issued to the peripheral (steps5402 to5404,5502 to5504,5602 to5604), the job issuance processing can be controlled in accordance with the judgment result.
• Here, the attribute list (attribute table) indicating the functions of the physical device control program, logical device control program, resource control program (font manager413,form overlay manager414,log manager415, color profile manager416) and general program for generalizing the programs of the peripheral is obtained from the peripheral. Moreover, the combination of attributes in which the job setting is inhibited (attributeIDs801 to805) is obtained. Furthermore, the download job or the print job is issued to the peripheral. Additionally, the upload job or the scan job is issued to the peripheral. Moreover, the job issuance method is selected in accordance with the attribute (attribute ID601) indicating the supported download method of the obtained function and the location of job issuance target data. Furthermore, the job issuance method is selected in accordance with the attribute (attribute ID602) indicating the supported upload method of the obtained function and the stored position of job issuance target data. Additionally, the job issuance target data is print document data. Moreover, the job issuance target data is scan document data. Furthermore, the job issuance target data is font data. Additionally, the job issuance target data is form overlay data. Moreover, the job issuance target data is color profile data. Furthermore, the job issuance target data is log data. Additionally, the job issuance target data is font data. Moreover, the event format data for the event received from the peripheral is obtained, and the received event is analyzed based on the event format data. Furthermore, the log data of the peripheral and the log format data of the log data are obtained, and the log data is analyzed based on the log format data. Additionally, the charge data (count data) of the peripheral and the format data of the charge data are obtained, and the charge data is analyzed based on the charge format data.
Technical Advantages of the Invention
• As described above, according to the present invention, after inputting and analyzing the job script constituted of the packet data from the information processing apparatus, an appropriate job file can be generated in accordance with the content of the job script. Furthermore, the job scheduling unit (job execution priority, job execution cancellation, and the like), the unit of some bound documents (binder), and each document unit can be controlled variously and processed clearly as separate units. Moreover, in the job processing the processing result and other information of each binder unit and document unit can be obtained. Moreover, in the job processing, while the job is being executed, new setting or changing can be performed on each binder unit or document unit. Moreover, various controls of the job scheduling unit (job execution priority, job execution cancellation, and the like) and each document unit can clearly be processed as separate units. Furthermore, in the job processing the information such as the processing result of each document unit can be obtained. Additionally, in the job processing while the job is being executed, the new setting and changing can be performed on each document unit. Moreover, in the print job the media unit such as paper to be outputted in one job and the finishing unit such as stapling can be processed as separate units. Furthermore, in the scan job, the unit of control of the reading of original and the unit of scan image control can be processed as separate units.

Claims (2)

1. A peripheral connected to an information processing apparatus, comprising:

input means for inputting a job script constituted of packet data from said information processing apparatus; and

generating means for analyzing the job script obtained by said input means and subsequently generating an appropriate job file in accordance with the content of the job script.

2. to60. (Cancelled)

Images