JP2000163240A - Peripheral equipment device and its control method, and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To suppress the unnecessary issue of a job by providing an output means which reads out a status and outputs it at an external request and representing the status as at least one of a normal, an abnormal, and a conditioned normal state. SOLUTION: A controller 101 has a hardware constitution and a software constitution as storage medium and manages and controls devices according to a program. Three physical printers, LBP 103, LBP 104, and IJP 105 are managed and controlled as the devices and print jobs can be issued selectively to those physical printers. In this case, a means which represents the current statuses of the peripheral devices as three kinds of 'normal', 'conditioned normal', and 'abnormal' is provided and then a client is able to grasp the current status of the peripheral devices as three kinds of representations, i.e., 'normal', 'conditioned normal' and 'abnormal' before jobs are issued, thereby knowing whether or not the jobs can be executed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a peripheral device such as a printer, a scanner, a copier, and a facsimile.

[0002]

2. Description of the Related Art Conventional printers do not provide a means for a user to know whether a job is to be executed before issuing the job. For this reason, it has not been known whether or not the job will be executed unless the job is actually issued.

[0003]

There is a problem that it cannot be guaranteed at the time of job issuance that a job is to be executed without fail, and a problem that wasteful network traffic increases if the status cannot be identified. Was.

[0004] Further, even if the user does not have the access right, the execution of the job is not permitted.

[0005]

Means for Solving the Problems To solve the above problems, there are provided storage means for storing the status of the main body, and output means for reading and outputting the status in response to an external request. A peripheral device characterized by being represented as at least normal, abnormal, and conditionally normal.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS (Configuration of Multifunctional Peripheral Equipment) FIG.
Is a multifunction peripheral (MFP: M) showing an embodiment of the present invention.
FIG. 3 is a diagram illustrating a configuration of a multi-function peripheral (ulti-Function Peripheral).

The multifunctional peripheral device is connected to various network devices described below, and integrally manages and controls each device in accordance with a command supplied from the client through the network. Figure 1
In the figure, 101 is a controller for controlling the multi-function peripheral device. This controller has the hardware configuration shown in FIG.
It has a software (control and management program) configuration as shown in ISK315, and manages and controls the device based on such a program. Reference numeral 102 denotes a scanner engine, which is controlled by the controller 101. 103 and 104 are laser beam printer engines (LBP)
1, 2 and are controlled by the controller 101. The laser beam printer engine 103 is connected to the finisher 106, and is capable of performing a stapling process on a plurality of recording media (for example, paper) output from the printer engine. The finisher 106 is also controlled by the controller 101. 105 is an inkjet print engine (I
JP) can also perform color printing, and is controlled by the controller 101. Reference numeral 107 denotes a network (Ethernet) interface, which provides the controller 101 with two-way communication through the interface. Reference numeral 108 denotes an IEEE1394 interface, which provides the controller 101 with bidirectional communication through the interface. An IEEE 1284 interface 109 provides the controller 101 with bidirectional communication through the interface. Reference numeral 110 denotes a user interface, which includes an LCD display and a keyboard, displays information from the controller 101, and transmits an instruction from a user to the controller 101.

The multifunctional peripheral device having the above-described configuration includes three physical printers, LBP103 (B / B
W, Finisher), LBP104 (B / W), IJP105 (Color)
The print job is controlled so that print jobs can be selectively issued to these physical printers. In addition, the functions of each physical printer are reconfigured to create four logical printer (cluster) printers, LBP103 + LBP104, LBP104 + IJP105, LBP1
03 + IJP105, LBP103 + LBP104 + IJP105 can be controlled, and a print job can be selectively issued to these logical printers in the same manner as the physical printer. In addition, a logical printer that can print only black and white using IJP is configured to enable the issuance of a print job. The above seven printers, LBP103, LBP104, IJP105,
LBP103 + LBP104, LBP104 + IJP105, LBP103 + IJP105, LBP1
03 + LBP104 + IJP105 automatically selects this multifunction peripheral according to the print job based on the instruction from the client via the network, sets any print, and uses this to set the optimal printer To execute a print job.

[0009] In addition, when a scan job is issued from a client, a color original can be read using a scanner. Also, a scanner and the above eight printers, LBP103, LBP104, IJP105, LBP103 + LBP104, LBP104 +
IJP105, LBP103 + IJP105, LBP103 + LBP104 + IJP105 Select the IJP that can print only black and white (automatic selection is also possible) and enable the issue of copy jobs. Further, when the printer is only IJP, it is possible to issue a color copy job.

In addition, fonts and form overlays prepared in advance can be used in a print job. These can be uploaded / downloaded between devices or from an external client or the like, and resources can be managed. In addition, the color profile can be used in a print job, a scan job, and a copy job, and upload / download can be performed, and resource management can be performed. Further, a log can be automatically generated inside the device and uploaded.

[0011] Further, an interface corresponding to networks such as Ethernet and TCP / IP, IEEE1284, IEEE1394 and the like is provided, and all the above-mentioned functions can be used from an external client connected via these interfaces. In addition, for each interface, the correspondence between the sub-address, the physical / logical device (printer, scanner, copy) and each resource is established, and the client designates and selects this sub-address to specify the physical / logical device and each resource. To realize a desired function. A job can be issued and download / upload can be instructed to each sub-address of each of these interfaces at the same time. In addition, the correspondence between the sub-addresses and the physical / logical devices and each resource is determined by the multifunction peripheral device having an attribute table for managing the functions and the like of each connected device, and the similar attributes of each device. A table can be accessed, and by inquiring the multifunctional peripheral device from the outside, information relating to the function and the like of each device connected to the multifunctional peripheral device can be obtained, thereby enabling centralized management of a plurality of devices. Further, functions can be used from a user interface provided internally.

That is, by inquiring a supervisor, which will be described later, in the main body of the apparatus from the outside through the interface, an outline of the provided functions (such as what kind of job can be issued, what kind of resource can be used, etc.), job issuance, resource Sub-addresses used for download / upload, detailed information of each function (maximum number of copies, PDL supported finisher type, number of output BINs that can be specified, etc.) can be obtained. Using the above information, software (control program) on the Client side
Can be automatically configured. The sub-address used for this inquiry is set in advance between the multifunction peripheral device and each client. In addition, the administrator of the apparatus limits the above various functions according to the connection mode and the user.

(Overall System Configuration) FIG. 2 is a diagram showing a system configuration of the present embodiment. The multifunction peripheral described above analyzes instructions from each client connected via various networks, and responds accordingly. Various functions are realized using the above-described printer, scanner, and the like. In FIG. 2, reference numeral 201 denotes a multi-function peripheral (MFP) shown in FIG.
1 is the network interface cable 208 (10BASE-
T), ClientPC 202, 203, 2 by IEEE1394 interface cable 206, IEEE1284 interface cable 207
04 and 205 (information processing devices).
In each Client PC as shown in FIG. 109, various software (control programs) stored in a disk 6009 described later as a storage medium shown in FIG. 108 are operating. Ethern
ClientPC202 and 203 connected to et208 are IP addresses,
A port number is designated to connect to the multi-function peripheral 201 and output IP packet data. IEEE1394 interface 206
Is connected to the multi-function peripheral 201 by specifying a node ID and a LUN (logical unit number), and outputs SBP-2 packet data. The client PC 205 connected to the IEEE1284 interface 207 specifies the socket number and connects to the multi-function peripheral device 201 to connect to the IEEE1284.4.
Output packet data.

(Hardware Configuration of MFP) FIG.
FIG. 3 is a diagram showing a hardware configuration of a controller 101 of the present embodiment shown in FIG. Inside the controller 101, the CPU 30
1 is an LCD display 30 constituting a memory (RAM) 302 and a user interface (operation unit) 110 via a bus 313.
3 and a keyboard 304, ROM 314, DISK 315 are connected. The various programs for device management and the data such as the attribute table shown in FIG. 107 stored in the DISK 315 are for realizing the above-described functions, and are stored in the DISK 315 (storage medium) such as a hard disk or a floppy disk. And read them out sequentially to Memory (RAM) 302 as needed.
It is executed by the CPU 301. The disk 315 may be detachable from the MFP 201 or may be built in the MFP 201. Further, FIG.
The program shown in FIG. 3 is executed via a network interface cable 208 (10BASE-T), an IEEE1394 interface cable 206, and an IEEE1284 interface cable 207.
It may be configured to be downloaded from the ientPC 202, 203, 204, 205 or another MFP and stored in the disk 315.

The programs stored in the disks 315 and 6009 include not only the programs explicitly shown in FIG. 1 but also all the programs described in this specification.

The LCD display 303 and the keyboard 304 are shown in FIG.
The CPU 301 performs display by writing data to an LCD display 303, and the CPU 301 operates the keyboard 30.
By reading data from 4, an instruction from the user is input.

A network interface connector 305, an IEEE1394 interface connector 306, and an IEEE1284 interface connector 307 are connected to the bus 313. The network interface 107, the IEEE1394 interface 108, and the IEEE12
The Ethernet (1) shown in FIG.
0BASE-T) cable 208, IEEE1394 cable 206, IEEE1284
The cable 207 is connected. The CPU 301 performs communication using each interface by reading or writing data from these interfaces.

Further, a bus 313 includes a Laser Beam Printer.
Engine308, Finisher309, Scanner Engine310, Laser Be
am Printer Engine 311 and Ink Jet Printer Engine 312 are connected, and these are the Laser Beam Prin
ter Engine103, Finisher106, Scanner Engine102, Lase
r Beam Printer Engine104, Ink Jet Printer Engine10
The CPU 301 reads and writes data from and to these engines, thereby performing engine operations such as print / scan and acquiring various statuses. In addition, Laser Beam Printer Engine308, Finisher
309, Scanner Engine310, Laser Beam Printer Engine31
1. The Ink Jet Printer Engine 312 may exist as a single peripheral device on the network instead of inside the MFP 201, and may be controlled by the controller 101 of the MFP 201. These engine groups can include various sensor groups to check the state of the engine itself and the state of documents and sheets to be processed.

(Software Configuration of Controller 101)
FIG. 4 is a diagram illustrating a software (management / control program) configuration of the DISK 315 in the controller 101, and the software (control program) is executed by the CPU 301. In the figure, solid lines indicate data and control, and dotted lines indicate setting and capability acquisition. A user interface driver 401 controls the LCD display 303 and the keyboard 304. Reference numeral 405 denotes a user interface manager (control program), which interprets input information from the user input from the UI driver 401, generates a command packet shown in FIG. The user interface manager 405 also interprets the command packet input from the interpreter 409 and displays the command packet on the LCD display 303 via the UI driver (control program) 401.

Reference numeral 402 denotes a network interface driver (control program) which controls the network interface connector 305 and performs processing of a physical layer (physical packet) of a network packet, that is, extraction of a transport packet from a physical packet and transport packet , A physical packet is generated. 406
Denotes a TCP / IP / UDP / IP processing module that processes a transport packet output from the network interface 402, extracts a command packet, and outputs the command packet to the interpreter 409. Further, a transport packet is generated from the command packet output from the interpreter 409 and output to the network interface 402.

Reference numeral 403 denotes an IEEE1284 driver (control program), which controls the IEEE1284 interface 307. Reference numeral 407 denotes an IEEE1284.4 processing module (control program). IEEE1284.4 is a transport layer standard primarily intended for use with the IEEE1284 interface. An IEEE1284.4 processing module (control program) 407 processes the transport packet output from the IEEE1284 driver 403, extracts a command packet, and outputs the command packet to the interpreter 409. In addition, a transport packet is generated from the command packet output from the interpreter 409, and the IEEE1284 driver
Output to 403. Reference numeral 404 denotes an IEEE1394 driver (control program) that controls the IEEE1394 interface 306.

Reference numeral 408 denotes a module (control program) for processing SBP (Serial Bus Protocol) -2 which is a transport layer in IEEE1394. The processing module 408 of the SBP-2 processes the transport packet output from the IEEE1394 driver 404, extracts a command packet, and outputs the command packet to the interpreter 409. Further, a transport packet is generated from the command packet output from the interpreter 409 and output to the IEEE1394 driver 404. 409 is a transport processing unit for 406, 407, and 408 and a user interface manager
It is a packet interpreter that interprets a command packet input from 405 and generates a command. The packet interpreter 409 also generates a command packet in response to a request from another module (control program).
The interpreter 409 is a subaddress of the supervisor (supervising manager) 410 and a service ID correspondence table (see FIG.
According to 9), only command packets input from the valid sub-address are processed, and command packets input from other sub-addresses are discarded.

Reference numeral 410 denotes FIG. 7 (attribute table), FIG. 9 (sub address: service ID correspondence table), FIG. 11 (service ID: task type correspondence table), FIG. 13 (user authentication table), FIG. ) Various data shown in FIG. 16 (event setting table), FIG. 17 (event format table), FIG. 114 (account ID table), and FIG. And controller 101
Supervisor (overall management manager) who oversees the operation of. Supervisor 410 includes various data held by itself, each manager (font manager 413, form overlay manager 414, log manager 41
5. Various data held by the color profile manager 416, the print managers 501 to 509, the scan job manager 419, and the copy job managers 601 to 608) and each controller (the printer controller 510).
-512, refer to and change various data held by the scanner controller 420 according to the instruction of the input command.

Reference numeral 411 denotes a security gate which converts a command packet interpreted by the interpreter 409 into a Supervi.
User authentication table of sor410 (control program) (Fig. 1
According to 3) and the access control table (FIG. 14), only a user who has a right to use is restricted from inputting a command so that the multifunctional peripheral device 201 can be used. 41
Reference numeral 2 denotes a dispatcher (control program), which is a control program for processing commands input from the interpreter 409, such as resource managers (font manager 413, form overlay manager 414, log manager 415, color profile manager 416) and each job manager (print manager 501-509, scan job manager 419, and copy job manager 601-608). 41
A font manager 3 manages fonts. The font manager 413 is shown in FIG. 26 (attribute table) and FIG.
ONT table) holds the data as shown in DISK315.
Fonts managed by Font Manager 413 (DISK315
Alternatively, stored in the ROM 314) is a PDL rasterizer 4
17 and 418 for use in processing print jobs.

A form overlay manager 414 manages the form overlay. The form overlay manager 414 is shown in FIG. 29 (attribute table) and FIG. 31 (FOR
Data shown in Table M) is stored in DISK315. The form overlay (stored in the disk 315 or the ROM 314) managed by the form overlay manager 414 is passed to the PDL rasterizers 417 and 418, and is used in processing a print job. A log manager 415 manages logs. The log manager 415 stores data as shown in FIG. 32 (attribute table) and FIG. 34 (LOG table)
It is held in ISK315. The log is output from each manager and is under the control of the log manager. The log file of the execution is stored in the RAM 302 or the disk 315 and updated as needed.

A color profile manager 416 manages color profile data for a color scanner or a color printer to perform color matching. The color profile manager 416 stores data as shown in FIG. 37 (attribute table) and FIG. 39 (color profile table) in the disk 315. The color profile managed by the color profile manager 416 is passed to each of the printer controllers (control programs) 510, 511, and 512 and the scanner controller (control program) 420, and is used for processing print jobs, copy jobs, and scan jobs. Is done. A PDL rasterizer 417 processes document data written in PS (registered trademark), which is a kind of PDL (page description language), and outputs image data. 418 is a kind of PDL (Page Description Language)
A PDL rasterizer that processes document data written in PCL (registered trademark) and outputs image data. 419
Is a scan job manager that manages scan jobs. The scan job manager 419 holds data as shown in FIG. 22 (attribute table) in the disk 315. The scan job manager 419 instructs the scanner controller 420 to execute a scan. A scanner controller 420 controls the scanner engine 310. The scanner controller 420 holds in the disk 315 data such as those shown in FIG. 44 (attribute table) indicating the function / state and performance of the scanner engine 310. The scan job manager 419 and the scanner controller 420 each have data (FIGS. 22 and 44) indicating functions and performances, but the functions indicated by these data need not necessarily be the same. The function can be limited by rewriting the data (FIG. 22) held by the scan job manager 419 through the supervisor 410.

The above-mentioned font manager 413, form overlay manager 414, log manager 4
15, the color profile manager 416 is a resource management program, and the scan job manager 41
9. The print job managers 501 to 509 and the copy job managers 601 to 608 are logical device (scanner and printer) control programs, and the laser beam printer controllers 510 and 511, the inkjet printer controller 512 and the scanner controller 420 are physical devices (printers and printers). (Scanner) control program.

(Configuration of Print Job Manager) FIG.
FIG. 5 is a diagram supplementing the software (control program) configuration diagram shown in FIG. 4. Each print manager receives a command distribution from the dispatcher 412 as described later. The dispatcher 412 is the same as the dispatcher 412 shown in FIG. 4, and distributes a command packet from the print job manager (control program) 501 to 509. Print job managers 501 to 509 manage print jobs. Each print job manager has data as shown in FIG. 18 (attribute table) in the disk 315, and can always grasp its own functions and the like. Each print job manager has a printer controller (LBP Controller 510 or LBP Controller) used to process a print job.
oller511 or Ink Jet Controller512 or Controlle
Any combination of r510, 511, and 512) and the print engine connected to it are determined, and which printer controller (control program) is used is shown in FIG.
Described in the data indicated by the attribute ID 2001. However, only the print job manager 508 has a function of dynamically selecting a print engine to be used, and it is described in the data (attribute table) of the print job manager 508 that it has this function. I have. Each print manager DISKs the input print jobs and data such as those shown in FIG. 20 (job table) and FIG.
Holds at 315. Printer controllers 510 to 512 control the print engines 308, 311 and 312, respectively. The printer controller 510 also controls the finisher 309. Each printer controller represents the function, status, and performance of the corresponding printer engine.
The DISK 315 has data as shown in (attribute table).
Each controller DISKs data such as shown in FIG. 42 (job queue table) representing the state of the input print job.
Holds at 315.

Each of the print job managers 501 to 509 and the printer controllers 510 to 512 has data in the disk 315 indicating functions and performances as shown in FIG. 18 (attribute table) and FIG. 40 (attribute table). Generally, the print job manager has a performance equivalent to the sum of the performances of the controllers used, and has a function corresponding to a common item of the functions of the controllers. However, some of these functions can be changed by rewriting the data (FIG. 18) held by the print job manager through the supervisor 410. For example, print job manager 503 and print job manager 509
Because we are using the same printer controller 512,
Although the same performance and function can be provided, the print job manager 503 can perform color printing and the print job manager 509 can disable color printing by setting processing described later of data held by the print job manager. .

(Configuration of Copy Job Manager) FIG.
FIG. 6 is a diagram supplementing the software (control program) configuration diagram shown in FIGS. 4 and 5. A copy job manager, which will be described later, also receives a command distribution from the dispatcher 412. The dispatcher 412 is the same as the dispatcher 412 shown in FIG. 4, and distributes a command packet to the copy job managers (control programs) 601 to 608. Reference numerals 601 to 608 denote copy job managers for managing copy jobs. Each copy job manager has data as shown in FIG. 24 (attribute table) in the disk 315. Each copy job manager determines a printer controller, a scanner controller, a print engine connected thereto, and a scanner engine used for processing a copy job. FIG. 24 shows which printer controller and scanner controller to use. It is described in the indicated data (attribute ID 2001). However, only the print job manager 608 has a function of dynamically selecting a print engine to be used. The fact that this function is provided is described in the data (attribute ID 2002) of the copy job manager 608. I have. As shown in FIG. 20 (job table) and FIG. 21 (job request table), each copy manager indicates the input copy jobs and which jobs are executed by which printer controller and scanner controller. DI data
It is held in SK315. Reference numerals 510 to 512 denote printer controllers for controlling each print engine.
Are the same as those shown in FIG.

(Attribute Table of Supervisor) FIG.
r (control program) 410 represents data (attribute table) held and managed in the disk 315. This table shows the multifunction peripherals 201
Of the function, connection information, security information, and billing information (current billing data and billing restriction data) described later. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record has attribute ID 701 and type ID 702
And attribute values 703. Based on these data, the setting status of the connected device, the availability of various commands, and the like are determined. The attribute ID 701 indicates the type of information as shown in FIG. 8, and indicates what the value 703 corresponding to each attribute ID 701 means. The attribute ID 701 is common to each device, and those having the same attribute ID represent the same information type. The type ID 702 indicates what data type each value 703 has as shown in FIG.
It is used when interpreting 3. Type ID is attribute I
It is uniquely determined by D and is uniquely defined inside the device. In this embodiment, both the attribute ID 701 and the type ID 702 are included in the attribute table. May be implemented so that only the attribute ID and value are entered. The value 703 indicates an attribute value according to the attribute ID 701.

FIG. 8 shows the attribute ID 701 and the type ID 702 of the attribute table shown in FIG.
It is a figure which shows the detail of. Among them, "List of supported security levels" of attribute ID 102 is Supervis
Contains a list of security levels that can be set for the security level required when issuing an operation for or. Figure for security level
This is done in the description of the 14 access control tables. Attribute ID103
The “current security level” indicates the security level currently set in the supervisor. Attribute ID 50
The supported event list 1 represents events that can be set to be notified to the supervisor by a list of event IDs uniquely defined for each event type. The actual event transmission settings are shown in the figure.
This is performed by setting the connection type and destination of the event notification together with the event ID in the event setting table 16. Regarding the values in the attribute table of FIG. 7, “Table Data” indicates that the values are data having a table format (52 to 104) indicated by the type ID.

(Sub Address: Service ID (SID) Correspondence Table) FIG. 9 shows a sub address: service ID correspondence table. This table is the attribute ID 1001 of the attribute table shown in FIG.
(Sub address: SID correspondence table) is held in the DISK 315 as an attribute value. The subaddress: SID correspondence table indicates which service (for example, printing, font downloading, etc.) can be obtained by inputting a command packet to which subaddress. In addition, the interpreter 409 controls whether to provide a job service for each connection mode according to the validity flag and the like in this table. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a connection type ID 801, a sub address 802, a service ID 803, a valid flag 804, a valid user list 805, and an invalid user list 806. The connection type ID 801 indicates an identifier indicating the connection type. FIG. 10 is a diagram showing the meaning of the connection type ID, where 0 is Internal (user interface), 1 is TCP / IP (network), 2
Indicates IEEE1284.4 (IEEE1284), and 3 indicates SBP-2 (IEEE1394).

The sub address 802 indicates a sub address for each connection mode. Although the user interface does not have a subaddress, a subaddress is assigned for convenience, and a command packet is input from the user interface together with the subaddress information.

The service ID 803 is an identifier indicating the contents of the service. The service ID 803 is assigned to each manager shown in FIGS. 4, 5 and 6 on a one-to-one basis.

The valid flag 804 indicates whether the subaddress is valid. When this value is true (YHS), the subaddress is valid, and the user can issue a command packet to the subaddress. If the value is false (NO), the subaddress is invalid, meaning that even if a command packet is issued to the subaddress, the packet is discarded. In the case of FIG. 8, when the connection form of the connection form ID2 (IEEE1284) is used, the service I is used.
Indicates that the service of D8 (Print Job Manager) cannot be provided.

The valid user list 805 indicates a list of user IDs who can receive the service when the subaddress is valid. The invalid user list 806 indicates a list of user IDs who cannot receive the service even if the subaddress is valid. List of valid users
Only one of 805 and the list of invalid users 806 can be set.

(Service ID: Task Type Correspondence Table) FIG.
Represents a service ID: task type correspondence table,
The task type indicates who the requested task (service) is (such as which printer manager task). This table uses DIS as the attribute value of the attribute ID 1002 (SID: Task Type table) in the attribute table shown in FIG.
It is held in K315. The service ID: task type table indicates what kind of service the service ID provides. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a service ID 901 and a task type 902. Task type 9
02 indicates what kind of service it is.
FIG. 12 is a diagram illustrating the meaning of the value of the task type 902. 0 is
The service provided by Supervisor, 1 is print, 2 is scan, 3 is copy, 101 is font, 102 is form overlay, 103 is log, and 104 is color profile. The service ID has a one-to-one correspondence with the service providing manager. For this reason, the service ID is also used to access the function table of each manager. Since the function table also has each printer controller and scanner controller, a controller ID corresponding to the service ID is also assigned to the printer controller and the scanner controller to access them, and the controller ID is any type. The controller is managed by the service ID: task type correspondence table. The task type 201 represents a printer controller, and the task type 202 represents a scanner controller. The controller ID has one-to-one correspondence with each controller shown in FIGS.

The meaning of the service ID is as follows. 0: Supervisor 410 1: Print job manager 501 2: Print job manager 502 3: Print job manager 503 4: Print job manager 504 5: Print job manager 505 6: Print job manager 506 7: Print job manager 507 8: Print job manager 508 9: Print job manager 509 10: Scan job manager 419 11: Copy job manager 601 12: Copy job manager 602 13: Copy job manager 603 14: Copy job manager 604 15: Copy job manager 605 16: Copy job manager 606 17 : Copy job manager 607 18: Copy job manager 608 101: Font manager 413 102: Form overlay manager 414 103: Log manager 415 104: Color profile manager 416 21: Printer control Over La 510 22: printer controller 511 23: printer-controller 512 24: scanner controller 420

(User Authentication Table) FIG. 13 shows a user authentication table held by Supervisor, and shows authentication information of a user who can use the device. This table is held in the disk 315 as attribute values of the attribute ID 1003 (user authentication table) of the attribute table shown in FIG. The user authentication table indicates a set of a valid user ID and password together with information on whether the user has administrator privileges. In the table, each row represents one information unit (record),
Data is configured as a set of a plurality of records.
Each record includes a user ID 1001, a password 1002, and an administrator privilege flag 1003. The administrator privilege flag 1003 indicates whether the user has a right as an administrator.

(Access Control Table) FIG. 14 shows an access control table held by the supervisor, and shows a security level for each service. This table is used as the attribute value of the attribute ID 1004 (access control table) in the attribute table shown in FIG.
It is held in DISK315. The access control table holds a required security level for each service ID and a list of users who are permitted to provide the service. In the table, each row represents one information unit (record),
Data is configured as a set of a plurality of records.
Each record is service ID 1101, security level 1102
And a list 1103 of user IDs. The security level 1102 indicates authentication information required when receiving the service specified by the service ID 1101, that is, when issuing a command packet to the manager indicated by the service ID 1101. FIG. 15 is a diagram showing the meaning of the security level. Security level 0 means that user authentication is not required, 1 means that only administrators are distinguished, 2 means that only authenticated users can be used,
The fact that a user ID is used for authentication and no password is used, 3 indicates that only an authenticated user can be used, and that a user ID and password are used for authentication. The user ID list 1103 shows that the security levels 1102 are 2 and 3.
Represents a list of user IDs permitted to use (access).

(Event Setting Table) FIG. 16 shows an event setting table held by Supervisor. This table is
The attribute value of the attribute ID 502 (event setting table) of the attribute table indicated by 7 is held in the disk 315. The event setting table holds, for each type of event, a method and destination for transmitting an event notification when a specified event occurs in the device. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is event ID 1201, connection type 1202
And a notification destination address 1203. The destination includes a connection type and a notification destination address depending on the connection type. The event ID 1201 represents the type of the event, and is uniquely defined in the device.
For example, Event ID 200 has no paper, ID 399 has no toner, ID
432 indicates no ink, and ID234 indicates that the cover of the multifunction peripheral is open. The connection type ID 1202 indicates a connection type for transmitting an event notification, and the same value as that used in the subaddress: service ID correspondence table in FIG. 9 is used. Notification address 1203 is the connection type 1202
Represents the destination of the notification destination of the event conforming to.
In addition, other types of events include a case where a job that exceeds the charging limit is requested or is about to be exceeded, a case where an access is made from a client for which access right is not recognized, and the like. May be notified to the client or each device.

(Event Format Table) FIG.
It represents the event format table held by isor and indicates the contents of the event. This table is held in the disk 315 as attribute values of the attribute ID 503 (event format table) of the attribute table shown in FIG. The event format table shows each event ID uniquely defined in the device
Holds the format of additional data transmitted as an event notification. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record includes an event ID 1301 and an event format 1302. The event format 1302 is a format of additional data transmitted as an event notification, and is represented as a list of attribute IDs. The attribute ID is uniquely defined in the device,
Since the type is also uniquely determined by the attribute ID, the format of the additional data can be represented by specifying the attribute ID. For example, event format
1302 attribute ID676 is paper size, ID756 is paper type, ID666
Indicates the type of toner, ID698 indicates the type of ink, and ID600 indicates the position of the cover. As shown below,
The destination is set in the data (attribute table) held by each manager and controller, and it is possible to notify the events that have occurred in each manager and controller. The format is also held in the event format table shown in FIG. When the specified event occurs, the contents defined in the event format are
This is notified together with data determined in advance for each event ID.

(Account ID Table) The table in FIG. 114 is Superviso
Indicates information about each account ID held by r. This table shows the attribute ID 1005 (Account ID) in the attribute table shown in FIG.
Is stored in the DISK 315 as attribute values in Table 3). This table shows the relationship between an effective account ID, a user ID belonging to the account ID, and a user ID permitting charging. In the table, each row represents one information unit (record),
Data is configured as a set of a plurality of records.
Each record is account ID8301, user ID belonging to it
List 8302, and user I who permits charging
D list 8303. The value used for the user ID must not be used for the account ID. The relationship between the account ID and the user ID belonging to it is one-to-many,
The number of user IDs may be zero. There is a one-to-many relationship between account IDs and user IDs that permit charging, and the number of user IDs may be zero.

(Current count data table) FIG.
This represents a current count data table held by the visor, and represents a list of information to be counted in the supervisor. This table uses DIS as the attribute value of the attribute ID 401 (current count data table) of the attribute table shown in FIG.
It is held in K315. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a user ID or account ID 8401 and a counter 8402. The meaning of the counter is represented by the attribute ID 402 “count data format”. For example,
The count data 45, 78, 34, and 13 of the account ID 2003 indicate the number of prints of the paper size represented in the count data format.

(Count data format table) FIG.
Represents a count data format table held by Supervisor, and is represented as a list of attribute IDs.
This table is held in the disk 315 as attribute values of the attribute ID 402 (count data format table) of the attribute table shown in FIG. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is a user ID or account
It consists of ID8501 and attribute ID8502. Since the attribute ID is uniquely defined in the device, the meaning of the count data can be specified by specifying the attribute ID. For example, the attribute value 565 of the attribute ID 402 is the number of prints of the paper size A2, and the attribute value 537 is the paper size A3.
The attribute value 545 means the number of prints of the paper size A4, and the attribute value 523 means the number of prints of the paper size A5.

(Count Limit Data Table) FIG.
It represents the count limit data table held by sor, and represents the maximum value that “current count data” of the attribute ID 401 can have. This table is held in the disk 315 as attribute values of the attribute ID 403 (count limit data table) of the attribute table shown in FIG. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a user ID or account ID 8601 and a maximum value 8602. "Current count data" of attribute ID 401
If any one of the values exceeds the maximum value, the CPU 301 invalidates the valid flag in the subaddress: service ID correspondence table shown in FIG. 9 to invalidate all services (by the manager).

(Count Unit Price Data Table) FIG.
It represents count unit price data held by sor,
The unit price for each count of the attribute ID held in the “count data format” of the attribute ID 402 is expressed in currency units. This table is the attribute ID 4 of the attribute table shown in FIG.
The attribute value of 04 (count unit price data table) is held in DISK 315. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a user ID or account ID 8701 and a unit price 8702.

(Current Billing Data Table) FIG. 119 shows Superviso
r represents the current billing data held by
It indicates a value obtained by multiplying the “current count data” of D401 by the corresponding value of “count unit price data” of the attribute ID 404 to obtain a total sum. This table has D as the attribute value of the attribute ID 405 (current billing data table) of the attribute table shown in FIG.
It is held in ISK315. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a user ID or account ID 8801 and a current billing 8802.

(Charging Limit Data Table) FIG.
Represents the charging limit data held by the attribute ID 40
It indicates the maximum value that the “current billing data” of 5 can have. This table is the attribute ID 4 of the attribute table shown in FIG.
The attribute value of 06 (charging restriction data table) is stored in the DISK 315. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a user ID or account ID 8901 and a charging limit 8902. attribute
When the “current billing data” of the ID 405 exceeds the “billing limit data” of the attribute ID 406, the CPU 301 sets the valid flag of the subaddress: service ID correspondence table shown in FIG. ) Disable the service.

Attribute table of print job manager)
18 is each print job manager (control program) 50
1 to 509 represent data (attribute table) held in the DISK 315. This table shows print job performance and functions that can be handled by the print job manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The contents of each record are the same as those of the supervisor shown in FIG. 7, and the attribute ID 1401, type ID 1402 and value 1403
It is composed of FIG. 19 shows the attribute ID 1401 of the attribute table of FIG.
FIG. 14 is a diagram showing values of the ID and the type ID 1402. Type ID 20 of the attribute table in Fig. 19
3 (job table format), type ID 204 (job request table format), type
ID81 (forbidden attribute combination list 1 format), type ID82 (forbidden attribute combination list 2 format), type ID83 (forbidden attribute combination list 3 format), type ID84 (forbidden attribute combination list 4 format), type ID85 (forbidden attribute combination list) Other type IDs other than (5 format) are the same as those used in the attribute table of Supervisor in FIG.

The “supported data download method” of the attribute ID 601 indicates a method of transmitting document data to be printed to a device. In the present embodiment, 1: a method of including document data in a job; And 2: The job includes a reference pointer (URL: Unified Resource Locator) for the document data, and supports a method of reading the document data indicated by the reference pointer from the device as needed.

The attribute IDs 801, 802, 803, 804, and 805 are prohibition setting attributes indicating restrictions on attributes set in a print job input to the print job manager. These are used to represent restrictions, for example, when the number of copies exceeds 100, the finisher cannot be set. The prohibition setting attribute has five types as a method of expressing the restriction. The attribute ID 801 is
As shown by {Attribute ID1: {Attribute ID2}, a plurality of pairs of a list of one attribute ID1 and another attribute ID2 are held.
This means that if the attribute ID1 has been set, the setting of each attribute ID2 cannot be performed in the print job script.

The attribute ID 802 is: {Attribute ID 1: operator identifier:
Value: As shown by {attribute ID2}, a plurality of pairs of a list of another attribute ID2 are held for one attribute ID1, operator identifier, and value. This means that if the result of applying the operator indicated by the operator identifier to the value of the attribute ID1 is true, the setting of each attribute ID2 cannot be performed in the print job script. In the operator identifier, the integer value has one-to-one correspondence with the binary operation. For example, 0 represents “= (equal)”.

The attribute ID 803 is: {Attribute ID 1: operator identifier
1: Value 1: {attribute ID 2: operator identifier 2: value 2}, as shown in the table, for a certain attribute ID 1, operator identifier 1, and value 1,
It holds a plurality of pairs of lists of different sets of attribute ID2, operation identifier2 and value2. This means that if the result of applying the operator indicated by operator identifier 1 to attribute ID 1 to value 1 is true, the operator indicated by operator identifier 2 for each attribute ID 2 is applied to value 2. This means that the setting that makes the result of the application true is not possible in the print job script.

The attribute ID 804 is $ (attribute ID1: operator identifier)
1: Value 1): Operation identifier 3: (Attribute ID 2: Operator identifier 2: Value
2): As shown by {attribute ID3}, for one attribute ID1, operator identifier 1 and value 1, operation identifier 3 and another attribute ID2, operation identifier 2 and value 2, yet another attribute ID3 Holds multiple pairs of lists. This is the result of applying the operator indicated by operator identifier 1 to value 1 for attribute ID1 and the result of applying the operator indicated by operator identifier 2 to value 2 for attribute ID2. If the result of performing the operation indicated by the operator identifier 3 is true, it indicates that the setting for each attribute ID 3 cannot be performed in the print job script.

The attribute ID 805 is represented by $ (attribute ID1: operator identifier)
1: Value 1): Operation identifier 3: (Attribute ID 2: Operator identifier 2: Value
2): {Attribute ID 4: Operation identifier 4: Value 4}, as shown for one attribute ID 1, operator identifier 1 and value 1, operation identifier 3 and another attribute ID 2, operation identifier 2 and value 2 , And a plurality of pairs of lists of sets of another attribute ID4, operation identifier 4, and value 4 are held. This is the result of applying the operator indicated by operator identifier 1 to attribute ID 1 and applying it to value 1.
If the result of applying the operator indicated by the operator identifier 2 to the value 2 to the ID 2 and the operation indicated by the operator identifier 3 is true, the operation is performed for each attribute ID 4 This indicates that the setting that makes the result of applying the calculation indicated by to the value 4 to be new cannot be performed in the print job script.

The “controller ID list for executing (possible) Job” attribute ID 2001 is a list of controller IDs of the controllers that execute print jobs. Print job managers other than the print job manager 508 always execute jobs. A list of controllers to be executed. Since the print job manager 508 dynamically selects a controller according to the function requested by the job, this attribute indicates a range in which the controller can be selected. Attribute ID 2002
"Whether the controller is automatically selected" indicates whether the print job manager automatically selects the controller. In this embodiment, only the print job manager 508 sets this value to true. Other attribute IDs are the same as those used in the supervisor attribute table of FIG. However, the setting range and the range affected are limited to those under the control of the print job manager to which the attribute table belongs. For example, attribute value
The “supported operations” 101 is a list of operations that can be issued to this print job manager.
Is to limit charging for a print job executed by the print job manager. In the case where the charge limit is exceeded, only the service of the print job manager is invalidated, and the service of another manager is not affected. The attribute table of the print job manager shown in FIG. 18 is an attribute table with a service ID of 4 (print job manager 504), and corresponds to each of the service IDs 1, 2, 3, 5, 6, 7, 8, and 9. Print job manager 501, 502, 503, 505, 506, 507, 508, 509
Are stored in the disk 315 and are different from each other.

The “maximum number of printable copies” of the attribute ID 10001 is
This is the maximum number of copies that can be printed. attribute
The “current status” of the ID 106 indicates the current status of the print job manager. Attribute value = 0: Normal, Attribute value = 1: Normal with restriction, Attribute value = 2: Abnormal = Indicates service unavailable state. The attribute ID 107 “list of attributes to be referenced when job execution is possible with restrictions” is attribute ID 106
And the attribute value = 1: the attribute shown in the case of normal with restriction.
The attribute ID 108 “list in case of abnormality” is an attribute indicating “reason at the time of abnormality” when the attribute value = 2: abnormality = service unavailable state in the attribute ID 106. The print job manager always uses the attribute ID 106 and attribute ID 10 according to the current situation.
7. The value of each attribute indicated by the value of the attribute ID 108 and the value of the attribute ID 107 is dynamically changed.

By the way, in the case of the state of the attribute table of FIG. 18, the state of the print job manager indicates "normal with restriction (attribute value = 1)" and the restriction is attribute ID 10001 "maximum number of printable copies (attribute value = 10) ”.

(Job Table) FIG. 20 is a diagram showing data (job table) held by the print job manager, and shows a correspondence table between file names and job IDs holding the actual jobs managed by the print manager. The table is RAM3 as the attribute value of the attribute ID (job table) in the attribute table shown in FIG.
02 is held. Print job manager is RA
Dynamically change the job table on M302 and DISK315 as needed
To save. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a job ID 1501 and a file name 1502 in which the actual job is held. The job ID 1501 is an identifier for a job assigned by the print job manager when the job is submitted to the print job manager. The job file name 1502 is the name of a file in which the job entity is stored. As shown in FIG. 52, the entity of the job is an attribute ID,
It is configured by having a plurality of sets of attribute value size and attribute value.

(Job Request Table) FIG. 21 is a diagram showing a job request table held by the print job manager, and shows the relationship between jobs managed by the print manager and jobs executed by the controller. This table is
The attribute value of the attribute ID 2004 (job request table) of the attribute table indicated by 18 is held in the disk 315. The job request table indicates which controller manages a job managed by the print job manager as which job. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a job ID 1503, a controller ID 1504, and a job ID 1505 assigned in the controller. Job ID 1503
Is an identifier for the job assigned by the print job manager when the job is input to the print job manager.
Corresponds to 01. The controller ID 1504 indicates the ID of the controller executing the job. Job ID 1505
Is the job identifier assigned by the controller that executes the job.

(Attribute table of scan job manager)
FIG. 22 shows an attribute table which is data held by the scan job manager 419. This table shows the performance and functions of the scan job that can be handled by the scan job manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The content of each record is the same as that of the supervisor shown in FIG. 7, and the attribute ID 1601, type ID
1602 and 1603. FIG. 23 is a diagram showing the values of the attribute ID and the type ID in the attribute table of FIG. Attribute ID = 602
"Supported data upload methods"
In this embodiment, a method for transmitting the scanned document data to the device is described. In the present embodiment, the document data is included in the reply of the job, and the document data is stored in the device and the job is returned. Contains a reference pointer to the document data (URL: Unified R
eSource Locator), and a method of reading document data indicated by a reference pointer from the host (Client) as needed is supported. Attribute ID = 1201
"List of image formats that can be output" indicates the data format of images that can be output, and "List of settable resolutions" with attribute ID = 1203 indicates the settable resolutions. Those in this can be designated as data format and resolution. The “identifiable document type” of the attribute ID = 1204 is S
Indicates the type of document (monochrome or color, text or image, etc.) that can be determined using the sensor function of canner Engine 102.When issuing a scan job, these types are combined and a certain document type is At this time, it is possible to specify the data format and the resolution. One of the values is a special value indicating “prescan”, and is used to specify which data format or resolution to use when setting prescan. For the job table with attribute ID = 108, see FIG.
This is the same as that held by the print job manager indicated by 0.

The other attribute IDs are the same as those used in the attribute table of Supervisor in FIG. However, the range of setting and the range of influence are limited to those under the control of the scan job manager to which the attribute table belongs. The other type IDs other than the type ID 203 (job table format) in the attribute table in FIG. 23 are the same as those used in the attribute table of Supervisor in FIG. The “current status” of the attribute ID 106 indicates the current status of the scan job manager. Attribute value = 0: Normal, Attribute value = 1: Normal with restriction, Attribute value = 2: Abnormal = Indicates service unavailable state. attribute
The “list of attributes to be referred to when job execution is possible with restriction” of ID 107 is an attribute that is indicated when the attribute ID 106 is attribute value = 1: normal with restriction. Attribute ID 108 “List in case of abnormality” is attribute ID 106, attribute value = 2:
When the abnormality is in the service unavailable state, the attribute indicates “reason at the time of abnormality”. The scan job manager always dynamically changes the values of the attribute ID 106, the attribute ID 107, the value of the attribute ID 108, and the value of each attribute indicated by the value of the attribute ID 107 according to the current situation.

(Attribute Table of Copy Job Manager) FIG.
Reference numeral 24 denotes data (attribute table) held by each copy job manager 601 to 608. This table shows the performance and functions of the copy job that can be handled by the copy job manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The content of each record is the same as that of the supervisor shown in FIG. 7, and the attribute ID 1701, type ID 17
02 and the value 1703. FIG. 25 shows the values of attribute ID 1701 and type ID 1702 in the attribute table of FIG. Attribute ID1302 (color printing possible), attribute ID1303 (type of finishing supported), attribute ID1304 (settable maximum resolution), attribute ID1305 (settable minimum resolution), attribute ID2001
(Controller ID list that may execute Job), Attribute ID 2002 (Controller automatic selection or not),
The attribute ID 2003 (job table) is the same as that shown in the description of the print job manager and the scan job manager. Also, attribute ID 1302 (whether color printing is possible), attribute ID 1303 (type of finishing supported), attribute ID 1304 (highest resolution that can be set), attribute ID
1305 (minimum resolution that can be set), attribute ID 2001 (controller ID list that may execute Job), attribute ID 200
Attribute ID other than 2 (controller automatic selection), attribute ID 2003 (job table), type ID 203 (job table format) and type I
D is the same as that used in the attribute table of Supervisor in FIG. The attribute table of the copy job manager shown in FIG. 24 is an attribute table with a service ID of 18 (copy job manager 608), and has a service ID of 11, 12, 13, and
The attribute tables of the copy job managers 601, 602, 603, 604, 605, 606, and 607 corresponding to 14, 15, 16, and 17, respectively, are stored in the disk 315 and are different from each other. Attribute ID 100
The “maximum number of printable copies” of 01 is the maximum number of prints in which a copy job is possible. The “current status” of the attribute ID 106 indicates the current status of the copy job manager.
Attribute value = 0: Normal, Attribute value = 1: Limited normal, Attribute value =
2: Abnormal = indicates a service unavailable state. The attribute ID 107 “list of attributes to be referred to when the job can be executed with restriction” is attribute ID 106, attribute value = 1: normal with restriction,
Is the attribute shown in the case of. The attribute ID 108 “list in case of abnormality” is an attribute indicating “reason at the time of abnormality” when the attribute value = 2: abnormality = service unavailable state in the attribute ID 106. The copy job manager always determines the value of attribute ID 106, attribute ID 107, attribute ID 108 and attribute I according to the current situation.
The value of each attribute indicated by the value of D107 is dynamically changed.

(Attribute Table of Font Manager) FIG. 26 shows data (attribute table) held by the font manager 413 in the disk 315. This table shows types of fonts that can be handled by the font manager, a list of fonts currently managed by the font manager, and the like. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The contents of each record are Superviso shown in Fig. 7.
Same as r, attribute ID 1801, type ID 1802 and value 1
803. FIG. 27 shows the attribute ID 1 in the attribute table of FIG. 26.
801 and the value of type ID 1802 are shown. Attribute ID 601 (supported data download method), attribute ID 602 (supported data upload method), attribute ID 1501 (list of supported font types), attribute ID 1502
The attribute IDs and type IDs other than (maximum number of fonts that can be held), attribute ID 1503 (number of currently held fonts), attribute ID 1504 (list of held fonts), and type ID 150 (font table) are the supervisors in Fig. 7. Is the same as that used in the attribute table. However, the range of setting and the range of influence are limited to those under the control of the font manager to which the attribute table belongs. "Supported data download method" of attribute ID 601, and attribute ID 60
The “supported data upload method” of 2 is the same as that described in the description of the print job manager and the description of the scan job manager, respectively. It shows.
The “current status” of the attribute ID 106 indicates the current status of the font manager. Attribute value = 0: Normal, Attribute value =
1: normal with restriction, attribute value = 2: abnormal = indicates service unavailable state. The attribute ID 107 “list of attributes to be referred to when job execution is possible with restrictions” is an attribute indicated when the attribute ID 106 is attribute value = 1: normal with restrictions. Attribute ID 108 “List in case of abnormality” is attribute ID 106
Attribute value = 2: Abnormal = If the service cannot be performed, the attribute indicates “reason at the time of abnormality”. The font manager always uses the attribute ID 106, attribute ID 107, attribute ID 10 according to the current situation.
The value of each attribute indicated by the value of 8 and the attribute ID 107 is dynamically changed.

(Font Table) FIG. 28 shows a font table held by the font manager. This table is
The attribute value of the type ID 1504 (font table) of the attribute table indicated by 26 is held in the disk 315. The font table shows what fonts are currently managed by the font manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record has font ID 190
1, a font type 1902, a font name 1903, and a file name 1904 including font data. Font data is stored in DISK315, and font ID 1
Reference numeral 901 denotes an identifier for the font assigned by the font manager when the font data is downloaded to the RAM 302.

(Attribute Table of Form Overlay Manager) FIG.
Indicates the data (attribute table) held in K315. This table is
This indicates a format of a form overlay that can be handled by the form overlay manager, a list of form overlays currently managed by the form overlay manager, and the like. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The content of each record is the same as that of Supervisor shown in FIG.
It is composed of an attribute ID 2001, a type ID 2002, and a value 2003. FIG. 30 shows the values of the attribute ID and the type ID in the attribute table of FIG. Attribute ID 601 (Supported data download method), Attribute ID 602 (Supported data upload method), Attribute ID 1601 (List of supported form overlay formats), Attribute ID 1602 (Maximum number of form overlays that can be held) ), Attribute ID 1603 (current number of form overlays), attribute ID 1604
(A list of retained form overlays), type ID
For attribute IDs and type IDs other than 160 (form table), see Fig. 7.
It is the same as that used in the Supervisor attribute table. However, the range of setting and the range of influence are limited to those under the control of the form overlay manager to which the attribute table belongs. "Supported data download method" of attribute ID 601 and attribute ID
602 "Supported Data Upload Methods"
Are the same as those described in the description of the print job manager and the description of the scan job manager, respectively, and indicate a supported method of downloading and uploading form overlay data. "Current status" of attribute ID 106 is
Indicates the current state of the form overlay manager.
Attribute value = 0: Normal, Attribute value = 1: Limited normal, Attribute value =
2: Abnormal = indicates a service unavailable state. The attribute ID 106 “list of attributes to be referred to when job execution is possible with restriction” is attribute ID 106, attribute value = 1: restricted normal,
Is the attribute shown in the case of. The attribute ID 108 “list in case of abnormality” is an attribute indicating “reason at the time of abnormality” when the attribute value = 2: abnormality = service unavailable state in the attribute ID 106. The form overlay manager always dynamically changes the value of the attribute ID 106, the attribute ID 107, the value of the attribute ID 108, and the value of each attribute indicated by the value of the attribute ID 107 according to the current situation.

(Form Overlay Table) FIG. 31 shows a form overlay table held by the form overlay manager 414. This table is held in the disk 315 as attribute values of the attribute ID 1604 (form overlay table) of the attribute table shown in FIG. The form overlay table indicates what form overlay is currently being managed by the form overlay manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is a form overlay ID 21
01, form overlay data format 2102,
It is composed of a form overlay name 2103 and a file name 2104 including form overlay data. The form overlay data is stored in the disk 315, and the form overlay ID 2101 is an identifier for the font assigned by the form overlay manager when the form overlay data was downloaded to the RAM 302.

(Attribute Table of Log Manager) FIG. 32 shows data (attribute table) held by the log manager 415 in the disk 315. This table shows a list of logs currently managed by the log manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The content of each record is the same as that of Supervisor shown in FIG.
It is composed of an attribute ID 2201, a type ID 2202 and a value 2203. FIG. 33 shows the values of the attribute ID and the type ID in the attribute table of FIG. Attribute ID 602 (supported data upload method), attribute ID 1703 (number of retained Logs), attribute ID 170
4 (log table), attribute ID 1705 (log format table), type
ID170 (log table), type ID171 (log format table format)
Other attribute IDs and type IDs are the same as those used in the attribute table of Supervisor in FIG. However, the range of setting and the range of influence are limited to those under the management of the log manager to which the attribute table belongs.

(Log Table) FIG. 34 shows a log table held by the log manager 415. This table is DISK as the attribute value of the attribute ID 1704 (log table) in the attribute table shown in FIG.
315 is held. The log table indicates what logs are currently managed by the log manager.
In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a log ID 2301 and a file name 2302 including log data. The log ID 2301 is a log identifier defined in advance for the type.

(Contents of Log Data) FIG. 35 shows the contents of log data managed by DISK 315 by the log manager. Log data is configured as a set of log records. Each log record includes a log format ID 2401, a recording date and time 2402, and log data 2403.
The log format ID 2401 refers to the log format information recorded in the log format table shown in FIG. 36, and represents the format of the log data 2403. For example, log data of LogFormatID1 "12345, 4,
1.23, "OK" means that the user ID that issued the job to the print job manager with service ID 1 is 12345, the number of output papers is 4, the used toner amount is 1.23, and the job end status is OK Is shown.

(Log Format Table) FIG. 36 shows a log format table held by the log manager 415. This table is held in the disk 315 as attribute values of the attribute ID (log format table) of the attribute table shown in FIG. The log format table indicates the format of a log recorded in each log data managed by the log manager 415. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is a log format ID
2501 and a log format 2502. The log format is represented as a list of service ID: attribute ID pairs. The attribute ID is uniquely defined in the device, and its type is also uniquely determined by the attribute ID. Therefore, by specifying the attribute ID, the format of the log data can be represented. Log format 25
02 service ID: attribute ID pair list and log data 2403
The list of values in the list corresponds to the order. For example, the third service I in the log format 2502 list
D: Attribute ID pair means the format of the third value of log data. For example, the format of LogFormatID1 "1: 7
“01, 1: 565, 1: 765, 1: 777” indicate the user ID of the user who issued the job to the print job manager of service ID 1, the number of output papers, the used toner amount, and the end state of the job. Also, the format of LogFormatID2 "11: 701, 11:
“565, 11: 765, 11: 777” indicate the user ID that has issued the job to the print job manager of service ID 11, the number of output sheets, the amount of toner used, and the end state of the job.

(Attribute Table of Color Profile Manager) FIG.
Represents the data (attribute table) held in. This table shows a format of a color profile that can be handled by the color profile manager, a list of color profiles currently managed by the color profile manager, and the like. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Figure 7 shows the contents of each record.
Is the same as that of Supervisor indicated by the attribute ID 260
1, consisting of a type ID 2602 and a value 2603. FIG. 38 shows the values of the attribute ID and the type ID in the attribute table of FIG. Attribute ID 601
(Supported data download methods), attributes
ID602 (Supported data upload method), Attribute ID1801 (List of supported color profile data formats), Attribute ID1802 (Maximum number of color profiles that can be stored), Attribute ID1803 (Current number of color profiles stored) ), Attribute ID 1804 (color profile table) and type ID 180 (color profile table format) are the same as those used in the attribute table of Supervisor in FIG. However, the setting range and the range affected are limited to those under the control of the color profile manager to which the attribute table belongs. The attribute ID 601 “supported data download method” and the attribute ID 602 “supported data upload method” are the same as those described in the description of the print job manager and the scan job manager, respectively. It is the same and indicates the supported font data download and upload methods. The “current status” of the attribute ID 106 indicates the current status of the color profile manager. Attribute value = 0: Normal, Attribute = value 1:
Restricted normal, attribute value = 2: abnormal = indicates service unavailable state. The attribute ID 107 “list of attributes to be referred to when job execution is possible with restrictions” is an attribute indicated when the attribute ID 106 is attribute value = 1: normal with restrictions. Attribute ID
108 “List in case of abnormality” is an attribute indicating “reason at the time of abnormality” when attribute value = 2: abnormality = service unavailable state in attribute ID 106. The color profile manager always dynamically changes the values of the attribute ID 106, the attribute ID 107, the value of the attribute ID 108, and the value of each attribute indicated by the value of the attribute ID 107 according to the current situation.

(Color Profile Table) FIG. 39 shows a color profile held by the color profile manager. This table is DISK as the attribute value of the attribute ID 1804 (color profile table) in the attribute table shown in FIG.
315 is held. The color profile table indicates what color profile is currently managed by the color profile manager. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record is composed of a color profile ID 2701, a color profile format 2702, and a file name 2703 including color profile data. The color profile ID 2701 is an identifier for the color profile assigned by the color profile manager when the color profile data is downloaded. The color profile data is correction data for correcting data sent from the Scanner Engine 102 and data sent to the Ink Jet Printer Engine 105 to perform color matching.

(Attribute Table of Printer Controller) FIG. 40 shows data (attribute table) held by the printer controllers 510, 511, and 512 in the disk 315. This table shows the performance / function of the print engine and finisher controlled by the printer controller, and the values relating to the performance / function cannot be rewritten. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The content of each record is the same as that of the supervisor shown in FIG. 7, and is composed of an attribute ID 2801, a type ID 2802, and a value 2803.
FIG. 41 shows the values of the attribute ID and the type ID in the attribute table of FIG. Attribute ID
12 (controller type), attribute ID 13 (controller I
D), attribute ID 5001 (whether color printing is possible), attribute ID 5
002 (supported finishing types), attribute I
D5003 (highest configurable resolution), attribute ID5004 (lowest configurable resolution), attribute ID5005 (job queue table), type ID50
Attribute IDs and type IDs other than 0 (job queue table format) are the same as those used in the attribute table of Supervisor in FIG. However, the range of setting and the range of influence are limited to those under the control of the printer controller to which the attribute table belongs. The attribute table of the printer controller shown in FIG. 40 is an attribute table with a service ID of 21 (printer controller 510). Each is different.

(Job Queue Table) FIG. 42 shows a job queue table held by the printer controller.
This table is held in the disk 315 as attribute values of the attribute ID 5005 (job queue table) of the attribute table shown in FIG. The job queue table indicates the status of the job managed and executed by the printer controller. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. Each record has job ID 2901 and job status 29
02 and the name of the file that stores the actual job 2903
It is composed of The job ID 2901 is an identifier for the job assigned by the printer controller when the job is input to the printer controller. Figure 43 is a diagram
42 is a diagram illustrating 42 job status 2902 (job status). FIG. 1 indicates that the job is being completed, 2 indicates that the job is being executed by the engine, and 3 indicates that the job is waiting for execution. The job file name 2903 is the name of a file in which the job entity is stored. The actual job is as shown in Fig. 52.
It is configured by having a plurality of sets of attribute ID, attribute value size and attribute value.

(Attribute Table of Scan Controller) FIG. 44
Represents data (attribute table) held by the scanner controller 420 in the disk 315. This table indicates the scanner engine performance / function controlled by the scanner controller, and the value relating to the performance / function cannot be rewritten. In the table, each row represents one information unit (record), and data is configured as a set of a plurality of records. The content of each record is the same as that of the supervisor shown in FIG. 7, and the attribute ID 3001, type ID 3002 and value 3003
It is composed of Fig. 45 shows the attribute ID and type of the attribute table shown in Fig. 44.
Indicates the ID value. Attribute ID12 (controller type), attribute
ID13 (controller ID), attribute ID6001 (whether color scan is possible), attribute ID6002 (maximum document size), attribute
Attribute IDs other than ID6003 (highest configurable resolution) and attribute ID6004 (lowest configurable resolution)
It is the same as that used in the attribute table of sor. However, the range of setting and the range of influence are limited to those under the control of the printer controller to which the attribute table belongs.

(Structure of Command Packet) FIG. 46 shows a user interface manager 405, TCP / IP / UDP / IP
From the processing module 406, the IEEE1284.4 processing module 407 and the SBP-2 processing module 408 to the interprinter 409
Represents the structure of a command packet output to the server. This command packet is interpreted by the interpreter.
409 to User Interface Manager 405, TCP / I
It also shows the structure of a reply packet and an event packet output to the P / UDP / IP processing module 406, the IEEE1284.4 processing module 407, and the SBP-2 processing module 408. The packet includes a packet header 3101 indicating the beginning of the packet, a packet version 3102 indicating the packet structure version, a flag 3103 indicating the character of the packet, an operation code 3104 indicating what kind of operation is to be performed, and a Client (PC) returning packet. Block number 3105 used to recognize the parameter, parameter length 3106 representing the length of parameter 3110, user used for user authentication
It comprises an ID 3107, a password 3108, a status code 3109 used only for a reply packet and indicating a general state of reply, and a parameter 3110 having a format determined for each operation code 3105. The parameter 3110 includes an access target service ID, an access target attribute ID, and the like. The flag 3104 indicates whether the packet is a command packet / event packet or a reply packet 3111, and the data to be transmitted cannot be included in the parameter 3110, and subsequent data is also included in the next packet to be transmitted. Continuation flag 31 indicating that it is in
There are 12. The length of parameter 3110 is the parameter length 31
06 is limited to the number represented (64k bytes). Specifically, ClientPC202,2 connected to Ethernet208
03 is a multifunction peripheral by specifying an IP address and port number
Connect to 201 and send IP packet data to Network Interface 305
Output to (107). The client PC 204 connected to the IEEE1394 interface 206 specifies the node ID and LUN (logical unit number) and connects to the multi-function peripheral 201 to connect to the SBP.
-2 output the packet data to the IEEE1394 Interface 306 (108). C connected to IEEE1284 interface 207
lientPC205 is a multifunctional peripheral device 20 by specifying a socket number.
Connect to IEEE1284 packet data by connecting to IEEE1284 Inter
Output to face307 (109). Network Interface Driver40
2, IEEE 1284 Interface Driver403, IEEE1394 Interfa
The transport packet with the IP Header, 1284 Header, and 1394 Header added to the beginning of the command packet shown in FIG. Output to module 408. The TCP / IP / UDP / IP processing module 406, the IEEE1284.4 processing module 407, and the SBP-2 processing module 408 process each of the input transport packets, extract the command packets shown in FIG.
Output to r / Generater409.

(Processing of Command Packet) FIG. 47 shows a processing flow of a command packet in the multifunctional peripheral device 201. In step 3201, each of the transport processing modules 405, 406, 407, and 408 processes data input from each of the interfaces 401, 402, 403, and 404, and extracts a command packet shown in FIG. The extracted command packet is transmitted along with the connection type information (connection type ID) and the subaddress to which the data was input, along with the TCP / IP
UDP / IP processing module 406, IEEE1284.4 processing module 4
07, input from the SBP-2 processing module 408 to the interpreter 409. In step 3202, the interpreter 40
9 is the subaddress held by Supervisor410: Service ID
By referring to the correspondence table (FIG. 9), by comparing the input connection type ID with the subaddress, a service ID is obtained and it is checked whether data input is valid. If the data entry is not valid as a result of the check,
In 3204, the command packet is discarded, and the process ends. If the data input is valid, the command packet is analyzed in step 3203 based on the packet structure in FIG. As a result of packet analysis, each item shown in FIG.
Each is output as independent and separate information. In step 3205, the access control table (FIG.
The security level corresponding to the service ID is acquired by referring to 14), and the billing data is acquired.

At step 3206, it is checked whether the security level acquired at step 3205 is 0 or 1. If the security level is 0 or 1, check the security level (security gate 411)
Is input to the dispatcher 412 without performing. Step 320
When security level is other than 0 or 1 in 6,
In step 3207, it is checked whether the security level is 2. If the security level is 2, it is checked in step 3209 whether the user ID (UID) included in the command packet exists in the user authentication table (FIG. 13). If the user ID is not included,
Assuming that the user does not have the authority, error reply information is generated in step 3210, a packet (error information is embedded in the status code 3109) is generated by the interprinter 409, and transmitted to the command packet transmission source. If the user ID is included, the user ID is input to the dispatcher 412. The source address is extracted from the transport packet (Header). In step 3207, if the security level is other than 2, it is checked whether the user ID: password pair included in the command packet in step 3208 exists in the user authentication table (FIG. 13). If the user ID: password pair is not included,
At 3211, error reply information is generated as the one without the authority, and a packet is generated by the interprinter 409 and transmitted to the command packet transmission source. If the user ID is included, the user ID is input to the dispatcher 412. In step 3212, it is determined whether the charge target is a user ID based on the billing data acquired in step 3205. If it is not the user ID, the account ID (AID) shall be charged, and the account
Check whether the ID is specified. If specified,
In step 3214, the user ID is entered in the account ID table (FIG. 114).
Check if D belongs to the specified account ID or if charging is allowed. If neither is the case, it is determined that the user does not have the right, error reply information is generated in step 3215, a packet is generated by the interprinter 409, and the packet is transmitted to the command packet transmission source. If it belongs to the account ID or the charge is allowed, the account ID
To enter. If no account ID is specified in step 3213, the account ID is
The table (FIG. 114) is searched for the account ID to which the user ID belongs. If the account ID is not found, it is determined that the user does not have the authority, and error reply information is generated in step 3217, a packet is generated by the interprinter 409, and transmitted to the command packet transmission source. If the account ID to which the user belongs is found, the account ID is input to the dispatcher 412. In step 3218, the dispatcher 412 determines the manager of the distribution destination based on the service ID, and connects to the determined manager with the connection type ID and the subaddress in which the data is input, the source address, the operation code, the block number, and the flag. Information, user IDs, passwords, parameter lengths, parameters, and charging target IDs are distributed. And step 32
At 19, each manager processes this information.

(Access Process of Attribute Table) FIG. 48 shows a process in the case where the Client instructs to read / write the attribute table of each manager / controller held by the multifunctional peripheral device 201. Reading and writing from the attribute table held by each manager / controller is performed by Su
This is performed by transmitting an appropriate command packet to the subaddress of the pervisor. The attribute table read command packet includes an access target service ID and an access target attribute ID as parameters.
The attribute table writing command packet includes, as parameters, an access target service ID and an access target attribute.
The attribute value corresponding to the ID and the attribute ID is included. Clie
The packet data sent from the nt to the multi-function peripheral 201 is processed by the flow shown in FIG. 47 and distributed to the supervisor. In step 3301, it is checked whether the operation code 3104 is an attribute value reading code (“Get”). Operation code is "Ge
In the case of “t”, the entire attribute table to be accessed is acquired based on the service ID in step 3301. Service ID
Is 0, the attribute table of the Supervisor 410 shown in FIG. 7 is shown, and if the service ID is 1, 2, 3, 4, 5, 6, 7, 8, 9, the attribute table of the print job manager as shown in FIG. If the service ID is 10, scan job manager 419 as shown in FIG.
If the service ID is 11, 12, 13, 14, 15, 16, 17, 18, the attribute table of the copy job manager as shown in FIG. 24, and if the service ID is 101, as shown in FIG. If the service ID is 102, the form overlay manager 41 as shown in FIG.
The attribute table of FIG. 4, the attribute table of the log manager 415 as shown in FIG. 32 when the service ID is 103, and the color profile manager 41 as shown in FIG.
In the case of the attribute table of FIG. 6 and the service IDs of 21, 22, and 23, the attribute table of the printer controller as shown in FIG.
In this case, the attribute table of the scanner controller 420 as shown in FIG. 44 is obtained. The attribute table of the print job manager shown in FIG. 18 is an attribute table with a service ID of 4 (print job manager 504), and includes service IDs 1, 2, 3,
The attribute table of the print job manager 501, 502, 503, 505, 506, 507, 508, 509 corresponding to each of 5, 6, 7, 8, and 9 is DIS
It is stored in K315. Similarly, the attribute table of the copy job manager shown in FIG. 24 is an attribute table with a service ID of 18 (copy job manager 608), and has a service ID of 1
The attribute tables of the copy job managers 601, 602, 603, 604, 605, 606, and 607 corresponding to 1, 12, 13, 14, 15, 16, and 17, respectively, are stored in the disk 315. Similarly,
The attribute table of the printer controller shown in FIG.
Is an attribute table of 21 (printer controller 510), and attribute tables of printer controllers 511 and 512 corresponding to the service IDs 22 and 23 are stored in the disk 315.

Thereafter, in step 3303, it is checked whether or not the specified attribute value can be obtained. The inspection is to obtain the value of "Attribute ID list that can be obtained only by administrator" (attribute ID = 105) of the target attribute table, and check if the attribute ID specified to be obtained is included in this Performed by If the attribute ID is included, the value cannot be acquired, so an error reply packet is created in step 3305, transmitted, and the processing is terminated. If the attribute ID is not included, the attribute ID specified in step 3304
Search the attribute table based on, and obtain the type ID and attribute value having the corresponding attribute ID. In step 3306, a reply packet is generated based on the type ID, and in step 3307, the reply packet is transmitted, and the process ends. If the operation code is not “Get” in step 3301, it is checked in step 3308 whether the operation code is an attribute value writing code (“Set”). If the operation code is “Set”, in step 3309 the entire attribute table to be accessed is acquired based on the service ID. Thereafter, in step 3310, it is checked whether the designated attribute value can be set.
Inspection is to obtain the value of "Attribute ID list that can be set only by administrator" (attribute ID = 104) of the target attribute table, and check whether the attribute ID specified for setting is included in this Performed by If the attribute ID is included, the value cannot be obtained, so an error reply packet is created in step 3314, transmitted, and the processing is terminated. attribute
If the ID is not included, the attribute table is searched based on the attribute ID specified in step 3311, and the type ID and the attribute value having the corresponding attribute ID are obtained. In step 3312, type
The specified attribute value is set based on the ID, and a reply packet indicating that the setting was successful is generated. Step 3313
Sends this reply packet and ends. If the operation code is not "Set" in step 3308, another processing step 3315, which will be described later, according to the operation code is performed, and the processing ends.

(Service ID List Inquiry Processing) FIG.
Represents a process when the Client inquires about a list of services (list of service IDs) provided by the multi-function peripheral 201. The inquiry about the service list is performed by transmitting an appropriate command packet to the subaddress of the supervisor and reading and processing the subaddress: service ID correspondence table shown in FIG. The flow shown in FIG. 49 is equivalent to step 3315 (other Ops) of the flow shown in FIG.
eration code processing) in detail. In step 3401, it is checked whether the operation code is a service list acquisition code ("List Service"). Operation code is "List S
If it is not “ervice”, another processing step 3402 described later according to the operation code is performed, and the processing is ended.
In the case of "ervice", in step 3403, a list is created by extracting only those corresponding to the connection format ID used in the inquiry from the subaddress: service ID correspondence table. In step 3404, the list created in step 3403 Is checked if the valid flag 804 is valid and the valid user list 805 has a value. If the user ID used for the query does not correspond to that value, the record is queried if the invalid user list 806 has a value. In the step 3405, a record containing the list of service IDs updated in the step 3404 is created,
The created reply packet is transmitted in step 3406.

(Sub Address Inquiry Processing) FIG.
The Client provides the sub-address information required when using the service provided by the multi-function peripheral device 201.
Represents the process when an inquiry is made by specifying an ID. As for the inquiry of the sub address, an appropriate command packet is transmitted to the sub address of the supervisor 410, and FIG.
This is performed by reading and processing the subaddress: service ID correspondence table indicated by. The subaddress inquiry command packet includes a service ID as a parameter. The flow shown in FIG. 50 is a detailed version of Step 3402 (processing of other Operation Code) in the flow shown in FIG. 49. In step 3501, it is checked whether or not the operation code is a sub-address acquisition code (“Reserve”). If the operation code is not “Reserve”, another processing step 35 described later according to the operation code is performed.
Perform 03 and finish. If the operation code is "Reserve" in step 3501, the sub-address / service ID correspondence table is scanned from the connection type ID used for the inquiry in step 3502 and the service ID specified in the parameter to search for a corresponding record. I do. Step 3504
For the record retrieved in, whether the valid flag is valid, if there is a value in the valid user list, whether the user ID used in the query is in the list, or if there is a value in the invalid user list, the list Check if there is no user ID used for the inquiry. If any of the check results are not OK, it is determined that there is no access right (use right) to the specified service, an error reply packet is created in step 3506, this packet is transmitted in step 3507, and the process is terminated. As a result of the check in step 3504, if all the checks are OK, a reply packet including a sub address is created in step 3505, and this packet is transmitted in step 3507, and the process is terminated.

(Inquiry Processing of Task ID Designated Service ID) FIG. 51 shows an optimum service for designating the type of service and processing the designated service among the services provided by the multi-function peripheral 201. This shows the processing flow when the service ID is inquired. Inquiry of the service ID specifying the type of service sends an appropriate command packet to the subaddress of Supervisor,
Subaddress shown in FIG. 9: service ID correspondence table and FIG. 11
This is performed by reading and processing the service ID: task type correspondence table indicated by. The sub-address ID inquiry command packet includes, as parameters, a task type for designating a service type and a combination (condition information) for limiting the service.
The condition information is represented as a list of pairs of an attribute ID and a value. The flow shown in FIG. 51 is a detailed version of Step 3503 (processing of other Operation Code) of the flow shown in FIG. In step 3601, the operation code is changed to the sub address acquisition code (“Get Se
rvice ”). If the operation code is not“ Get Service ”, another processing step 3603 described later according to the operation code
And exit. If the operation code is “Get Service” in step 3601, the connection format used for the inquiry is obtained from the connection format ID and subaddress: service ID correspondence table used for the inquiry in step 3602.
Create a list of service IDs with IDs. Step 3604
In, refer to the service ID: task type correspondence table,
Create a list of those having the specified task type from the above list. In step 3605, each record in the list created in step 3604 is inspected, and if the valid flag 804 is valid and the valid user list 805 has a value, the record in which the user ID used for the inquiry does not correspond to the value is invalidated. If the user list 806 has a value, the record in which the user ID used for the inquiry corresponds to the value is deleted from the list. In step 3609, the condition information included in the parameter is compared with the attribute table of each manager corresponding to the service ID in the list, and values other than the value matching the condition are deleted from the list. In step 3606, the number of records in the list changed in step 3605 is checked, and if the number of records is 0, an error reply packet is created in step 3611 assuming that the requested service does not exist, and a reply is made in step 3613. Send the packet and exit. If the number of records is not 0 in step 3606, it is checked in step 3607 whether the number of records is 1. If the number of records is 1, a reply packet including the service ID obtained in step 3612 is created, the reply packet is transmitted in step 3613, and the process ends. If the number of records is other than 1 in step 3607, in step 3608, each manager corresponding to the service ID in the list is inquired about the current load state. Each manager returns the number of jobs being processed as a load state, and selects a manager having the lowest load from among these. In step 3610, a reply packet including the service ID corresponding to the selected manager is created, and in step 3613, the reply packet is transmitted, and the process ends.

FIG. 52 shows an authentication processing flow of the service ID (SID), the user ID (UID), and the password (PWD) in the multifunctional peripheral device 201. Figure
The flow indicated by 52 is a step 36 of the flow shown in FIG.
It is a detailed version of step 03 (processing of other Operation Code). In step 36a01, it is checked whether the operation code is a user information acquisition code (“CheckID”). If the operation code is not “CheckID”, another processing step 36a12 described later according to the operation code is performed, and the processing ends.

At step 36a02, a service ID, a user ID, and a user password included as parameters of the command are obtained.

In step 36a03, it is checked whether there is a service ID specified by the user by referring to the service ID / task type correspondence table (FIG. 11) based on the service ID. Step 36a10 if the service ID does not exist
Then, error transmission information is created, and in step 36a11, an error reply packet is transmitted to the transmission source, and the process ends.

If the service ID exists in step 36a03, the access control table (FIG.
Obtain the security level corresponding to the service ID by referring to 4). If the security level is 0 in step 36a04, a job submission permission reply packet is created in step 36a09 without checking the user ID and user password, and the reply packet is transmitted to the transmission source in step 36a11.

If the security level is not 0 in step 36a04, it is checked in step 36a05 whether the security level is 1. If the security level is 1, a job submission permission reply packet is created in step 36a09 without checking the user ID and user password, and the reply packet is transmitted to the transmission source in step 36a11.

If the security level is not 1 in step 36a05, it is checked in step 36a06 whether the security level is 2. If the security level is 2, the user ID included in the packet acquired in step 36a02 in step 36a08 is the user authentication table (FIG. 13).
And check if it exists. User ID
If not included, step as unauthorized
Error reply information is generated in 36a10, and step 36a11
To send the reply packet to the sender. If the user ID is included in step 36a08, a job submission permission reply packet is created in step 36a09, and the reply packet is transmitted to the transmission source in step 36a11.

If the security level is not 2 in step 36a06, the process proceeds to step 36a07.
It is checked whether the user ID: password pair in the packet acquired in 36a02 exists in the user authentication table (FIG. 13). If the user ID: password pair is not included, error reply information is generated in 36a10 as having no authority, and a reply packet is transmitted to the transmission source in step 36a11. If a user ID: password pair is included in step 36a07, a job submission permission reply packet is created in step 36a09, and the reply packet is transmitted to the transmission source in step 36a11.

(Job Structure) FIG. 53 shows the internal structure of a file (job file) that holds the job entity managed by each manager. The file name of the job file is held as the file name 1502 in the job table (FIG. 20). The structure of this file also indicates the internal structure of the file that holds the job entity managed by each controller. This file name is stored in the job queue table (Figure
42) file name 2903. The job entity is represented by having a plurality of consecutive sets of attribute ID 3701, attribute value size 3702, and attribute value 3703. When the job includes a document, as shown by 3704, 3705, and 3706, a value representing the document file is stored as the attribute ID, the size of the document file name is stored as the attribute value, and the file name of the document file is stored as the attribute value. Also, if the job contains a binder, 371
As shown by 0, 3711, and 3712, a value representing the binder file is held as the attribute ID, the size of the binder file name is held as the attribute value, and the file name of the binder file is held as the attribute value. The job attributes include information such as the job name, job execution priority, the type of event and the destination to which event notifications are sent when the event occurs, information on the current status of the job, and the type of job. Dependent information: number of copies for print job,
This includes designation of a sheet for separation from another job, designation of a recovery method when the medium is used up, and the like.

(Document Structure) FIG. 54 shows the internal structure of a document file held by each job file. The file name of the document file is held as the file name 1502 in the document table (FIG. 62). The structure of this file also indicates the internal structure of the file that holds the entity of the document managed by each controller. The entity of the document is attribute ID37a0
1, represented by having a plurality of sets of attribute value sizes 37a02 and attribute values 37a03 in succession. If the document contains data, hold the value representing the data as the attribute ID, the size of the file name as the attribute value, and the file name of the file holding the data as the attribute value, as indicated by 37a07, 37a08, 37a09. ing. Document attributes include information such as the data transmission method, data format (such as the PDL used), data compression format, and information that depends on the type of document. , Media such as paper, double-sided printing, print quality,
This includes specifying the position and amount of the margin.

(Structure of Binder) FIG. 55 shows the internal structure of a binder file held by each job file. The file name of the binder file is held as the file name 1502 of the binder table (FIG. 63). The structure of this file also indicates the internal structure of the file that holds the substance of the binder managed by each controller. The substance of the binder is represented by having a plurality of consecutive sets of the attribute ID 37b01, the attribute value size 37b02, and the attribute value 37b03. 37b04, 37b05, 37b06 or 37b10, 37b11, 37b if the binder contains documents
As shown by 12, a value representing data is stored as an attribute ID, a file name size is stored as an attribute value, and a file name of a file holding document data is stored as an attribute value. The binder attributes include, for example, in the case of a print binder, designation of a bin to be output, designation of finishing such as staples and punch holes, designation of sorting, and the like.

(Job Script Processing in Each Manager) FIGS. 56, 57, 58, 59 and 60 show the processing flow of the job script in each manager. The job script is composed of a series of command packets shown in FIG.
It is defined as starting with an operation code and ending with a "Job End" operation code. Each packet constituting the job script is input to the subaddress indicated by the subaddress: service ID correspondence table shown in FIG. 9, and is distributed to each manager by the command packet processing flow shown in FIG. The processing flow shown in FIGS. 56 to 60 is for processing the command packet distributed to each manager to create the job file, binder file, document file and data file shown in FIGS. 53, 54 and 55. It is a processing flow of.

The operation distributed to each manager checks whether the operation code is a supported operation code in step 3801 in FIG. The check is performed by comparing each manager with the value of the “supported operation” attribute (attribute ID 101) held in the attribute table. If the result of the check indicates that the operation is not supported, an error reply packet is created in step 3811, transmitted, and the processing is terminated. If the operation code in step 3801 is a supported one, it is checked in step 3802 whether the job is currently being submitted. The check is performed by checking whether the job submission flag (the flag set in step 3806) is true. As a result of the inspection, if the job submission flag is false and the job is not being submitted,
In step 3804, the operation code is "Job Sta
rt ". The result of the check is
If the operation code is not "Job Start", an error reply packet is created in step 3816, transmitted, and the processing ends. OK as a result of the check in step 3804
If so, in step 3805, a job ID is assigned, an item is added to the job table (FIG. 20), and a new job file is created. Then, in step 3806, the job input flag is set to true, and the processing of the command packet ends. If it is determined in step 3802 that the job input flag is true, it is checked in step 3803 whether binder processing is currently being performed. Check is
This is performed by checking whether the binder processing flag (the flag set in step 38d03) is true. As a result of the inspection, the binder processing flag is true,
If the binder process is being performed, the process proceeds to the binder process in FIG. If the result of the check indicates that the binder processing flag is false and the binder processing is not being performed, it is checked in step 3807 whether the document processing is currently being performed. The check is made by checking whether the document processing flag (the flag set in step 38d06) is true. As a result of the inspection, if the document processing flag is true and the document is being processed,
Proceed to 58 document processing. If the result of the check indicates that the document processing flag is false and the document is not being processed, it is checked in step 3808 whether the operation code is "Set Job". The operation code "Set Job" is for instructing the manager that the parameters (attribute ID and attribute value) constituting the job are included in the parameters. If the operation code of the job is "Set Job", an area is added to the job file in step 3809, and writing is completed in the area to which the attribute ID, attribute value size, and attribute value have been added in step 3810. If it is determined in step 3808 that the operation code is not “Set Job”, the process proceeds to the process in FIG.

In step 38a01 in FIG. 57, it is checked whether the operation code is "Set Binder". Operation code "Set Binder" is an attribute (attribute ID and attribute value) that constitutes the binder in the parameter
Is instructed to the manager. If the operation code is "Set Binder", an area is added to the binder file in step 38a02, and in step 38a03, writing to the area to which the attribute ID, attribute value size, and attribute value have been added is completed. In step 38a01, as a result of the check, if the operation code is not "Set Binder", step 38a04
Check if the operation code is "Binder End" in. If the operation code is "Binder End" as a result of the check, step 38a05
Performs a binder file generation process and terminates the process. As a result of the check, the operation code is "Binder
If it is not "End", other operation processing is performed in 38a06 and the processing ends.

At step 38b01 in FIG. 58, it is checked whether the operation code is "Set Document". Operation code "Set Document"
It instructs the manager that the parameters (attribute ID and attribute value) constituting the document are included in the parameters. If the operation code is "Set Document", an area is added to the document file in step 38b02, and in step 38b03, the attribute ID, the attribute value size, and the attribute value are written in the added area, and the process ends. If it is determined in step 38b01 that the operation code is not “Set Document”, the operation code is set to “Document En” in step 38b04.
Check if the operation code is "Document End". If the operation code is "Document End", the document file generation processing is performed in step 38b05 and the processing is terminated. As a result of the check, the operation code is "Document End" If not, the process proceeds to the process in FIG.

In step 38c01 in FIG. 59, it is checked whether the operation code is "Binder Start". As a result of the check, if the operation code is "Binder Start", a binder ID is allocated in step 38c02, an item is added to the binder table (FIG. 63), and a new binder file is created. Then, in step 38c03, the binder processing flag is set to true, and the processing of the command packet ends. In step 38c01, the operation code is "Binder S
If it is not "tart", it is checked in step 38c04 whether the operation code is "Documnet Start". As a result of the check, the operation code is "Documnet Start"
ument Start ", a document ID is assigned in step 38c05, an item is added to the document table (FIG. 62), and a new document file is created. In step 38c06, the document processing flag is set to true and the command is executed. In step 38c04, the operation code is "Docume".
If it is not "nt Start", it is checked whether or not the operation code is "Job End" in step 38c07. If the operation code is "Job End", job generation end processing is performed in step 38c08 and the processing ends. The job generation end processing includes processing such as closing a job file, and differs depending on the type of manager (print job, scan job, copy job, font, form overlay, log, color profile). As a result, if the operation code is not “Job End”, other operation processing is performed in 38a09 and the processing ends.

At step 38c01 in FIG. 60, it is checked whether the operation code is "Send". The operation code "Send" instructs the manager that the parameters include data constituting the document. If the operation code is "Send" in step 38d01, step 38d02
In step 38d03, the continuation flag input together with the command is checked. If the continuation flag is true, an area is newly added to the existing data file 37a13 in step 38d03, and the parameter is written to the area in 38d04, and the processing is ended. If the continuation flag is false in step 38d02, in step 38d05, the data file 37a13
Is newly created, and the parameters are written to the data file in step 38c06. Then, in step 38d07, an area is added to the document file,
Attribute ID 37a07 representing data in d08, file name size 37a08, and file name 37a of newly created file
09 is written in this area, and the processing ends. If the operation code is not "Send" in step 38d01, the operation code is "Send Reque" in step 38d10.
Check if it is "st." If the operation code is "Send Request", it instructs the manager to send data, and the data transmission method is included as a parameter. The operation code is "Send Requ
If it is "est", processing dependent on each manager is performed in step 38d11, and the processing is terminated. In the case of the scan job manager, the original is scanned according to the attribute values held in the job file. Instruct the scanner controller to transmit the obtained data by the specified method. In the case of the font manager, immediately transmit the font data specified as the attribute value in the job file by the specified transmission method. If the operation code is not "Send Request" in step 38d10, step 38
At d12, the processing of the other operation codes is performed, and the processing ends.

If the operation code is not “Set Job” in step 3817 in FIG.
At 0, check if the operation code is "Send Request". Operation code is "S
"end Request" instructs the manager to transmit data, and includes a data transmission method as a parameter. When the operation code is "Send Request", processing dependent on each manager is performed in step 3821. And the processing is terminated.
In the case of the scan job manager, it instructs the scanner controller to scan the document according to the attribute values held in the job file and sends the obtained data in the specified method. In this case, the font data specified as the attribute value is immediately transmitted by the specified transmission method. In step 3820, the operation code is "S
If it is not "end Request", processing of other operation codes is performed in step 3822, and the processing ends.

(Job Processing in Print Job Manager) FIG. 64 shows the print job manager shown in FIG.
It shows the processing flow of a job in 501 to 509. The print job manager operates a task that constantly monitors the job table. When the print job manager performs the processing flow of the job script shown in FIG. 54 and detects that a new item has been added to the job table by inputting the “Job Start” operation code, this monitoring task is executed as shown in FIG. The task having the processing flow indicated by is operated to process the input job. First, in step 3901, a job event handler for processing an event related to a job is started. The job event handler is another task that operates in connection with the job, and the details of the operation are described later with reference to FIG. Next, in step 3902, reception of data to be printed and PDL rasterizer processing are performed.
The details of this processing are described in FIG. In step 3902, image data is obtained. In the next step 3903, a job processing request is made to the printer controller using the image data. The details of this processing are described in FIG. Step 39
In 04, account processing of resources used by the job is performed. The details of this processing are described in FIG. Finally, in step 3905, the job event handler started first is terminated, and files and the like used for job processing are deleted, and then the job processing in the print job manager is terminated.

(Job Event Handler Processing) FIG.
It shows the processing flow of the job event handler. The job event handler is another task that is started at the same time that each job manager starts a job process, and monitors various events that occur in the device. And job status transition, error occurrence,
When an event related to the job that started itself, such as completion of job processing, occurs, notification processing of the event is performed. In addition, each job manager, at the end of the job,
The end of the job event handler is instructed, and the instruction is also detected as an event to the job event handler. In step 39a01, an event in the device is monitored, and when an event related to a job occurs, the process proceeds to the next step. In step 39a02, the job file is inspected, and it is determined whether or not the event that has occurred is registered as a notification target. If the event is registered as a notification target, the job file is read in step 39a03, and its transmission method and transmission destination are obtained. Then, in step 39a04, an event packet to be transmitted is created, and the packet is transmitted to the obtained transmission destination. If the event that has occurred is not registered, the flow shifts to step 39a05. In step 39a05, it is checked whether the end of the job event handler has been instructed. If there is a termination instruction, the job event handler terminates the processing; otherwise, the step 39a0
Return to 1.

(Data reception / PDL rasterizer processing)
FIG. 66 shows the flow of data reception and PDL rasterizer processing in the print job manager. The PDL (Page Description La) used to represent the data (document data) in step 39b01
nguage) Wait for the attribute indicating the type to be added to the job file, and use the PDL R when the PDL type is determined
asterizer (PDL Rasterizer417 or PDL Rasterizer41
Wait until 8) becomes available. PDL Ra in step 39b01
When the sterizer becomes usable, it waits in step 39b02 for an attribute indicating the data receiving method to be added to the job file. When the attribute indicating the data receiving method is added to the job file, the data receiving method is checked in step 39b03. If the data reception method is external to the multifunction peripheral MFP 201 (for example,
If the method is to access a client PC or the like, a task for reading the specified data is generated in step 39b04 to access the outside. Then step 39
It waits for reading of data to start at b05. If data is included in the job in step 39b03 (in the case of data reception by the “Send” operation code in FIG. 61), the process waits for the start of data reception in step 39b06. Step 39b05 or 39b06
In step 39b07, when reading or receiving of data is started, the data is PDL Rasterized in step 39b07.
Start loading at r. Then, in step 39b08, the PD
Receive image data from L Rasterizer.

(Printer Controller Processing) FIG. 67 shows a processing flow of a job requested to the printer controller. In step 39c01, a printer controller to be used is determined. This determination is based on the attribute ID 2001 of the attribute table of the print job managers 501 to 507 and 509.
(Controller ID list for executing Job) and attribute I of print job manager 508
The printer controller required for printing can be dynamically set by reading the contents of the print job file (attribute I and attribute value of the job file shown in FIG. 53) by specifying "Yes" in D2002 (whether or not the controller can be automatically selected). May be decided. In this case, for example, if color printing is designated by the attribute ID and attribute value in the job file, Ink Je
t Determine the Contorller512 (CID23), and if the use of Finisher is specified in the attribute ID and attribute value, LBP Controller
Determine 510 (CID21). When the printer controller is determined, in step 39c02, image data is input to each printer controller and a job ID is received from the printer controller. In step 39c03, the job ID and the printer controller ID are stored in the job request table (FIG. 21).
The job ID received from the printer controller is recorded as a separate record for each printer controller. Then the print job manager returns to step 39c0
In step 4, each printer controller waits for the job end, and when the job end is notified from the printer controller, the corresponding record is deleted from the job request table in step 39c05. In step 39c06, it is checked whether all the jobs requested to each printer controller have been completed. If there are still jobs remaining in the printer controller, the process returns to step 39c04 to wait for the completion of the job in the printer controller. If the jobs in all the requested printer controllers are completed in step 39c06, the job table (FIG.
From 0), delete the record of the job.

Steps 3901 and 39 in FIG. 68
In 02, it is determined whether the PDL Rasterizer can be used and whether the data receiving method has been determined. If completed, in step 3903 the data receiving method is confirmed. When referring to external data, access is started in step 3904 and the process waits in step 3905. On the other hand, if it is within the job, the process waits at step 3906. Step 3905 or 3906
In step 3907, when reading or receiving of data is started, the data is converted to a PDL Rasterizer
Start feeding. Then, in step 3908, the PDL
Receive image data from Rasterizer, step 39
At 09, the printer controller to be used is determined.
This decision is made by print job managers 501-507 and 50
Attribute ID 2001 of the 9 attribute table (Controller ID for executing Job
List) and the content of the print job file (the attribute I and attribute of the job file shown in FIG. 52) by specifying the permission by the attribute ID 2002 of the print job manager 508 (whether or not the controller can be automatically selected). Value) may dynamically determine the printer controller required for printing. In this case, for example, if color printing is specified by the attribute ID and attribute value in the job file, Ink Jet Controller 512 (CID23) is determined, and use of Finisher is specified by the attribute ID and attribute value. For example, LBPController510 (CID21) is determined. When the printer controller is determined, in step 3910 image data is input to each printer controller and a job ID is received from the printer controller. Step 39
In step 11, the job ID, the printer controller ID, and the job ID received from the printer controller are recorded as separate records for each printer controller in the job request table (FIG. 21). Thereafter, the print job manager waits for the end of the job in each printer controller in step 3912, and when notified of the end of the job from the printer controller, deletes the corresponding record from the job request table in step 3913. In step 3914, it is checked whether all the jobs requested to each printer controller have been completed. If any jobs remain in the printer controller, the process returns to step 3912 to wait for the job completion in the printer controller. If the jobs in all the printer controllers requested in step 3914 are completed, in step 3921 the count data format table of the UID or AID to be charged for the current job (see FIG.
116), the job is counted in the current count data table (FIG. 115), and the job table (FIG.
Delete the record of the job from 0). At the same time, an event transmission process shown in FIG. 77 is performed. In step 3916, the inside of the job file is inspected, and in step 3917, it is checked whether or not there is an attribute value instructing the event transmission regarding the job end. If not, the process ends, but if there is, in step 3918 the attribute value is read to obtain the transmission method and transmission destination. Steps
At 3919, an event transmission packet is created, and the event is transmitted to the specified transmission method and transmission destination.
In step 3920, end processing such as deletion of the job file / data file is performed, and the job processing ends.

(Job Processing in Scan Job Manager) FIG. 69 shows a job processing flow in the scan job manager 419. The scan job manager starts processing the job after the job input is completed. For this reason, the scan job manager
FIG. 69 shows the job termination process of step 3815 in 61.
Start job processing. First, in step 4001, a job event handler for processing an event related to a job is started. The job event handler is another task that operates in connection with the job, and the details of the operation are described in FIG. Next, in step 4002, a job processing request is made to the scan controller. The details of this processing are described in FIGS. 70 and 71-described later. In step 4003, transmission processing of data obtained by the scan is performed. The details of this processing are described in FIG. In step 4004, account processing of resources used by the job is performed. The details of this processing are described above with reference to FIG. Finally, in step 4005, the job event handler started first is terminated, and files and the like used for the job processing are deleted. Then, the job processing in the scan job manager ends.

(Scanner Controller Processing) FIG. 70 shows a processing flow of a job requested to the scanner controller. In step 40a01, a job is input to the scanner controller 420 and a job ID is received.
In step 40a02, the job ID, the scanner controller ID, and the job ID received from the scanner controller 420 are recorded in the job request table (FIG. 21). Step 4
In step 0a03, the process waits for the job end from the scanner controller 420. When the job end is notified from the scanner controller 420, the scanned image data is received from the scanner controller 420. Delete record. In step 40a05, the record of the job is deleted from the job table (FIG. 20).

(Scanner Controller Internal Processing) FIG. 71
12 shows a flow in which the scanner controller 420 processes a scan job requested by the scan job manager 419. First, in step 40b01, the scanner controller requested for the job uses the sensor of the Scanner Engine to check the type of the document to be scanned. The type of original is color original, monochrome original, blue print original, text original,
It is possible to check various types such as an image original, a mixed original of text and image, and the like. Also, the setting state of the prescan designation is checked. The setting of the prescan state can be set as the state of the device itself, or can be set to start in the prescan state when submitting a job. After checking the document type and prescan settings,
At 40b02, the attribute of the document file is read, and it is checked whether or not there is a matching document type and prescan designation setting. In step 40b02, if there is a matching original type and pre-scan designation, the process proceeds to step 40b03, where the attributes of the document file are read, and the document format (resolution, image format, etc.) to be generated after scanning is included in the generated data list. to add. Then, in step 40b04, it is checked whether or not a document is further specified. If there is, the process returns to step 40b02; otherwise, the process proceeds to step 40b05. Also,
If no matching document type and prescan designation are found in step 40b02, the process proceeds to step 40b05. In step 40b05, the generated data list is checked to determine the scanning conditions. At this time, the generated data list is checked, a scan operation is performed with the common multiple of the resolution of the plurality of data to be generated, the highest resolution of the device or the highest resolution required in the list, or a multi-valued image, and then the data is scanned. By performing format conversion, the number of scan operations can be reduced. In step 40b06, an actual scan operation is performed. In step 40b07, data in a format according to the generated data list is generated. Next, step 40b08
It is checked whether all data in the generated data list has been generated. If desired data can be obtained by converting data obtained by one scanning operation, the process returns to step 40b07 to generate desired data. If a further scan operation needs to be performed, the process returns to step 40b05. If it is determined that all data in the generated data list has been generated, step
Proceed to 40b09. In step 40b09, it is checked whether or not to continue the scanning process. Here, the conditions that require continuous scanning are as follows: the pre-scan setting is on, the main scan operation is performed, or if multiple originals are placed on the platen, There is a case to proceed. If it is determined that the scan needs to be continued, the process returns to step 40b01. Otherwise, the end process such as discarding various data generated during the process is performed, and the series of process flows ends.

(Data Transmission Processing) FIG. 72 shows a processing flow for transmitting data after scanning. Step 40
At c01, a search is made for attributes instructing the data transmission method from the attributes in the job. And send it as a script. Details of the data transmission process from the device are shown in FIG. If the instruction is to send data as a reference in step 40c01,
At 40c02, the data is stored inside the device, and reference information for the data is transmitted as a script together with other attribute information.

(Job Processing in Copy Job Manager) FIG. 73 shows a job processing flow in the copy job managers 601 to 608. The copy job manager starts processing the job after the job input is completed. Therefore, the job manager starts the job processing in FIG. 73 as the job end processing in step 3815 in FIG. First, in step 4101, a job event handler for processing an event related to a job is started. The job event handler is another task that operates in connection with the job, and the details of the operation are described in FIG. Next, step 41
In 02, a job processing request is made to the scan controller. The details of this process are described in FIGS. 70 and 71-above. In step 4102, image data is obtained. In the next step 4103, a job processing request is made to the print controller using the image data. The details of this processing are described in FIG. In step 4104, account processing of resources used by the job is performed. The details of this processing are shown in FIG.
This has been described above. Finally, in step 4105, the job event handler started first is terminated, and files and the like used for the job processing are deleted, and then the job processing in the copy job manager is terminated.

(Job Processing Download) FIG. 74 shows the font manager 413 and form overlay manager 4
14, the job flow in the log manager 415 and the color profile manager 416 relating to the data download function. The jobs for these managers are for downloading and uploading data managed by each manager. Management such as reference / deletion of data managed by each manager is performed by inputting a command packet to a subaddress managed by the supervisor 410 and accessing an attribute table of each manager as shown in FIG. Each manager starts processing of the job related to data download after the job input is completed. For this reason, each manager performs step 38 in FIG.
As the end processing of the 15 job, the job processing related to data download of FIG. 74 is started. In step 4201, the job file (FIG. 56) is scanned to check whether an attribute related to the data receiving method exists. If there is no attribute relating to the method of receiving data as a result of the check, the job file is related to uploading, and the processing is terminated assuming that the processing flow shown in FIG. 75 has already been performed. Step 42
In the end processing in 08, the job file is deleted.
If there is an attribute related to the data receiving method in step 4201, the data receiving method is checked in step 4202. If the data reception method is included in the job (in the case of data reception by the “Send” operation code in FIG. 69), the data has already been received, and the received data is saved as a file in step 4205. If the data reception method is data outside the device, the external source designated in step 4203 is accessed, data is acquired, and the acquired data is saved as a file in step 4205. The file information saved in step 4205 is
At 06, a management table managed by each manager (a font table for the font manager 413 (FIG. 28), a form overlay table for the form overlay manager 414 (FIG. 31), a log table for the log manager 415 (FIG. 34),
In the case of the color profile manager 416, it is registered by writing a new record in the color profile table (FIG. 39). In step 4207, end processing such as deletion of the job file / data file is performed, and the job processing ends.

(Job Processing Upload) FIG. 75 shows the font manager 413 and the form overlay manager 4.
14, the job flow in the log manager 415 and the color profile manager 416 relating to the data upload function. Each manager configures the job script “Send Reques
When the "t" operation code is input, the processing of the job relating to the data upload starts. For this reason, each manager starts the job processing relating to the data upload of FIG. 75 as the processing dependent on each manager in step 3821 in FIG. At step 4301, the attribute that indicates the data transmission method is checked from the attributes in the job file (FIG. 53).
If the data transmission method is an instruction to transmit data as a script in 4301 (NO), in step 4303, the data specified in the job is transmitted as a script together with other attribute information. Details of the data transmission process from the device are shown in FIG. Step 4301
If the instruction is to send data as a reference, the reference information for the data specified in the job is transmitted as a script together with other attribute information.

(Job Management in Each Manager) FIG. 76
Is the print job manager 5 in the multifunction peripheral 201
13 shows a processing flow performed when a Client gives an operation instruction (job deletion) for a job managed by the scan job manager 419 and the copy job managers 601 to 608. The operation on the job managed by each manager is performed by transmitting an appropriate command packet to the subaddress of the supervisor. The job management command packet includes, as parameters, a service ID for specifying the target job manager and a target job ID. The command packet sent from the Client to the multi-function peripheral 201 is
It is processed by the flow shown in FIG. 47 and distributed to the supervisor 410. The processing flow shown in FIG. 76 is a detailed version of the step 3603 (processing of other Operation Code) in the flow shown in FIG. 77. In step 4401,
Supervisor 410 checks whether the operation code is for job deletion ("Cancel Job"). If the operation code is not “Cancel Job”, another processing step 4409 described later according to the operation code is performed, and the processing ends. If the operation code is "Cancel Job" in step 4401, the service ID specified in the parameter in step 4402
, The parameters are sent to each manager corresponding to the service ID. In step 4403, each manager searches the job request table managed by each manager for the specified job ID. If there is no job ID specified in the job request table in step 4404, it is determined that the job in the controller has already been completed.
In step 10, the corresponding record is deleted from the job table, and in step 4411, a reply packet is created and transmitted, and the processing ends. If the job request table contains the specified job ID in step 4404, the job ID of the controller corresponding to the specified job ID and the controller ID of the controller executing the job are acquired in step 4405. In step 4406, the controller corresponding to the controller ID is instructed to delete the job by designating the job ID of the controller. Step 44
At 07, an execution result from the controller is awaited. If the execution result is unsuccessful, an error reply packet is created and transmitted at step 4408, and the process ends. If the execution result from the controller is successful in step 4407, the corresponding record is deleted from the job request table in step 4408, the job request table is searched in step 4403, and the request to another controller is executed. Check again if it has been done.

(Event Transmission) FIG. 77 shows a processing flow of event transmission in each manager.
Each manager has an event setting table as shown in FIG. 16 as a value of an attribute table held by each manager. As shown in the description of FIG. 16, this table describes connection types and destinations for transmitting an event when the event occurs. When an event occurs, each manager recognizes the event ID for the event. After that, in step 4501, the event setting table is searched to see if the event ID is registered. If no event ID is registered in step 4502, the process ends.
If at least one event ID has been registered in step 4502, the connection type used to send the event and the destination to send the event to are acquired from the first record in step 4503, and an event transmission packet is created in step 4504 I do. In this packet, a parameter defined for each event ID and a parameter according to the format for each event ID registered in the event format table (FIG. 17) held by the supervisor 410 are added. In step 4505, the event transmission packet is transmitted to the transmission destination of the connection format acquired in 4503. In step 4506, it is determined whether or not steps 4503 to 4505 have been repeatedly performed for all records having the event ID.
And if all records have been processed, the processing is terminated.

(Transmission of Data Script from Multifunctional Peripheral Device) FIG. 78 shows a processing flow when data is transmitted from the multifunctional peripheral device 201 as a script which is a sequence of command packets. This processing flow is used in a transmission step 4008 of image data obtained as a result of a scan job, a transmission step 4303 of font data, and the like. In step 4601, a packet including a data attribute is generated and transmitted. Step 45 if necessary
Repeat 01 to send multiple attributes. In step 4602, data designated to be transmitted is obtained. The command packet has the structure shown in FIG. 46, and the size that can be transmitted as a parameter is limited.
Check the length of the data. As a result of the inspection, when the length of the data exceeds the length of the limit value (64 Kbytes), the data is cut at the length of the limit value in step 4606, and the obtained data is added as a parameter in step 4607. Generate and send command packets. In this command packet, “Send” is set as the operation code, and the continuation flag is set as true. Step 4608
In step 4603, the remaining disconnected data is obtained.
The data length is checked again. If the result of the check in step 4603 indicates that the data length is within the limit value of the command packet, in step 4604 a command packet to which data is added as a parameter is generated and transmitted.
In this command packet, “Send” is set as the operation code, and the continuation flag is set as false.
In step 4605, a command packet including the remaining attributes is generated and transmitted. If necessary, repeat step 4501 to send a plurality of attributes and end.

(Hardware Configuration of Client PC) FIG. 79 is a diagram showing a common hardware configuration (controller) of the Client PCs 202, 203, 204, and 205 of the present embodiment shown in FIG. Inside the controller, the CPU 6001 is connected to the Mem via the bus 6010.
ory (RAM) 6002, display 6003 such as CRT, pointing device 6004 such as keyboard and mouse, ROM6008, D
ISK6009 is connected. Various programs and data shown in FIG. 108 are stored in a DISK 6009 (storage medium) such as a hard disk or a floppy disk, and are sequentially read out to a Memory (RAM) 6002 as needed and executed by the CPU 6001. This DISK6002 can be detached from Client PC
t It may be built into the PC. Further, the program shown in FIG.
(10BASE-T), IEEE1394 interface cable 206, I
Other clients via EEE1284 interface cable 207
A configuration that is downloaded from the PC or the MFP 201 and stored in the DISK 6009 may be used. The hardware shown in FIG. 79 constitutes the general Client PC shown in FIG. The CPU 6001 performs display by writing data to the display 6003, and the CP
The U6001 reads data from the pointing device 6004 to input an instruction from the user.

A bus 6010 is connected to a network interface connector 6005, an IEEE1394 interface connector 6006, and an IEEE1284 interface connector 6007. Is connected. The CPU 6001 performs communication using each interface by reading or writing data from these interfaces.

(Software Configuration of Client PC) FIG. 80 shows Clients 202, 203, 204, 20
5 shows a part of a software (control program) block diagram. Software (control program) and data used by the Client PC are stored in the DISK 6009 as shown in FIG. 501 is a user interface,
As a result, the respective drivers and utilities 505 to 514 display the information of the multi-function peripheral 201 on the display 6003. Reference numeral 502 denotes a database (DISK6009) for holding information (data) of the multifunction peripheral 201 currently in use. When the Client connects to the multifunction peripheral 201, the device information acquisition unit of the 503 has the device. All information is acquired and stored in the 502 database. Five
04 is used in each attribute table held by the multifunctional peripheral device 201, meaning of each attribute, data type for each attribute ID, parameter format specified for each event ID,
Definition database (DISK6009) that holds the definition information such as the meaning of the task type and the sub address of Supervisor
It is. Each of the drivers and utilities indicated by 505 to 514 operates based on the definition database 504 and the device information database 502. Reference numeral 5050 denotes a printer driver, which generates a print job script according to an instruction from an application program operating on the Client PC. 506 is a scanner driver and Client PC
A scan job script is generated according to an instruction from an application program operating on the above. A copy driver 507 generates a copy job script according to an instruction from an application program operating on the client PC. A font management utility 508 generates a job for downloading and uploading font data, and generates a command for managing font data. A form overlay management utility 509 generates a job for downloading and uploading form overlay data, and generates a command for managing the form overlay. A log management utility 510 generates a job for downloading and uploading log data, and generates a command for managing logs. A color profile management utility 511 generates a job for downloading and uploading color profile data, and generates a command for managing the color profile. Reference numeral 512 denotes a job management utility, which generates a command for performing management such as deletion, suspension, and execution restart of a print job, a scan job, and a copy job. A device management utility 513 generates a command for acquiring the status of the printer controller / scanner controller. Reference numeral 514 denotes an accounting management utility that generates a command for acquiring accounting data.

Reference numeral 515 denotes a generator that generates a command packet based on commands generated from the drivers and utilities indicated by 505 to 514. The generated command packet is transmitted to the multifunction peripheral 201 by using the transport processing modules 517, 519, and 521.
Send to The generator 515 interprets reply packets and event packets input from the transport processing modules 517, 519, and 521 and distributes them to an appropriate driver or utility. Reference numeral 517 denotes a processing module of SBP-2 which is a transport layer of IEEE1394.
519 is a processing module for TCP / IP and UDP / IP. Five
Reference numeral 21 denotes a processing module of IEEE1284.4 which is a transport layer of IEEE1284. Reference numeral 518 denotes an interface for processing a physical layer of IEEE1394. 520 is a network interface. Reference numeral 522 denotes an interface for processing a physical layer of IEEE1284. FIG. 80 also shows the internal configuration of the user interface manager 405 in the software (control program) block diagram (FIG. 4) of the multi-function peripheral 201. In the case of the user interface manager 405, the SBP
2 Processing module 517, TCP / IP and UDP / IP processing module
519, IEEE1284.4 processing module 521, network interface 518, network interface 520,
The IEEE1284 interface 522 does not exist, and the generator 515 is directly connected to the interpreter 409 in FIG. 4, thereby exchanging command packets, return packets, and event packets. This direct connection does not exist in the software (control program) configuration of the other Clients 202, 203, 204, 205.

(Packet Generation / Transmission Process) FIG. 81 shows a case where the generator 515 receives a command or a job script from each of the drivers and utilities 505 to 514 and generates a command packet shown in FIG. The processing flow transmitted to 201 is shown. Prior to this processing flow, it is assumed that an appropriate sub-address of the multifunction peripheral device to be transmitted is connected in advance. Information on which sub address to connect to is obtained by the device information obtaining flow shown in FIG. The job script is defined by a series of commands. If the processing target is a job script, steps 4701 to 4706 are repeated until all commands are processed. In the following description, issuance of a job script means that processing from step 4701 to step 4707 is performed for each command. In step 4701, the length of data to be transmitted together with the command is checked. As a result of the inspection, if the length exceeds the limit value of the parameter (64 Kbytes), the data is cut at the length of the limit value in step 4702. In step 4703, the disconnected data is
A packet including an operation code corresponding to the command is generated with the continuation flag set to true, and the packet is transmitted in step 4704. If the length of the data falls within the length of the parameter limit value in step 4701, a packet including an operation code corresponding to the command is generated in step 4705 with the continuation flag set to false, and the packet is transmitted in step 4706.

(Information Acquisition at Client and Automatic Software Configuration) FIG. 82 shows a processing flowchart of the device information acquisition unit 503 in FIG. The device information acquisition unit 503 performs the processing shown in FIG. 82 immediately after the Client connects to the multi-function peripheral device 201, acquires the device information, and acquires the device information database 502 (DISK6009).
To hold. This processing also operates again when a configuration change event is sent from the device. In step 4801, the Client PC connects to the multi-function peripheral 201. Specifically, the Client PCs 202 and 203 connected to the Ethernet 208 specify the IP address and port number, connect to the multi-function peripheral 201, and output IP packet data. The Client PC 204 connected to the IEEE1394 interface 206 specifies the node ID and the LUN (logical unit number), connects to the multi-function peripheral 201, and outputs SBP-2 packet data. IEEE1284 interface 207
Is connected to the multi-functional peripheral device 201 by designating a socket number and outputs IEEE1284.4 packet data. The sub address of the connection destination is a supervisor specified in advance for each connection type used for connection.
Use a subaddress for This specified value is obtained from the specified information database 504 (DISK 6009). Step 4
At 802, the attribute ID 10 in the supervisor attribute table shown in FIG.
Get the value of 0 (list of attribute IDs). The acquisition of the attribute value is performed by generating an attribute value acquisition command (Get) using the service ID 0 and the attribute ID of the supervisor as parameters and inputting the command to the generator 515. The generator 515 performs the processing flow of FIG. 65, and transmits a command packet for acquiring an attribute value to the multi-function peripheral 201.
The multi-functional peripheral device 201 receives the command packet, and returns the attribute value of the specified attribute ID to the Client by performing the processing flow of FIGS. 47 and 48. The Client analyzes the reply packet by the generator and sends it to the device information acquisition unit. The attribute of the attribute ID 100 is a list of all attribute IDs in the attribute table of the supervisor. In step 4803, an attribute ID is designated to acquire an attribute value, and in step 4804, the process is repeated until all attribute values of the attribute ID are acquired, and the attribute value is stored in the device information database 50 together with the attribute ID.
Save to 2. In the above steps, the attribute table (FIG. 7) of Supervisor is all stored in the device information database 502.

Then, in step 4805, a service ID list (SID: TASK TYPE table shown in FIG. 11) is obtained from the attribute table stored in the device information database 502 (DISK 6009). Note that the service ID can also be obtained by generating a service ID list inquiry command (LISTSERVICE) and inputting the command to the generator 515. At this time, in the multi-function peripheral 201, FIGS.
8. The processing flow shown in FIG. 49 is executed. Step 4
In steps 806 to 4811, information of each manager is obtained for each service ID obtained in step 4805. In step 4806, from the list shown in FIG.
Service ID 1 (print job manager 50) which is the first service ID among service IDs except (service ID 0)
1) to get. In step 4807, a sub address corresponding to the service ID is obtained. The acquisition of the sub address is performed by generating a command (Reserve) for acquiring the sub address using the service ID as a parameter and inputting the command to the generator 515. At this time, multifunctional peripheral devices 20
In 1, the processing flows shown in FIGS. 47, 48, 49, and 50 are executed. The acquired sub address is stored in the device information database 502. In step 4808, the value of the attribute ID 100 in the attribute table of each manager (list of attribute IDs)
To get. The acquisition of the attribute value is performed by generating a command for attribute value acquisition (Get) by designating the service ID and the attribute ID corresponding to each manager as parameters and inputting the command to the generator 515. In step 4809, an attribute ID is specified to acquire an attribute value. In step 4810, the process is repeated until all attribute values of the attribute ID are acquired, and the attribute value is stored in the device information database 502 together with the attribute ID. In step 4811, it is determined whether the service ID is the last service ID in the service ID list.
At 4812, the service ID next to the list is acquired from the list, and the processing from step 4807 is repeated. Step 4811
In the list of service IDs (print job managers 501, 502, 503, 504, 505, 506, 50
7, 508, 509, scan job manager 419, copy manager 601, 602, 603, 604605, 606, 607, 608, font manager 413, form overlay manager 4
14. The attribute values of the log manager 415, the color profile manager 416, the printer controllers 510, 511, 512, and the scanner controller 420) are stored in the device information database 502 together with the attribute ID. And step 4813
Then, based on the device information (data) stored in the device information database 502 (DISK 6009), a user interface for a manager corresponding to each of the driver utilities (control programs) 505 to 514 is automatically configured. The processing of the automatic configuration step 4813 includes updating the user interface, and changes the display of the setting screen (user interface) according to the driver / utility. For example, the user interface of the printer driver supports based on the attribute value of the attribute ID 1101 of each print job manager (501 to 509) as shown in FIGS. 81 and 82 showing the display screen displayed on the display 6003. PDL list, attribute ID1
Coloring is possible based on 102 or Finishing type supported based on attribute value of attribute ID1103, attribute ID1
Highest resolution that can be set based on 104 attribute values, attribute ID 110
Change the display of the lowest configurable resolution based on 5. Similarly, the display of the user interface for the other drivers 506 and 507 and the utilities 508 to 514 is changed according to the attribute. Further, icons of each driver / utility (print manager, copy job manager, etc.) are displayed in an identifiable manner. Finally, in step 4814
The connection with the Supervisor 410 ends, and the process ends.

(Issuing a job specifying a task type)
FIG. 83 illustrates processing when each application / utility issues a job script specifying a task type. Issuing a job specifying a service ID is performed by using the device information database 50
2), and by sending an appropriate job script to the obtained sub-address, if only the task type is specified by the user's instruction, the service used for the multi-function peripheral 201 It is necessary to give an ID introduction request. FIG. 83 shows the processing in this case. In step 4901, an attribute value acquisition command for acquiring a service ID by designating a task type is generated, and the command is input to the generator 515. In the multifunction peripheral 201, FIGS. 47, 48, 49,
The processing flow shown in FIGS. 50 and 51 is executed. In step 4902, the device information database 502 is searched based on the service ID obtained in step 4901, and the job script is transmitted to the obtained sub-address.

(Structure of Event) FIG. 84 shows the structure of an event sent from the multi-function peripheral 201 to the Client. The event packet has the same structure as the command packet shown in FIG. 46, and the one shown in FIG. 84 is the structure of the parameter 3110 of the packet. 5001 is an event ID indicating the type of event. 5002 is parameter data defined for each event ID. The format of this data is stored in the regulation information database 504 in advance. 5003 is parameter data whose format is determined by the device for each event ID. The format of this data is held as an event format table (FIG. 17) in the device information database 502 by executing the processing flow of FIG. 82.

(Processing of Event) FIG. 85 is a flow chart showing the processing when the Client receives an event from the multifunctional peripheral device 201 for each driver / utility. Each driver / utility registers in advance a desired event in the generator 515 using the event ID as a key. When an event is sent from the multi-function peripheral 201 to the client, the generator 515 distributes the event to each registered driver utility. Figure 85
Indicates the processing after each driver / utility receives the distribution of the event. In step 5101, the specified parameter data 5002 is analyzed based on the format information obtained from the specified information database 504. In step 5102, an event format 1302 corresponding to the event ID is acquired from the event format table (FIG. 17) held in the device information database 502 using the event ID (5001) as a key. In step 5103, based on the acquired event format, the device-dependent event format (the attribute of the event format)
(ID676: paper size, ID756: paper type, ID666: toner type, ID698: ink type, ID600: cover position) are analyzed. Then, the parameters analyzed in step 5104 and the event ID (event ID 200: no paper, ID 39
9: No toner, ID432: No ink, ID234: Cover open of multi-function peripheral device) and display according to the event (for example, user interface such as no paper, cover open, no toner) on display 6003 )I do.

(Log Processing) FIG. 86 shows a flow in which the log management utility 510 acquires and processes a log held by the multi-function peripheral 201. In step 5201, log data is obtained. Acquisition of log data
This is performed by generating a log data acquisition job script and sending it to the multi-function peripheral 201. In the multifunctional peripheral device 201, the processing flows shown in FIGS. 47, 56, and 75 are executed, and log data is sent to the client. For example, the log data of LogFormatID1, 98/1/3 1:23 shown in FIG.
1.23, "OK" means that the user ID that issued the job to the print job manager with service ID 1 is 12345, the number of output papers is 4, the used toner amount is 1.23, and the job end status is OK Is shown. In step 5202, a log format table (FIG. 36) is obtained from the device information database 502. In step 5203, the log format ID 2401 at the beginning of each record of the log data is obtained, and the log format 2502 is obtained from this value from the log format table (FIG. 36). For example, the format “1: 701, 1: 565, 1: 765, 1: 777” of LogFormatID1 is a service I
It shows the user ID that issued the job to the print job manager of D1, the number of sheets output, the amount of toner used, and the end state of the job. The format “11: 701, 11: 565, 11: 765, 11: 777” of LogFormatID2 is the service ID 1
The print job manager indicates the user ID that issued the job, the number of sheets output, the amount of toner used, and the end status of the job. In step 5204, the log data 24
The analysis of 03 is performed in accordance with the log format 2502, and the analyzed data is processed (such as sorting the logs) together with the log generation time 2402. Then, in step 5205, it is determined whether or not the log data of each record has been analyzed. If not analyzed, the processing from step 5203 is repeatedly executed, and if all the data has been analyzed, the processing ends.

(Acquisition and Processing of Billing Information) FIG. 87 shows a flow in which the billing management utility 514 acquires and processes billing data held by the multi-function peripheral 201. The billing data is represented as count data for each UID or AID held by each manager. Count data is attribute ID
The attribute table (FIGS. 7, 18, 22, 24, 26,
29, 32, 37, 40, and 44), and the value is a list of integer values for each UID or AID. The meaning of each integer value is the attribute of count data format (attribute ID 40) in the attribute table of each manager.
It is expressed as the value of 2), and the value is a list of attribute IDs for each UID or AID. The count data list and the count data format list correspond to each other in the order in the list. For example, the third value of the count data is the same UID in the count data format
Or it means the information of the third attribute ID of AID. Figure
Reference numeral 87 denotes a flow for acquiring and processing the count data held by each manager. In step 5301, specify the service ID of the target manager,
Get the value of attribute ID 401 (count data value). For example, user ID (or account ID) 2 of attribute ID 401
The counter value of 003 (45, 78, 34, 13) indicates the number of prints of the paper size represented by the count data format of the user ID (or account ID) 2003 of the attribute ID 402. The acquisition of the value of the attribute ID 401 is based on the service ID and the attribute I.
D is performed by generating an attribute value acquisition command using the parameter as a parameter and inputting the command to the generator 515. In step 5302, the same service ID
Is specified, and the value (value of the count data format) of the user ID (or account ID) 2003 of the attribute ID 402 is acquired. For example, the attribute value 565 of the user ID (or account ID) 2003 of the attribute ID 402 is the number of prints of the paper size A2, the attribute value 537 is the number of prints of the paper size A3, the attribute value 545 is the number of prints of the paper size A4, and the attribute value 523. Means the number of prints of paper size A5. This may be obtained from the device information database 502. In step 5303, the count data is analyzed using the acquired count data format. In step 5304, the accounting data is processed and generated using the analyzed count data, for example, for each service ID, each user ID, each account ID, and each department, and the process ends.

(Issue of Print Job and Data Download Job) FIG. 88 shows issuance of a print job by the printer driver 505, issuance of a font data download job script by the font management utility 508, and issuance of a form overlay data download job script by the form overlay utility 509. , A log data download job script by the log management utility 510 and a color profile data download job script by the color profile management utility 511. The processing flow by the above software (control program) is common, and the document data to be printed and the data to be downloaded of each type (font data, form data, color profile data, log data) are shown in FIG. In the description, "data" is described. When a job is issued, data to be printed or downloaded is specified together with a plurality of attribute values set in the job script. First, in step 5401, a check process of device information is performed. The details of this processing are described later with reference to FIG. Next, in step 5402, a device status check process is performed. The details of this processing are described later with reference to FIG. After the completion of the check processing in steps 5401 and 5402, step 54
At 03, job processing with a user management function is performed. The details of this processing are described later with reference to FIG. If the job processing with the user management function is not performed, this step may be omitted. Step 54
In 04, a data transmission method determination process is performed. Details of this processing are described in FIG. next,
In step 5405, an account check process is performed. The details of this processing are described in FIG. Finally, in step 5406, the job script generated in the previous steps and other job scripts necessary for performing the print job are input. Multifunctional peripheral device 20 that received the job script
56, 61, 64, 65, 66,
Perform the processing shown in FIG. 67, FIG. 68 (or more, print job manager) or FIG. 56, FIG. 61, or FIG. 74 (or more, font manager, form overlay manager, log manager, color profile manager), and specify the job Is performed.

(Device Information Checking Process) FIG. 89 shows a device information checking process flow performed when each job is issued. In step 54a01, the device information database 502 is accessed to obtain device information. In step 54a02, by referring to the attribute table of each manager to which the data is to be input (for example, a print manager that designates printing in the case of document data to be printed), each attribute for which the designated attribute value is set in the attribute table Checks if it is within a range of values. As a result of the check, if even one is not within the range, step 54a0
In step 5, a job issuance rejection process is performed, such as displaying an error dialog on the user interface, and the process ends. As a result of the check in step 54a02, when all the attributes are within the range of each attribute value in the attribute table of the manager, in step 54a03, the prohibition setting attributes (attribute IDs 801 to 805) exist in the attribute table of the manager. Check if it is. If the manager's attribute table has a prohibition setting attribute, in step 54a04, is the job attribute specified for each prohibition setting attribute in the manager's attribute table not a combination of prohibited setting values? To check. As a result of the check, if there is a combination of the setting values of the prohibited attributes, step 54a05
Performs a job issuance rejection process, and terminates.

(Status Check Processing) FIG. 90 shows status check processing prior to job issuance. In step 54e01, a status attribute is obtained. To obtain the status attribute, the service ID of the target manager and the attribute ID 106
Is transmitted as a parameter. The multi-function peripheral 201 analyzes the Get command according to the steps shown in FIG. 48 and returns the value of the attribute ID 106. Step 54e
In 02, whether the current status is normal or abnormal is identified by the attribute ID 106. If it is normal (attribute value = 0), the job issuing process is continued. If it is not normal (attribute value = 0) in step 54e02, in step 54e03, the current status is “conditional normal (attribute value = 1)” or “abnormal (attribute value =
2) ”is identified by the attribute ID 106. `` Abnormal (attribute value
= 2) ”, in step 54e07, the reason why the job service is disabled is acquired. The acquisition is performed by acquiring the value of the attribute ID 108 of the manager that is the target of the multi-function peripheral 201. Step 54e08
To display "reason currently unavailable" and end the process. If the current status is “conditionally normal (attribute value = 1)” in step 54e03, “list of attributes to be referred to when there is a restriction” is acquired in step 54e04. The acquisition is performed by acquiring the value of the attribute ID 107 of the manager that is the target of the multi-function peripheral 201. In step 54e05, the values of all the attributes indicated as the values of the list in step 54e04 are acquired. In step 54e06, the contents of the job to be issued and all the attribute values of the list acquired in step 54e05 are compared to determine whether the job can be issued. If the job can be issued, the job issuing process is continued. If it is determined in step 54e06 that the job cannot be issued, in step 54e08, "the reason why the current job cannot be issued" is displayed, and the job issuance process ends. Note that the status display mode is not limited to the above-described embodiment, and may be classified or classified stepwise in another mode.

(Job Processing with User Management Function) FIG. 91
Represents an inspection process of user information before issuing a job.

In step 54b01, a user ID and a user password are input.

In step 54b02, the service ID corresponding to the job manager to which the job is to be submitted and step 54b0
Inquire the peripheral device for the user ID and user password entered by the user in step 1. The inquiry is performed by inputting a command using the “CheckID” as an operation code and the user ID, the user password, and the service ID as parameters to the multi-function peripheral 201. Multifunctional peripheral 2
At 01, the input command is processed according to the flow shown in FIG. 51A, and it is checked whether the input user information is authenticated and a reply is made. Steps
At 54b03, return data is received from the multi-function peripheral 201 and analyzed. In step 54b04, step 54b03
Then, it is checked whether the reply received from the multi-function peripheral 201 is a job issuing permission. If the job issuing permission is permitted, the job issuing process is continued.

If the job is not permitted to be issued in step 54b04, it is displayed in step 54b05 that the job is not permitted. Step 54b06
Asks the user whether to enter the user ID and user password again in step 2.
Return to 54b01. If no input is made, the process ends without issuing a job.

(Data Transmission Method Determination Processing) FIG. 92 shows issuance of a print job by the printer driver 505, issuance of a font data download job script by the font management utility 508, issuance of a form overlay data download job script by the form overlay utility 509, and log management. A processing flow for determining a data transmission method when issuing a log data download job script by the utility 510 and issuing a color profile data download job script by the color profile management utility 511 is shown. First, in step 54c01, the location of the data to be transmitted is set in advance. The location of the data is set by the user specifying the address or by the application generating the address. Next, in step 54c02, the attribute value 601 (supported data download method) of the attribute table of each responsible manager in the device information database 502 is checked, and a reference pointer (URL: Uni
Check whether the job can be issued including the fiedResource Locator). If the job can be issued with the reference pointer included in the job, a job script in which the data reference pointer is included in the job is generated in step 54c06. In this case, a job script can be generated regardless of whether the transmission data is inside the client or outside. On the other hand, if the job cannot be issued with the reference pointer included in the job in step 54c02, it is checked in step 54c03 whether the transmission data is inside or outside the client. If the transmission data is outside the client, in step 54c04, the transmission data outside the client is read once, and
Move to 54c05. If the transmission data is inside the client, the process moves to step 54c06 to use the transmission data as it is. In step 54c06, a job script in which transmission data is included in the job is generated.

(Account Check Processing) In step 72d01 in FIG. 93, the charging utility acquires and analyzes charging-related data. In step 72d02, the count data is compared with the count limit data,
If they are the same, it is determined that the count data has already reached the limit, an error message (FIG. 95) is issued in step 72d04, the job is rejected in step 72d05, and the process ends. If the count data is not the same as the count limit data, it is determined that the count data has not reached the limit yet, and step 72d03
Then, the charging data acquired and the charging restriction data are compared. If they are the same, it is determined that the charge data has already reached the limit, an error message (FIG. 96) is issued in step 72d04, the job is rejected in step 72d05, and the process ends. If the billing data is not the same as the billing limit data, it is determined that the billing data has not reached the limit yet, and in step 72d06, the increment by the job to be issued is added to the count data, the result is set to N1, At 72d07, it is determined whether or not N1 is close to the count limit data. In this case, the criterion for judging whether the value is close to the limit depends on the restriction target, and the reference value may be set freely by the user or the administrator, or the setting may be fixed in advance, and there is no particular limitation. If N1 is close to the count limit data, a warning message (FIG. 97) is issued in step 72d08 to urge the user to determine whether to issue a job. If the user's reply is to cancel the job issuance in step 72d09, the job is rejected in step 72d05, and the process ends. If the user's reply is to issue the job and if N1 is not close to the count limit data in step 72d09, it is determined in step 72d10 whether N1 has reached the count limit data. N
If 1 has reached the count limit data, step
At 72d11, a warning message (FIG. 98) is issued to urge the user to determine whether to issue a job.
If the user's reply is to cancel the job issuance in step 72d12, the job is rejected in step 72d05, and the process ends. If the user's reply is to issue the job, and if N1 has not reached the count limit data in step 72d10, the increase by the current job is added to the billing data in step 72d13, and the result is N2. . Step 72
At d14, it is determined whether or not N2 is close to the charging restriction data. In this case, the numerical value serving as a criterion for determining whether or not the value is close to the limit may be set freely by the user or the administrator, or may be fixed in advance and is not particularly limited. N
If No. 2 is close to the charge restriction data, step 72d15
Issues a warning message (FIG. 99) to urge the user to determine whether to issue a job. Steps
If the user's reply is to cancel the job issuance in 72d16, the job issuance rejection process is performed in step 72d05, and the process ends. If the user's reply is to issue the job, and if N2 is not close to the charging limit data in step 72d14, step 72d17
It is determined whether or not N2 has reached the charging limit data. If N2 has reached the charging limit data,
Warning message at step 72d18 (Fig. 100)
Is issued to urge the user to determine whether to issue a job. If the user's response is to cancel the job issuance in step 72d19, the job is rejected in step 72d05, and the process ends. If the user's reply is Submit Job and step 72d17
If N2 has not reached the charging restriction data in step, the process proceeds to the next process.

(Issuance of scan job and data upload job) FIG. 101 shows issuance of a scan job by the scanner driver 506, issuance of a font data upload job script by the font management utility 508, and issuance of a form overlay data upload job script by the form overlay utility 509. , A log data upload job script issued by the log management utility 510 and a color profile data upload job script issued by the color profile management utility 511. The processing flow of each software (control program) described above is common, and the document data obtained as a result of scanning and the above-described respective types of upload target data (font data, form data, color profile data, logo data) are shown in FIG. In the following description, "data" is described. When a job is issued, a designator indicating data is specified together with a plurality of attribute values set in the job script. First, in step 5501, a check process of device information is performed. The details of this processing are described above with reference to FIG. Next, in step 5502, a device status check process is performed. The details of this processing are shown in FIG.
-As described above. After the check processing in steps 5501 and 5502 is completed, in step 5503, job processing with a user management function is performed. The details of this process are described above with reference to FIG. if,
If you do not perform job processing with user management function,
This step may be omitted. In step 5504, a process of determining a requested data format (designator indicating data) is performed. Details of this processing are described in FIG. In step 5505, a process for determining a data receiving method is performed. The details of this processing are described in FIG. Next, in step 5506,
An account check process is performed. Details of this processing are described in FIGS. Next, in step 5507, the job script generated in the previous steps and other job scripts necessary for performing the scan job are input. Each manager of the multi-function peripheral device 201 receiving the job script,
FIG. 56, FIG. 61, FIG. 69, FIG. 65, FIG. 70, FIG. 71, FIG. 68 (above, scan job manager), or FIG. 56, FIG. 61, FIG.
(The above, the font manager, the form overlay manager, the log manager, and the color profile manager) are performed, and the designated job is processed. Finally, in step 5508, data reception processing is performed. Details of this processing are described in FIG.

(Data Format Determination Processing) FIG. 1023 shows a processing flow for determining a data format when a scan job or a data upload job is issued. In this embodiment, this processing flow will be described focusing on a scan job. Therefore, if it is determined in step 55a01 that the job is not a scan job, the process proceeds to step 55a0.
Proceeding to 6, the data format suitable for the data upload job is determined, and the processing flow ends, but the details are omitted here. If it is determined in step 55a01 that the job is a scan job, in step 55a02 document type or prescan combination is set. Individual document types include a color document, a monochrome document, a blue print document, a text document, an image document, and a mixed document of text and image, and the like. It is obtained by accessing the device information database 502. This process
Document types that can be identified by the device are listed on a user interface, and a combination thereof is designated. That is, combinations such as "color original" and "image original", "monochrome original" and "text and image mixed original" are possible. Furthermore, the condition that the pre-scan setting is ON can be combined. Next, in step 55a03, the type (resolution, image format, etc.) of the scan data to be obtained is specified for the set document type or pre-scan combination. As with the document type, the resolution and image format that can be specified for the device can be obtained by accessing the device information database 502. In this process as well, data formats that can be specified in the device are listed on the user interface and specified. One data format is specified for one document type or one prescan combination. Then step 5
In step 5a04, a job script for generating a desired data format when a desired document type and prescan are combined is generated. An example of the scan job script is described later with reference to FIG. Step 55a
At 05, it is determined whether or not another data format is further set. If another data format is to be designated, the process returns to step 55a02; otherwise, the data format determination process is completed.

(Data Receiving Method Determining Process) FIG. 103 shows a processing flow for determining a data receiving method when a scan job or a data upload job is issued. First, in step 55b01, a receiving destination for receiving data is set. This is either the client issuing the job itself or a non-client. When specifying other than the client, also set detailed information such as the address of the recipient. Next, in step 55b02, it is checked whether the process to be performed is a scan job or a data upload job. If the job is a data upload job, since only data transmission can be performed, the process proceeds to step 55b05. On the other hand, in the case of a scan job, a transmission method from the device is set in step 55b03. The transmission method supported by the device can be obtained by checking the attribute value 602 (supported data uploading method) of the attribute table of the scan job manager in the device information database 502. List them on the interface and choose one of them.
In step 55b04, the set transmission method is checked, and if data transmission is set, the process proceeds to step 55b05,
If reference transmission has been set, the flow shifts to step 55b06. In step 55b05, a job script for instructing data transmission is generated. In step 55b06, a job script for instructing reference transmission is generated. When the generation of the job script is completed in any of these steps, the data receiving method determination processing is completed.

(Data Reception Processing) FIG. 104 shows a processing flow for receiving data after issuing a scan job or a data upload job. First, step
At 55c01, the destination of the received data is checked. This is set in step 55b01 of the above (data receiving method determination processing—FIG. 103). If the receiving destination is the client itself, the process proceeds to step 55c02 to receive the transmitted data or reference. On the other hand, when a destination other than the client is the receiving destination, the destination is instructed to receive the data or the reference.

(Issuance of Copy Job) FIG. 105 shows a process of issuing a copy job. As an instruction to issue a copy job, a plurality of attribute values set in a job script are specified. First, in step 5601, a check process of device information is performed. The details of this processing are shown in FIG.
2-as described above. Next, in step 5602, a process for checking the device status is performed. The details of this processing are described above with reference to FIG. After the check processing of step 5601 and step 5602 is completed,
In step 5603, job processing with a user management function is performed. The details of this process are described above with reference to FIG. If the job processing with the user management function is not performed, this step may be omitted. Next, in step 5604, account check processing is performed. The details of this process are described above with reference to FIG. Next, in step 5605, the job script generated in the previous steps and other job scripts necessary for performing the copy job are input. Multifunctional peripheral device 20 that received the job script
The copy job manager shown in FIGS. 56, 61, 73, and 6
5. The processing shown in FIGS. 71, 71, 67, and 68 is performed to manage the designated job.

(Structure of Two-Level Job Script) FIG.
1 is a configuration diagram showing a two-level job script.
In this figure, each box such as JobStart and SetJob has one command packet (see Figure 46)
And the job script is composed of a series of command packets. From the command packet-JobStart to the command packet-JobEnd is identified as one job unit. The job unit is composed of a command packet -SetJob for setting the attribute of the job and a command packet group constituting the document unit. Command Packet-From DocumentStart to Command Packet-Docum
Up to entEnd is identified as one document unit. The document unit is composed of a command packet -SetDocument for setting the attribute of the document, a command packet -Send for specifying data transmission, or a command packet -SendRequest for requesting data transmission.

(Structure of Three-Level Job Script) FIG.
2 is a configuration diagram showing a job script of three layers. In this figure, each box such as JobStart and SetJob is one command packet (see FIG. 46), and the job script is composed of a series of command packets. Command packet-JobSta
From rt to the command packet-JobEnd is identified as one job unit. The job unit is composed of a command packet -SetJob for setting the attribute of the job, and a command packet group constituting the binder unit. Also,
Command packet-BinderStart to command packet-BinderEnd are identified as one binder unit. The binder unit includes a command packet -SetBinder for setting the attribute of the binder, and a command packet group constituting the document unit. further,
Command packet-DocumentStart to command packet-DocumentEnd are identified as one document unit. In the document unit, a command packet for setting the attribute of the document-SetDocument, a command packet for specifying data transmission-Send, or a command packet for requesting data transmission-SendRequest
It consists of.

(Example of Scan Job Script) FIG.
FIG. 3 is a configuration diagram showing an example of a scan job script having two layers. In addition, as described in FIG.
It may be a scan job script having a hierarchy.
In the scan job script, each document unit is a unit for designating what type of data is generated when a specific document type is detected. The document attribute “document type” in the drawing indicates what type of document the document unit is referred to. The document attributes “resolution” and “image format” indicate the format of data generated in this document unit. In document unit -1 in the figure,
“PreScan & Color” is specified in the “document type” of the document attribute, which indicates that when the prescan specification is on and the document type is a color document, this document unit is referred to. Similarly, the document unit-2 and the document unit-3 are referred to when the document type is a color document, and the document unit-3 is referred to when the document type is monochrome. If prescanning is off and a color document is scanned, document unit-2 and document unit-3 are referenced, and 1200 dpi JPEG format data and 1200 dpi bitmap format data are generated at the same time. You. On the other hand, if the pre-scan is on and an attempt is made to scan a monochrome document, no data is generated because there is no matching document type.

The command packet -Send Req in FIG.
uest indicates which transmission method is used and to which destination data is transmitted. For example, when the transmission method is “data transmission”, the uest indicates that the data after scanning is transmitted as it is. . If the transmission method is “reference transmission”, the scanned data is stored in the device,
It instructs to send only the reference information. In addition, “client itself” and “other than client” indicate destinations to which data is actually transmitted, and network address information and the like are used (issue of job management commands). 13 shows a processing flow when a job management command is issued. In step 5701, a job table (FIG. 20) held by the manager is acquired from the MFP 201 using the service ID of the target manager as a parameter. In step 5702, a job ID of a job to be managed is selected from the job list included in the acquired job table by an appropriate method. The selection means includes a method of displaying a list of jobs on the display 6003 via the user interface 501 and allowing the user to make a selection. In step 5703, the specified job
Generate a job management command with the ID as a parameter,
Issue and end. The supervisor of the multi-function peripheral device 201 that has received the job management command is shown in FIGS. 47, 48, 49, and 5.
0, the processing shown in FIG. 51 and FIG. 76 is performed, and the designated job is managed.

Even if the present invention is applied to a system including a copier, a printer, a scanner, and the like which exist alone, an apparatus including a single device (for example, a copier,
Facsimile machine, etc.). Further, an object of the present invention is to supply a storage medium (FIG. 107, FIG. 108) storing a program code of software (control program) for realizing the functions of the above-described embodiment to the system as shown in FIG. , The device of the system (CPU301 or CPU600
1) is achieved by reading and executing the program code stored in the storage medium. As a method of supplying the program and data shown in FIG. 77 to the Client PC, a method of storing the program and data in the floppy disk FD7000 as shown in FIG. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.

As a storage medium for supplying the program code, for example, in addition to a floppy disk and a hard disk, an optical disk, a magneto-optical disk, a CD-RO
M, CD-R, magnetic tape, nonvolatile memory card,
A ROM or the like can be used. When the computer executes the readout program code, not only the functions of the above-described embodiments are realized, but also an OS (operating system) running on the computer based on the instruction of the program code. It goes without saying that a case where some or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing is also included. Further, after the program code read from the storage medium is written into a memory provided on a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that a CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

FIG. 110 is a sectional view showing the internal structure of a laser beam printer (hereinafter abbreviated as LBP) applicable to the laser beam printer engines 103 and 104 in FIG.
The BP can input character pattern data or the like and print it on recording paper. In FIG. 110, reference numeral 8012 denotes an LBP main body, which forms an image on recording paper, which is a recording medium, based on a supplied character pattern or the like. 8000 is an operation panel on which switches and LED indicators for operation are arranged,
Reference numeral 8001 denotes a printer control unit that controls the entire LBP8012 and analyzes character pattern information and the like. The printer control unit 8001 mainly converts character pattern information into a video signal and outputs the video signal to the laser driver 8002. Laser driver
8002 is a circuit for driving the semiconductor laser 8003,
The laser light 8004 emitted from the semiconductor laser 8003 is switched on / off according to the input video signal. The laser light 8004 is swung right and left by a rotating polygon mirror 8005 to scan on an electrostatic drum 8006. As a result, an electrostatic latent image of a character pattern is formed on the electrostatic drum 8006. This latent image is developed by a developing unit 8007 around the electrostatic drum 8006 and then transferred to a recording sheet. A cut sheet is used for this recording paper, and the cut sheet recording paper is stored in a plurality of paper cassettes 8008 corresponding to a plurality of types of paper attached to the LBP8012, and is fed into the apparatus by a paper feed roller 8009 and transport rollers 8010 and 8011. It is taken in and supplied to the electrostatic drum 8006.

FIG. 111 shows an ink jet recording apparatus IJRA applicable to the ink jet printer engine 105 shown in FIG.
FIG. In the figure, a carriage HC that engages with a spiral groove 9003 of a lead screw 9004 that rotates via driving force transmission gears 9010 and 9008 in conjunction with forward and reverse rotation of a drive motor 9011 has pins (not shown). And arrows a and b
It is reciprocated in the direction. An ink jet cartridge IJC is mounted on the carriage HC. 9001
Is a paper pressing plate, which presses the paper against the platen 9000 in the moving direction of the carriage. Photocouplers 9006 and 9007 are home position detecting means for confirming the presence of the carriage lever 9005 in this region and switching the rotation direction of the motor 9011. Reference numeral 9013 denotes a member that supports a cap member 9019 that caps the front surface of the recording head. Reference numeral 9012 denotes suction means that suctions the inside of the cap, and performs suction recovery of the recording head through an opening 9020 in the cap.
Reference numeral 9014 denotes a cleaning blade. Reference numeral 9016 denotes a member that allows the blade to move in the front-rear direction.
These are supported. It goes without saying that the blade is not limited to this form and a known cleaning blade can be applied to this example. Reference numeral 9018 denotes a lever for starting suction for suction recovery, which moves with the movement of the cam 9017 engaging with the carriage, and the driving force from the driving motor is controlled by a known transmission means such as clutch switching. Is done. These capping, cleaning, and suction recovery are configured so that desired operations can be performed at the corresponding positions by the action of the lead screw 9004 when the carriage comes to the area on the home position side. If this operation is performed, any of the present embodiments can be applied.

As described above, according to the present embodiment,
A logical device control program (scan job manager 419, print job managers 501 to 50) that retains the function of the logical device to which a job is input from the information processing apparatus and manages the job input to the logical device.
9. Physical device control programs (scanner controller 420, LBP controller 510, and copy job managers 601 to 608) that hold the functions of the device engine of the peripheral device and manage jobs in the device engine.
511, Ink Jet controller 512) can be used to analyze the job.

Here, the physical device control program is:
A scanner control program (scanner controller 420) for controlling a scanner engine of a peripheral device. The physical device control program is a laser beam printer control program (LBP controllers 510 and 511) for controlling the laser beam printer engine of the peripheral device. The physical device control program is an inkjet printer control program (Ink Jet printer controller 512) for controlling an inkjet printer engine of a peripheral device. The logical device control program is a laser beam printer control program for a peripheral device, an inkjet printer control program, or a print job control program (print job managers 501 to 509) for controlling the laser beam printer control program and the inkjet printer control program. The logical device control program is a scanner job control program (scan job manager 419) for controlling a scanner control program for peripheral devices. The logical device control program includes a scanner control program for peripheral devices and a laser beam printer control program or an inkjet printer control program or a copy job control program (copy job managers 601 to 60) for controlling the laser beam printer control program and the inkjet printer control program.
8).

With such a configuration, the logical device control program can hold a relationship with at least one device engine used by the logical device for executing a job. Further, it is possible to determine a device engine to be actually used for job execution based on the job input to the logical device. Further, the function held by the logical device control program can be changed. A job input to a logical device can be managed in association with a job managed by a physical device that actually executes the job. Also, there are a plurality of logical device control programs,
The optimum logical device control program can be selected by comparing the load states of a plurality of logical device control programs. In addition, it has a plurality of logical device control programs and a supervising program (Supervisor 410) that supervises the plurality of logical device control programs, and the supervising program has a sub-address used when submitting a job to each of the logical device control programs. The type of connection interface can be stored in association with each logical device control program. The supervising program holds a list of information indicating whether the sub-address is valid or invalid, and when a job is input to an invalid sub-address, the job can be discarded.
Further, the supervising program holds a list of available user authentication information, and can notify an error of the job when the user information included in the input job is not included in the list of authentication information. Further, the supervising program can hold a list of security levels indicating the types of available user authentication determination processing. Further, the logical device control program can hold a list of connection interfaces and transmission destination addresses for transmitting event data to the information processing apparatus when an event occurs during analysis of a job. Further, when an event occurs during analysis of a job by the logical device control program, event data can be transmitted with reference to a list of connection interfaces and transmission destination addresses for transmission to the information processing apparatus.

According to the present embodiment, as described above, according to the function (attribute value) acquired from the peripheral device,
A user interface of a control program for controlling peripheral devices can be automatically configured (step 4813). In addition, the display of the user interface for the peripheral device (FIGS. 81 and 82) can be controlled according to the acquired function. Further, information (attribute value) on a setting range of the function of the peripheral device can be acquired. Also,
Information on the setting range is expressed by a combination of attributes (attribute IDs 801 to 805) for which job setting is prohibited. Further, information (attribute value) related to the function options of the peripheral device can be obtained. An attribute list (attribute table) indicating the function of the peripheral device is acquired from the peripheral device, and an attribute value can be acquired by specifying an attribute ID of the attribute list. Further, an attribute list (attribute table) indicating the functions of the physical device control program, the logical device control program, the resource control program of the peripheral device, and the general control program that supervises them can be obtained from the peripheral device. The physical device control program is a scanner control program for controlling a scanner engine of a peripheral device. The physical device control program is a laser beam printer control program for controlling a laser beam printer engine of a peripheral device.

The physical device control program is an ink jet printer control program for controlling an ink jet printer engine of a peripheral device. The logical device control program is a laser beam printer control program or an inkjet printer control program of a peripheral device, or a print job control program for controlling the laser beam printer control program and the inkjet printer control program. The logical device control program is a scanner job control program for controlling a peripheral device scanner control program. The logical device control program is a peripheral device scanner control program and a laser beam printer control program or an inkjet printer control program or a copy job control program for controlling the laser beam printer control program and the inkjet printer control program. The resource control program is a font control program for managing fonts of peripheral devices. The resource control program is a form overlay control program for managing the form overlay of the peripheral device. The resource control program is a log control program for managing logs of peripheral devices. The resource control program is a color profile control program for managing the color profiles of peripheral devices.

As described above, according to the present embodiment, it is determined whether a job script can be issued to the peripheral device based on the function obtained from the peripheral device (MFP 201) (steps 5402 to 5404, step 5502). To 5504 and steps 5602 to 5604), the job issuing process can be controlled according to the result of the determination.

Here, a physical device control program, a logical device control program, a resource control program (a font manager 413, a form overlay manager 414, a log manager 415, and a color profile manager 416) for peripheral devices and a general control program for supervising them. Is acquired from the peripheral device. A combination of attributes for which job setting is prohibited (attribute IDs 801 to ID8)
05) is obtained. Further, a download job or a print job is issued to the peripheral device. Further, an upload job or a scan job is issued to the peripheral device. Further, the job issuing method is selected according to the attribute (attribute ID 601) indicating the support of the acquired function download method and the location of the data to be issued. Also,
The job issuance method is selected according to the attribute (attribute ID 602) indicating the support of the acquired function upload method and the storage location of the job issuance target data. The job issuance target data is print document data. The job issuance target data is scan document data. The job issuance target data is font data. The data to be issued is form overlay data. The job issuance target data is color profile data. The job issuance target data is log data. The job issuance target data is font data. Further, event format data corresponding to the event received from the peripheral device is obtained, and the received event is analyzed based on the event format data. Also, log data of a peripheral device and log format data of the log data are obtained, and the log data is analyzed based on the log format data. Further, the charging data (count data) of the peripheral device and the format data of the charging data are obtained, and the charging data is analyzed based on the charging format data.

As described above, according to the present invention, there is provided an input device for inputting a job script composed of packet data from the information processing device, the input device being a peripheral device connected to the information processing device. Means for the peripheral device to analyze the job script obtained in the above, and generate an appropriate job file according to the contents of the script;
The job script may comprise one or more binders and documents inside the script, the binder comprises documents and has a hierarchical structure in the job, and the peripheral device analyzes the job script having the hierarchical structure. Means for analyzing the hierarchically structured job script, generating a job file and simultaneously generating a binder file and a document file separately therefrom, and generating a document file in the binder file; and generating the job file, the binder file and By having means for appropriately processing document files, a job scheduling unit (job execution priority, job execution cancellation, etc.) and a unit (binder) that bundles several documents and each document To clearly process various controls in the unit of document as separate units, to obtain information such as the processing result of each binder unit and document unit in the job processing, and to obtain the information of each binder unit during job execution in the job processing. New settings or changes for each document or document. In a print job, processing a media unit such as paper to be output in one job and a finishing unit such as staples as another unit. In a job, it is possible to process a document reading control unit and a scan image control unit as different units in one job.

In the job issuing system with a user management function of this embodiment, means for authenticating user information prior to job issuance in a peripheral device capable of adding user information to the job and controlling execution of the job by the user information. , User information can be authenticated before issuing a job.

Further, by providing means for using a user ID for user information used for authentication, user information can be authenticated from a user ID before a job is issued.

Further, by providing means for using a user ID and a user password for user information used for authentication, user information can be authenticated by a user ID and a user password before issuing a job.

Further, by providing means for using the user ID and the type of service for the user information used for authentication, the user information can be authenticated based on the user ID and the type of service before issuing a job.

Further, by providing means for using a user ID, a user password, and a service type in user information used for authentication, a user ID can be set before a job is issued.
The user information can be authenticated based on the user password and the type of service.

Further, by having means for confirming user information before transmitting a job to the peripheral device and means for adding user information to the job transmitted to the peripheral device, a job is issued based on the user information. You can know if is possible.

In addition, by having means for using a user ID for the user information, it is possible to know whether or not a job can be issued based on the user information using the user ID.

Further, by having means for using a user ID and a user password for the user information, it is possible to know whether or not a job can be issued based on the user information using the user ID and the user password.

Further, by providing means for using a user ID and a service type in the user information,
It is possible to know whether or not a job can be issued based on the user information using D and the type of service.

Also, by having means for using a user ID, a user password and a service type in the user information, it is possible to issue a job based on the user information using the user ID, the user password and the service type. I can tell you.

According to the present embodiment, in a peripheral device capable of holding the current status of the peripheral device as information and controlling the execution of a job based on the current status, obtaining the current status of the peripheral device from the Client When a request is issued, by having a means for returning the current status of the peripheral device held, the client can obtain the current status of the peripheral device before issuing the job and execute the job. You can know if it is or is not possible.

Further, by providing means for expressing the current status of the peripheral device in three types of “normal”, “conditionally normal”, and “abnormal”, it is possible to execute the Clie before issuing a job.
The nt can grasp the current status of the peripheral device in three types of expressions, “normal”, “conditionally normal”, and “abnormal”, and can know whether the job can be executed or not.

When the current status of the peripheral device is “conditionally normal” and the client requests the reason, the “if job execution is possible with restriction and is By having a means to return the value of the "list of attributes to be referenced" attribute, the client can know the condition if the current status of the peripheral device is "conditionally normal" before issuing the job. Can be.

If the current status of the peripheral device is "abnormal" and the client requests the reason, the value of the "reason in case of abnormality" attribute held in the peripheral device is returned. With this, the client can know the reason why the job cannot be issued before issuing the job.

Further, by providing means for requesting acquisition of the current status of the peripheral device before transmitting the job to the peripheral device, the current status of the peripheral device is acquired before the job is issued. Can be performed or not.

When the current status of the peripheral device is "normal", it is confirmed that the job can be executed before issuing the job by providing a means for issuing the job. You can submit the job above.

When the current status of the peripheral device is “conditionally normal”, the “list of attributes to be referred to when job execution is possible with a restriction” held in the peripheral device Means for acquiring the value of the attribute value, a means for comparing the attribute value with the job content, and a means for issuing the job when the job content satisfies the condition of the attribute value. The job can be executed with a condition in advance, and the job can be transmitted after confirming that the condition is satisfied.

If the current status of the peripheral device is "conditionally normal", the "list of attributes to be referred to when job execution is possible with restriction" attribute held in the peripheral device , A means for comparing the attribute value with the job content, a means for canceling the job issuance when the job content does not satisfy the condition of the attribute value, and a means for displaying the reason thereof. Thus, before the job is issued, it is possible to execute the job with a condition in advance, but if the condition is not satisfied, the transmission of the job can be stopped.

If the current status of the peripheral device is "abnormal", a means for acquiring the value of the "reason for abnormal case" attribute held in the peripheral device and "a reason for abnormal case" Is displayed, it is possible to confirm beforehand that the job cannot be executed and issue the job before issuing the job.

In the example of the peripheral device account confirmation system, in a peripheral device having a job account function, means for holding a limit value for account information,
By having means for transmitting account information to the client when requested by the client, it is possible to acquire the account information before the client issues a job.

Before sending a job to the peripheral device, means for requesting the peripheral device for account information relating to the content of the job to be transmitted,
Means for analyzing the account information sent from the peripheral device as a reply, means for judging from the analyzed account information whether the content of the job to be transmitted from now does not exceed the charging limit, By providing a means for displaying an error message when the charge limit is exceeded and a means for rejecting the issuance of a job when the charge limit is exceeded, before issuing a job to a peripheral device, It is possible to determine whether the job to be issued has already exceeded the charge limit, and the transmitted job is not discarded without being executed by the charge limit on the peripheral device side.

A means for holding a reference value for judging that the account information is close to the limit value, and a means for judging from the analyzed account information whether or not the content of the job to be transmitted is close to the charging limit. Means for displaying a warning message when the charge limit is approached, means for asking the user whether to issue a job even when the charge limit is approached, and means for obtaining the user's determination whether to issue the job. Means for rejecting the issuance of a job when the user determines to cancel the issuance of the job, so that the job to be issued is close to the charging limit before the job is issued to the peripheral device. In this case, the user can select whether to execute the job or not, so that the user's intention can be reflected more on the job execution conditions. That.

In this embodiment, in a peripheral device capable of registering / holding / deleting a plurality of user IDs and their corresponding counters, means for analyzing the user ID attached to the transmitted job, By having means to charge the job to the counter according to the user ID attached to the job, the account is automatically processed only by processing the information attached to the transmitted job without having to work on the peripheral device itself. Can be managed.

A means for registering / holding / deleting an attribute indicating a relationship between user IDs belonging to each account ID in a one-to-many relationship; a means for analyzing a user ID attached to a transmitted job; By providing means for charging the job to the counter according to which account ID the user ID attached to the job belongs to, it is possible to charge to the account ID to which the user ID belongs.

A means for registering / holding / deleting a plurality of account IDs and their corresponding counters, and a user ID belonging to each account ID in a one-to-many relationship
Means for registering / holding / deleting an attribute indicating the relationship between a user ID and an account ID attached to a transmitted job
And a means for charging the counter according to the account ID to which the user ID attached to the job belongs, so that the user ID can be charged or not. It is possible to select whether to charge the account ID to which the user belongs.

[0186] Further, by providing means for analyzing the user ID and account ID attached to the transmitted job and means for charging the job to the counter in accordance with the account ID attached to the job, the account ID selected by the user is provided. Can be charged.

A means for analyzing the account ID attached to the transmitted job, a means for analyzing information on whether to charge the user ID or the account ID attached to the transmitted job, The provision of the means for charging the job to the counter in accordance with the attached account ID makes it possible to select whether to charge the user ID or the account ID selected by the user.

A means for analyzing the account ID attached to the transmitted job, a means for analyzing information on whether to charge the user ID or the account ID attached to the transmitted job, It is possible to select whether to charge to the user ID, charge to the account ID to which the user ID belongs, or charge to the account ID selected by the user by having means for charging the counter according to the attached account ID. Becomes

[0189] Further, by providing means for performing user authentication on a user ID counter or an account ID counter using a user ID and a password attached to a job, user authentication can be performed based on the user ID. It is possible to do.

Further, by providing means for attaching a user ID to a job to be transmitted to a peripheral device,
Account management using D becomes possible.

Further, by having means for attaching a user ID and an account ID to a job transmitted to a peripheral device, account management using the user ID and the account ID can be performed.

Further, by providing means for attaching information indicating which of a user ID and an account ID is charged to a job transmitted to a peripheral device, it is possible to switch account targets.

According to the present invention, it is possible to simultaneously generate a plurality of types of document data in an appropriate format desired by the user according to the type of the scanned document by a single scan job.

Also, in the peripheral device control software, by acquiring the document data format that can be generated by the scanner and the discriminable document type, it is possible to generate a job for obtaining document data in a desired format and to generate desired data. It is possible to select a scanner to obtain.

According to the present invention, a plurality of types of document data in an appropriate format desired by the user can be generated by a single scanning operation according to a prescan instruction. Also, by acquiring the document data format that can be generated by the scanner, the peripheral device control software can generate a job to obtain the document data in the desired format and select the scanner to obtain the desired data. Become.

According to the present invention, a plurality of types of appropriate document data desired by the user can be simultaneously generated by the scanning operation as small as possible.

[0197]

As is apparent from the above description, according to the present invention, whether or not a job can be executed is determined before sending a job from the outside. By doing so, network traffic can be reduced.

Further, by performing user authentication before sending a job, it is possible to prevent an increase in traffic due to unnecessary job issuance.

[Brief description of the drawings]

FIG. 1 shows a multifunctional peripheral device (M) showing one embodiment of the present invention.
FIG. 3 is a diagram showing a configuration of FP).

FIG. 2 is a diagram showing a system configuration showing an embodiment of the present invention.

FIG. 3 is a diagram illustrating a hardware configuration of a controller of the MFP illustrated in FIG. 1;

FIG. 4 is a diagram illustrating a software configuration of a controller of the MFP illustrated in FIG. 1;

FIG. 5 is a diagram illustrating a software configuration of a controller of the MFP illustrated in FIG. 1;

FIG. 6 is a diagram illustrating a software configuration of a controller of the MFP illustrated in FIG. 1;

FIG. 7 is a diagram illustrating an attribute table of a Supervisor 410 illustrated in FIG. 4;

8 is a diagram illustrating the meaning of an attribute ID and a type ID in the attribute table of FIG. 7;

FIG. 9 is a diagram showing a subaddress: service ID correspondence table.

FIG. 10 is a diagram illustrating the meaning of a connection type ID in FIG. 9;

FIG. 11 is a diagram showing a subaddress: task type correspondence table.

FIG. 12 is a diagram illustrating the meaning of a task type ID in FIG. 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 security levels.

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 illustrating an attribute table of a print manager.

FIG. 19 is a diagram showing the meaning of an attribute ID and a type ID in the attribute table shown in FIG.

FIG. 20 is a diagram illustrating a job table.

FIG. 21 is a diagram illustrating a job request table.

FIG. 22 is a diagram illustrating an attribute table of a scan job manager.

FIG. 23 is a diagram showing the meaning of an attribute ID and a type ID in the attribute table shown in FIG.

FIG. 24 is a diagram illustrating an attribute table of a copy job manager.

FIG. 25 is a diagram showing the meaning of an attribute ID and a type ID in the attribute table shown in FIG.

FIG. 26 is a diagram illustrating an attribute table of a font manager.

FIG. 27 is a diagram showing the meaning of an attribute ID and a type ID in the attribute table shown in FIG. 26.

FIG. 28 is a diagram showing a font table.

FIG. 29 is a diagram showing an attribute table of a form overlay manager.

30 is a diagram illustrating the meaning of an attribute ID and a type ID in the attribute table illustrated in FIG. 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 the meaning of an attribute ID and a type ID in the attribute table shown in FIG. 32.

FIG. 34 is a diagram showing a log table.

FIG. 35 is a diagram showing the contents of log data.

FIG. 36 is a diagram showing a log format table.

FIG. 37 is a diagram illustrating an attribute table of a color profile manager.

38 is a diagram illustrating the meaning of an attribute ID and a type ID in the attribute table illustrated in FIG. 37.

FIG. 39 is a diagram showing a color profile table.

FIG. 40 is a diagram illustrating an attribute table of the printer controller.

FIG. 41 is a diagram showing the meanings of an attribute ID and a type ID in the attribute table shown in FIG. 40.

FIG. 42 is a diagram showing a job queue table.

FIG. 43 is a diagram showing the status of FIG. 42.

FIG. 44 is a diagram illustrating an attribute table of the scanner controller.

FIG. 45 is a diagram illustrating the meanings of an attribute ID and a type ID in the attribute table illustrated in FIG. 44.

FIG. 46 is a diagram showing the structure of a command packet.

FIG. 47 is a flowchart showing processing of a command packet.

FIG. 48 is a flowchart showing access processing of an attribute table.

FIG. 49 is a flowchart of a service ID list inquiry process.

FIG. 50 is a flowchart of a sub address inquiry process.

FIG. 51 is a flowchart of a service ID inquiry process specifying a task type;

FIG. 52 is a diagram showing authentication of a service ID, a user ID, and a PWD.

FIG. 53 is a diagram showing the structure of a job.

FIG. 54 is a diagram showing the structure of a document.

FIG. 55 is a diagram showing a structure of a binder.

FIG. 56 is a flowchart of job script processing in each manager.

FIG. 57 is a diagram showing job script processing of each manager.

FIG. 58 is a diagram showing job script processing of each manager.

FIG. 59 is a diagram showing a job script process of each manager.

FIG. 60 is a diagram showing job script processing of each manager.

FIG. 61 is a diagram showing job script processing of each manager.

FIG. 62 is a diagram showing a document table.

FIG. 63 is a view showing a binder table.

FIG. 64 is a flowchart of job processing in the print job manager.

FIG. 65 is a flowchart of a job event handler process.

FIG. 66 is a flowchart of a data reception / PDL rasterizer process.

FIG. 67 is a flowchart of a printer controller process.

FIG. 68 is a flowchart of an account process.

FIG. 69 is a flowchart of job processing in a scan job manager.

FIG. 70 is a flowchart of a scanner controller process.

FIG. 71 is a flowchart of a scanner controller internal process.

FIG. 72 is a flowchart of a data transmission process.

FIG. 73 is a flowchart of job processing in the copy job manager.

FIG. 74 is a flowchart of job processing (download) in a font manager, a form overlay manager, a log manager, and a color profile manager.

FIG. 75 is a flowchart of job processing (upload) in the font manager, form overlay manager, log manager, and color profile manager.

FIG. 76 is a flowchart of job management in each manager.

FIG. 77 is a flowchart of event transmission.

FIG. 78 is a flowchart of data (script) transmission from the device.

FIG. 79 is a diagram illustrating a hardware configuration of a Client PC.

FIG. 80 is a diagram illustrating a software (control program) configuration of the Client PC.

FIG. 81 is a flowchart of a packet generation / transmission process.

FIG. 82 is a flowchart of information acquisition and automatic configuration of software (control program) on the Client side.

FIG. 83 is a flowchart of issuing a job specifying a task type.

FIG. 84 is a diagram showing the structure of an event.

FIG. 85 is a flowchart of event transmission.

FIG. 86 is a flowchart of a log process.

FIG. 87 is a flowchart of acquiring and processing billing information.

FIG. 88 is a flowchart of job issuance (print job, data download).

FIG. 89 is a flowchart of a device information check process.

FIG. 90 is a diagram showing a status check process prior to issuing a job.

FIG. 91 is a flowchart of job processing with a user management function.

FIG. 92 is a flowchart of a data transmission method determination process.

FIG. 93 is a diagram showing an account check process.

FIG. 94 is a diagram showing account check processing.

FIG. 95 is a diagram showing an error message.

FIG. 96 is a diagram showing an error message.

FIG. 97 is a diagram showing a warning message.

FIG. 98 is a diagram showing a warning message.

FIG. 99 is a diagram showing a warning message.

FIG. 100 is a diagram showing a warning message.

FIG. 101 is a flowchart of job issuance (scan job, data upload).

FIG. 102 is a flowchart of a data format determination process.

FIG. 103 is a flowchart of a data reception method determination process.

FIG. 104 is a flowchart of a data reception process.

FIG. 105 is a flowchart of issuing a copy job.

FIG. 106 is a flowchart of issuing a job management command.

FIG. 107 is a memory map of a DISK 315 of the MFP.

FIG. 108 is a memory map of DISK6009 of the Client PC.

FIG. 109 is a diagram illustrating a configuration of a Client PC.

FIG. 110 is a diagram illustrating an LBP applicable to a laser beam printer engine of an MFP.

FIG. 111 is a diagram illustrating an IJRA applicable to an inkjet printer engine of an MFP.

FIG. 112 is a diagram showing a sample display screen displayed on the display.

FIG. 113 is a diagram illustrating a sample display screen displayed on the display.

FIG. 114 is a diagram showing an account ID table.

FIG. 115 is a diagram showing a current count data table.

FIG. 116 is a diagram showing a count data format table.

FIG. 117 is a diagram showing a count restriction data table.

FIG. 118 is a diagram showing a count unit price data table.

FIG. 119 is a diagram showing a current billing data table.

FIG. 120 is a diagram showing a charging restriction data table.

FIG. 121 is a configuration diagram of a two-level job script.

FIG. 122 is a configuration diagram of a three-level job script.

FIG. 123 is a configuration diagram of a scan job script.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Takuyuki Matsuo 3-30-2 Shimomaruko, Ota-ku, Tokyo Inside Canon Inc. (72) Inventor Yasuhiko Sasaki 3-30-2 Shimomaruko, Ota-ku, Tokyo (72) Inventor Mamoru Osada 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Takashi Inoue 3-30-2 Shimomaruko, Ota-ku, Tokyo Canon Inc. (72) Inventor Mako Shimohira 3-30-2 Shimomaruko, Ota-ku, Tokyo F-term within Canon Inc.

Claims (33)

[Claims] A storage unit for storing a status of the main body; and an output unit for reading and outputting the status in response to an external request, wherein the status is expressed as at least normal, abnormal, and conditionally normal. A peripheral device characterized by the above-mentioned. 2. The peripheral device according to claim 1, wherein the peripheral device is a printer. 3. The peripheral device according to claim 2, wherein the conditionally normal is a limit on the number of output sheets of the printer. 4. The peripheral device according to claim 2, wherein the conditionally normal is the output resolution limitation of the printer. 5. The method according to claim 1, further comprising the steps of: storing a status of the main body; and reading and outputting the status in response to an external request, wherein the status is expressed as at least normal, abnormal, and conditionally normal. A method for controlling peripheral equipment. 6. A storage medium for storing a status of a main body, reading and outputting the status in response to an external request, and storing at least a program indicating the status as normal, abnormal, and conditionally normal. 7. A peripheral device capable of holding the current status of a peripheral device as information and controlling execution of a job based on the current status, when a client requests acquisition of the current status of the peripheral device. And a means for returning the current status of the peripheral device being held. 8. The peripheral device according to claim 7, wherein the status indicates a state of the device in a stepwise manner. 9. The peripheral device according to claim 8, wherein the gradual status of the peripheral device is one of “normal”, “conditionally normal”, and “abnormal”. 10. When the current status of a peripheral device is "conditionally normal" and the client requests the reason, "if the job execution is restricted and is 9. The peripheral device according to claim 8, further comprising means for returning a value of the "list to be referred to". 11. When the current status of a peripheral device is "abnormal" and a client requests the reason, a means for returning a value of "reason in case of abnormality" held in the peripheral device is provided. 9. The peripheral device according to claim 8, comprising: 12. The peripheral device according to claim 8, further comprising means for issuing a job when the current status of the peripheral device is “normal”. 13. If the current status of the peripheral device is "conditionally normal", a "list of attributes to be referred to when job execution is possible with restriction" held in the peripheral device 9. The method according to claim 8, further comprising: means for acquiring the value of the job, means for comparing the attribute value with the job content, and means for issuing the job when the job content satisfies the condition of the attribute value. Peripheral equipment. 14. If the current status of the peripheral device is "conditionally normal", a "list of attributes to be referred to when job execution is possible with a restriction" held in the peripheral device Means for obtaining the value of the attribute, means for comparing the attribute value with the job content, means for canceling the job issuance when the job content does not satisfy the condition of the attribute value, and display means for displaying the reason. 9. The peripheral device according to claim 8, comprising: 15. A means for acquiring a value of a "reason in case of abnormality" attribute held in the peripheral device when the current situation of the peripheral device is "abnormal"; The peripheral device according to claim 8, further comprising means for displaying "." 16. A peripheral device for executing a job request from an information processing device connected to a network, comprising: storage means for storing a status of a main body; A determination unit for determining whether the job can be executed in the relationship described above, and a unit for restricting job issuance from the information processing apparatus when the result of the determination by the determination unit is not executable. Equipment and devices. 17. The peripheral device according to claim 16, wherein the status indicates a state of the device in a stepwise manner. 18. The peripheral device according to claim 16, wherein the gradual statuses of the peripheral device are three types of “normal”, “conditionally normal”, and “abnormal”. 19. A method for controlling a peripheral device for executing a job request from an information processing device connected to a network, the method comprising: storing a status of a main body; A step of judging whether the job can be executed in relation to the status, and means for restricting job issuance from the information processing apparatus when the result of the judgment in the judging step is not executable. Peripheral device control method. 20. The method according to claim 19, wherein the status indicates a state of the device in a stepwise manner. 21. A peripheral device for executing a job request from an information processing device connected via a network, wherein the peripheral device performs a job request based on user information sent from the information processing device.
A peripheral device, wherein user authentication is performed prior to issuance of the job request. 22. The peripheral device according to claim 21, wherein a user identification code is used as the user information. 23. The peripheral device according to claim 21, wherein a user identification code and a user password are used as the user information. 24. The peripheral device according to claim 21, wherein the user information includes a user identification code and / or a user password and / or a service identification code indicating a type of an h service. 25. A method of controlling a peripheral device that executes a job request from an information processing device connected via a network, wherein the method is based on user information sent from the information processing device.
A method for controlling a peripheral device, comprising the step of performing user authentication prior to issuing the job request. 26. A system comprising an information processing device and a peripheral device connected via a network, wherein the information processing device transmits user information via the network prior to sending a job request. The peripheral device performs user authentication based on the user information, and regulates transmission of a job request from the information processing device according to a result of the authentication. 27. The system according to claim 26, wherein said peripheral device is a printer. 28. The system according to claim 27, wherein said printer is a physical printer and a logical printer. 29. The system according to claim 26, wherein said peripheral device is a scanner. 30. The system according to claim 26, wherein said peripheral devices are a printer and a scanner, and are capable of executing a copy job. 31. The peripheral device according to claim 26, wherein a user identification code is used as the user information. 32. The peripheral device according to claim 26, wherein a user identification code and a user password are used as the user information. 33. The peripheral device according to claim 26, wherein a user identification code and / or a user password and / or a service identification code indicating a service type are used as the user information.