JP4612768B2 - Peripheral device control system, control method thereof, and medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a technique for issuing a job from an external device to peripheral devices such as a printer, a scanner, a copier, and a FAX connected to a network.
[0002]
[Prior art]
Conventionally, in a peripheral device such as a printer, various operations can be specified by specifying various modes in a job submission start command.
By the way, the user can designate a desired mode in the job submission start command because the job issuing software previously recognizes and displays what mode the peripheral device can process.
[0003]
As described above, when the job issuing software recognizes in advance what mode the peripheral device can process, generally, the peripheral device can recognize and display the mode that can be processed by the peripheral device. is doing. This type of recognition / display method based on mode storage is similarly adopted when a job is issued from an external device via a network. Conventionally, when a job is issued from an external device, peripheral devices can process the job. The mode was stored in the external device.
[0004]
[Problems to be solved by the invention]
However, in recent years, the performance of peripheral devices has improved rapidly, and many functions have been added. When a peripheral device with added functions in this way is connected to a network, it is possible to store functions (modes) that can be processed by the peripheral device in an external device on the network as in the past. Is troublesome, and it is necessary to provide an extra memory in the external device, resulting in high costs.
[0005]
The present invention has been made in view of such problems, and the problem is to enable a job to be issued from an external device to a peripheral device easily and inexpensively while effectively using the memory resources of the system. There is.
[0006]
[Means for Solving the Problems]
In order to solve the above problems, the present invention Peripheral device control system Peripheral device control system for controlling a peripheral device by transmitting a control command from the external device to the peripheral device via a network Because The peripheral device is , The peripheral device Attribute list including supported attributes and information indicating whether the supported attributes are attributes whose attribute values can be set from software of the external device when a job is submitted Storing means for storing the external device, in front Stored by the storage means The attribute list from the peripheral device Obtained via the network Whether each attribute included in the attribute list acquired by the first acquisition unit and the attribute list acquired by the first acquisition unit is an attribute whose attribute value can be set by software of the external device when a job is submitted A determination unit configured to determine the attribute value that can be set by the software of the external apparatus when the job is submitted by the determination unit from the peripheral device; A second acquisition unit to acquire, and a setting screen for the attribute value reflecting the settable attribute value acquired by the second acquisition unit. Display means for displaying; in front By the display means Table Indicated Generate jobs according to the settings entered via the settings screen Do Generation Means and said Generation By means Generation Was job Transmitting means for transmitting to the peripheral device via the network; , Have It is characterized by .
[0007]
In addition, the present invention For controlling peripheral device control system according to the present invention A control method for a peripheral device control system for controlling a peripheral device by transmitting a control command from the external device to the peripheral device via a network Because The peripheral device In The peripheral device Attribute list including supported attributes and information indicating whether the supported attributes are attributes whose attribute values can be set from software of the external device when a job is submitted Memory to remember Step and The external device In The memory By step Remembered The attribute list from the peripheral device Obtained via the network And whether each attribute included in the attribute list acquired in the first acquisition step is an attribute whose attribute value can be set by software of the external device when a job is submitted A determination step for determining, and attribute values that can be set for the attribute from the peripheral device when the attribute is determined to be an attribute value that can be set by software of the external device at the time of job submission in the determination step A second acquisition step to be acquired, and a setting screen for the attribute value reflecting the settable attribute value acquired by the second acquisition step. Display to display Step And the display Step Displayed by Generate jobs according to the settings entered via the settings screen Do Generation step And said Generation step By Generation Was job Send to the peripheral device via the network Step When , Have It is characterized by .
[0009]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0010]
[First Embodiment]
FIG. 1 is a system configuration diagram of a peripheral device control system to which the present invention is applied.
[0011]
The peripheral device 101 is a device that performs job processing such as printing, scanning, copying, and FAX transmission / reception. PCs 102 to 104 indicate PCs (personal computers) connected to the peripheral device 101 via the network 105. As the connection by the network 105, connection by LAN or WAN, connection of IEEE1284 / 1394, USB or the like can be considered. Further, the workstation may be connected to the peripheral device 101, or may be other peripheral devices or other devices.
[0012]
Control software called a controller operates in the peripheral device 101, and processes job processing such as printing, scanning, copying, and FAX transmission / reception requested from the job issuing software, and inquiry of attribute information of the peripheral device 101. The job issuing software is software that operates in the peripheral device 101 or the PCs 102 to 104, and requests the controller in the peripheral device 101 to perform job processing such as printing, scanning, copying, or FAX transmission / reception, or the peripheral device. 101 attribute information is queried.
[0013]
FIG. 2 is a block diagram illustrating a schematic configuration of hardware of the peripheral device 101.
[0014]
In the peripheral device 101, a CPU 201, a RAM 202, an LCD 203, a keyboard 204, a ROM 205, a communication interface 206, a scanner engine 207, a printer engine 208, a FAX board 209, and a DISK 210 are connected via a system bus 211. Are connected to each other.
The CPU 201 is a main body that executes a controller or job issuing software, and each unit configuring the peripheral device 101 is controlled by the CPU 201 unless otherwise specified. A program of the controller or job issuing software is stored in the ROM 205 or the DISK 210, read out to the RAM 202 as necessary, and executed by the CPU 201. These programs display information through the LCD 203, receive a user instruction from the keyboard 204, and perform processing such as communication with the outside through a communication interface.
[0015]
In the ROM 205 and DISK 210, in addition to the controller and job issuing software program, attribute information indicating the function and status of the peripheral device 101, attribute information indicating the function and status of the job processed by the peripheral device 101, and processing target. Stores job data.
[0016]
The DISK 210 also stores a file for saving job contents. The communication interface 206 may be, for example, an Ethernet interface, an IEEE 1284 interface, or another communication interface. A scanner engine 207, a printer engine 208, and a FAX board 209 are controlled by a controller, and perform scan job processing, print job processing, and FAX transmission / reception processing.
[0017]
The peripheral device 101 having the above configuration enables print job processing by the printer engine 208. The scanner engine 207 and the printer engine 208 enable copy job processing. Further, the scanner engine 207, the printer engine 208, and the FAX board 209 enable FAX reception job processing and FAX transmission job processing.
[0018]
FIG. 3 is a block diagram illustrating a schematic configuration of hardware of the PCs 102 to 104.
[0019]
In the PCs 102 to 104, a CPU 301, a RAM 302, a CRT 303, a keyboard 304, a communication interface 305, a DISK 306, a ROM 307, and a pointing device 308 are connected to each other via a system bus 309.
[0020]
The CPU 301 is an operating system (hereinafter referred to as an OS) that controls the PCs 102 to 104 or a main body that executes job issuing software. The units constituting the PCs 102 to 104 are controlled by the CPU 301 unless otherwise specified. The OS or job issue software program is stored in the ROM 307 or the DISK 306, read into the RAM 302 as necessary, and executed by the CPU 301.
[0021]
These programs display information through the CRT 303, receive a user instruction from the keyboard 304 and the pointing device 308, and perform processing such as communicating with the outside through the communication interface 305.
[0022]
FIG. 4 shows an example of a command group for instructing job processing. This command group is generated by the processing flow of FIGS. 14 and 15 and is sent from the job issuing software to the controller in the peripheral device 101.
[0023]
A command group for instructing job processing includes a job submission start command 401, a job attribute setting command 402, a job data transmission command 403, and a job submission completion command 404.
[0024]
The job submission start command 401 is a command for notifying the controller of the start of job submission, and includes a mode 405 and additional information 406 corresponding to the mode as parameters. Upon receiving the job submission start command 401, the controller starts preparations for performing job processing.
[0025]
A job attribute setting command 402 is a command for setting an attribute representing a job function or status. The attributes include information such as job name, job type, data format, paper selection, and the like. With this command, a plurality of attributes can be set continuously.
[0026]
A job data transmission command 403 is a command for transmitting data to be subjected to job processing such as image data. However, depending on the contents of the job, the data to be processed may not be required. In this case, this command may be omitted.
[0027]
The job submission completion command 404 is a command for indicating that all command groups instructing job processing have been sent. A series of commands from the job submission start command 401 to the job submission completion command 404 is interpreted as an instruction relating to one job process.
[0028]
FIG. 5 shows a processing flow of the attribute information access command. An access command to the attribute information is issued by the job issuing software, and this processing flow is processed by the controller in the peripheral device 101.
[0029]
In step S501, the received command and its parameters are analyzed. Steps S502 to S506 are processing when it is determined that the received command is an attribute acquisition command as a result of the analysis, and the process proceeds to step S503.
[0030]
In step S503, it is checked whether or not the attribute specified by the attribute acquisition command can be acquired. If the attribute can be acquired, the process proceeds to step S504, and if it cannot be acquired, the process proceeds to step S506. In step S504, the value of the attribute held in the peripheral device 101 is acquired, and the process proceeds to step S505.
[0031]
In step S505, the attribute value obtained in step S504 is set in the parameter of the reply command, a reply command for the attribute acquisition command is transmitted to the job issuing software, and the process ends. In step S506, a process for notifying the job issuing software that the attribute acquisition has failed is performed, and the process ends.
[0032]
Steps S507 to S510 and S506 are processing when it is determined as a result of analysis that the received command is an attribute acquisition command, and the process proceeds to step S508. In step S508, it is checked whether or not the attribute specified by the attribute value change command can be changed. If it can be changed, the process proceeds to step S509, and if it cannot be changed, the process proceeds to step S506.
[0033]
In step S509, the designated attribute is changed to the designated attribute value in accordance with the designated command parameter, and the process advances to step S510. In step S510, a process for notifying the job issuing software that the attribute value has been successfully changed is performed, and the process ends. In step S506, processing for notifying the job issuing software that the change of the attribute value has failed is performed, and the process ends.
[0034]
If it is determined in step 507 that the received command is not an attribute change command, that is, if it is determined that the received command is neither an attribute acquisition command nor an attribute change command, processing corresponding to the command is performed. (Step S511), the process ends.
[0035]
FIG. 6 shows an example of a screen for setting the mode and additional information of the job submission start command. This setting screen is displayed when the job issuing software sends a job submission start command, and is used in the processing flow shown in FIGS.
[0036]
This setting screen is displayed on the LCD 203 of the peripheral device 101 or the CRT 303 of the PCs 102 to 104. This is done through the pointing device 308.
[0037]
A setting screen title 601 represents a brief description of the setting screen, and indicates that the setting screen is used for “setting a job submission start command”. List boxes 610, 612, and 614 display a list of modes that can be specified when a job submission start command is sent to the peripheral device 101. The modes listed in these list boxes are the “job submission start command mode (normal / interrupt)” attribute shown in FIG. 8, the “job submission start command mode (job storage)” attribute shown in FIG. One-to-one correspondence to those listed in the “job submission start command mode (execution guarantee)” attribute.
[0038]
The list box 616 displays a list of “storage file storage locations”. The contents listed in the list box correspond one-to-one with those listed in the “list of“ storage file storage locations ”” attributes shown in FIG.
[0039]
When the setting screen is first displayed, the default storage location obtained by the “default“ storage file storage location ”attribute in FIG. 13 is highlighted and is in a selected state. The list box 616 is effective when a mode with job storage is selected as the mode of the “job submission start command”, and the selected content is sent as additional information of the job submission start command.
[0040]
Inverted displays 611, 613, 615, and 617 indicate the currently selected “job input start command mode” or “storage file storage location”, and in FIG. 6, “normal execution”, “job storage”, and “execution”, respectively. “No guarantee” and “save destination 8” are selected.
[0041]
The user can select a desired setting value from the list boxes 610, 612, 614, and 616. An OK button 602 is a button for determining the mode and additional information of the job submission start command to values shown in reverse display. A cancel button 603 is a button for canceling the setting of the job submission start command.
[0042]
FIG. 7 shows an example (other configuration example) of a screen for setting the mode and additional information of the job submission start command. FIG. 6 shows the mode of the job submission start command for each function, while FIG. 7 shows the mode by a combination of functions.
[0043]
This setting screen is displayed when the job issuing software sends a job submission start command, and is used in the processing flows shown in FIGS. This setting screen is displayed on the LCD 203 of the peripheral device 101 or the CRT 303 of the PCs 102 to 104, and user input (selection of list box items or button pressing) is performed by the keyboard 204 of the peripheral device 101 or the keyboard 304 of the PCs 102 to 104. This is done through the pointing device 308.
[0044]
A setting screen title 701 represents a brief description of the setting screen, and indicates that the setting screen is used for “setting a job submission start command”. The list box 710 displays a list of modes that can be specified when a job submission start command is sent to the peripheral device 11. The modes listed in the list box 710 correspond one-to-one with those listed in the “job submission start command mode (mixed)” attribute in FIG.
[0045]
The list box 712 displays a list of “storage file storage locations”. The contents listed in the list box correspond one-to-one with those listed in the “list of“ storage file storage locations ”” attributes shown in FIG. When the setting screen is first displayed, the default storage location obtained by the “default“ storage file storage location ”attribute in FIG. 13 is highlighted and is in a selected state.
[0046]
Note that the list box 712 is effective when a mode with job storage is selected as the mode of the “job submission start command”, and the selection content here is sent as additional information of the job submission start command.
[0047]
Inverted displays 711 and 713 indicate the currently selected “job submission start command mode” and “storage file storage location”. In this figure, “normal execution + guarantee + save” and “save destination 8” respectively. Is selected.
[0048]
The user can select a desired setting value from the list boxes 710 and 712. An OK button 702 is a button for determining the mode and additional information of the job submission start command to values shown in reverse display. A cancel button 703 is a button for canceling the setting of the job submission start command.
[0049]
FIG. 8 shows an example of the “mode (normal / interrupt) that can be specified in the job submission start command” attribute held by the peripheral device 11, which is stored in the ROM 205 or DISK 210 of the peripheral device 101. This attribute lists modes that can be specified when the job issuing software submits a job submission start command to the controller of the peripheral device 101. Here, modes related to job interrupt execution are listed, but other attribute values may be listed in addition to the attribute values shown in FIG.
[0050]
The attribute value “normal execution” 801 indicates that jobs are executed in the order of job submission as usual. This is because when another job is being executed in the peripheral device 101 when a job submission start command is input or a job waiting for execution is in the queue, the job submission start command is executed after the processing of those jobs is completed. Indicates to start the indicated job.
[0051]
The attribute value “interrupt execution” 802 indicates that the job is executed by interruption. This is because when another job is being executed in the peripheral device 101 when a job input start command is input or a job waiting for execution is on the queue, the processing of those jobs is temporarily stopped and the job input Indicates that the job specified by the start command is started preferentially.
[0052]
FIG. 9 shows an example of a “mode that can be specified in a job submission start command (job storage)” attribute held by the peripheral device 101, and is stored in the ROM 205 or DISK 210 of the peripheral device 101. This attribute lists modes that can be specified when the job issuing software submits a job submission start command to the controller of the peripheral device 101. Here, modes related to job storage are listed, but other attribute values may be listed in addition to the attribute values shown in FIG.
[0053]
An attribute value “no job storage” 901 indicates that the job is normally executed. This indicates that a series of commands instructing job processing is not saved as a file in the peripheral device 101.
[0054]
The attribute value “with job storage” 902 indicates that the job is stored and executed. This indicates that a series of commands instructing job processing is saved as a file in the peripheral device 101 and job processing is also executed.
[0055]
An attribute value “job save only” 903 indicates that the job is saved but not executed. This means that a series of commands instructing job processing is only stored as a file in the peripheral device 101, and job processing is not performed.
[0056]
FIG. 10 shows an example of a “mode (execution guaranteed) attribute that can be specified in a job submission start command” attribute held by the peripheral device 101 and is stored in the ROM 205 or DISK 210 of the peripheral device 101. This attribute lists modes that can be specified when the job issuing software submits a job submission start command to the controller of the peripheral device 11. Here, modes related to job execution guarantee are listed, but other attribute values may be listed in addition to the attribute values shown in FIG.
[0057]
The attribute value “no execution guarantee” 1001 indicates that the job is normally executed. This is because, after a series of commands instructing job processing is sent to the peripheral device 11, if the peripheral device 101 cannot process the job due to some trouble (power supply to the peripheral device 101) or the like, Indicates that execution of the job is not guaranteed.
[0058]
The attribute value “with execution guarantee” 1002 indicates that the execution of the job is guaranteed. This is because, after a series of commands instructing job processing is sent to the peripheral device 101, if the peripheral device 101 cannot process the job due to some trouble (power supply to the peripheral device 101) or the like, Indicates that the execution of the job is guaranteed.
[0059]
FIG. 11 shows an example of the “mode (mixed) that can be specified for job input start command” attribute held by the peripheral device 101, and is stored in the ROM 205 or DISK 210 of the peripheral device 101. This attribute lists modes that can be specified when the job issuing software submits a job submission start command to the controller of the peripheral device 101. Here, combinations of modes relating to job interrupt execution, job storage, and job execution guarantee are listed, but other attribute values may be listed in addition to the attribute values shown in FIG.
[0060]
The attribute value “normal execution” 1101 indicates that jobs are executed in the order of job submission as usual. This is synonymous with the combination of “normal execution” 801 in FIG. 8, “no job storage” 901 in FIG. 9, and “no execution guarantee” 1001 in FIG.
[0061]
The attribute value “interrupt execution” 1102 indicates that the job is executed by interruption. This is synonymous with the designation of “interrupt execution” 802 in FIG. 8, “no job storage” 901 in FIG. 9, and “no execution guarantee” 1001 in FIG.
[0062]
The attribute value “normal execution + save” 1103 indicates that the job is saved and executed. This is synonymous with the designation of “normal execution” 801 in FIG. 8, “job storage” 902 in FIG. 9 and “no execution guarantee” 1001 in FIG. An attribute value “interrupt execution + save” 1104 indicates that the job is saved and interrupted. This is synonymous with the designation of “interrupt execution” 802 in FIG. 8, “job storage” 902 in FIG. 9, and “no execution guarantee” 1001 in FIG.
[0063]
The attribute value “save only” 1105 indicates that the job is saved but not executed. This is synonymous with a combination of “normal execution” 801 in FIG. 8, “job storage only” 903 in FIG. 9, and “no execution guarantee” 1001 in FIG.
[0064]
The attribute value “normal execution + guarantee” 1106 indicates that the execution of the job is guaranteed. This is synonymous with the combination of “normal execution” 801 in FIG. 8, “no job storage” 901 in FIG. 9, and “execution guaranteed” 1002 in FIG.
[0065]
The attribute value “normal execution + guarantee + save” 1107 indicates that the job is saved and the execution is guaranteed. This is synonymous with the combination of “normal execution” 801 in FIG. 8, “job storage” 902 in FIG. 9, and “execution guaranteed” 1002 in FIG.
[0066]
FIG. 12 shows an example of the “list of“ storage file storage locations ”” that the peripheral device 101 holds, and is stored in the ROM 205 or DISK 210 of the peripheral device 101.
[0067]
The attribute values “save destination 1” 1201 to “save destination 9” 1209 indicate “save file storage locations” that can be specified. When a mode that involves saving a job is specified in the job submission start command, one of the “storage file storage locations” listed in this attribute must be specified as additional information. Although the attribute value is indicated by a name such as “save destination n” here, the attribute value may be indicated by other information that can be uniquely identified, such as an identifier indicating a storage location or a handle value.
[0068]
FIG. 13 shows an example of a “default“ storage file storage location ”” attribute held by the peripheral device 101, which is stored in the ROM 205 or DISK 210 of the peripheral device 101.
[0069]
The attribute value “save destination 8” 1301 is an example of a default “save file storage location”. If the job submission start command specifies a mode that involves saving the job, it is necessary to specify additional information for the job submission start command. If this specification is not specified, the value indicated by this attribute is the additional information. Adopted as
[0070]
Although the attribute value is indicated by a name such as “save destination n” here, the attribute value may be indicated by other information that can be uniquely identified, such as an identifier indicating a storage location or a handle value.
[0071]
14 and 15 show a processing flow of job input. Job submission is performed from the job issuing software to the controller in the peripheral device 101, and this processing flow is processed by the job issuing software.
[0072]
In step S1401, a mode that can be specified in the job submission start command is acquired, and the process advances to step S1402. The job issuing software sends an attribute acquisition command to the controller of the peripheral device 101, and the controller returns the specified attribute value. At this time, the processing flow of the attribute information access command shown in FIG.
[0073]
The attributes to be acquired here are the “mode that can be specified in the job submission start command (normal / interrupt)” attribute in FIG. 8 and the “mode that can be specified in the job submission start command (job storage)” attribute in FIG. FIG. 10 shows a “mode that can be specified for job submission start command (execution guarantee)” attribute and a “mode that can be specified for job submission start command (mixed)” attribute in FIG.
[0074]
In step S1402, the mode obtained with the “mode that can be specified for job submission start command (job storage)” attribute of FIG. 9 or the “mode that can be specified for job submission start command (mixed)” attribute of FIG. It is determined whether or not a mode that includes saving of a job is included in the specified mode. As a result, if it is included, the process proceeds to step S1403. If it is not included, the process proceeds to step S1406.
[0075]
In step S1403, “storage file storage location” that can be specified as additional information is acquired, and the process advances to step S1404. The job issuing software sends an attribute acquisition command to the controller of the peripheral device 101, and the controller returns the specified attribute value. At this time, the processing flow of the attribute information access command shown in FIG. The attribute to be acquired here is the “list of“ storage file storage locations ”” attributes shown in FIG.
[0076]
In step S1404, the default “storage file storage location” is acquired, and the process advances to step S1405. The job issuing software sends an attribute acquisition command to the controller of the peripheral device 101, and the controller returns the specified attribute value. At this time, the controller of the peripheral device 101 executes the attribute information access command processing flow shown in FIG. The attribute to be acquired here is the “default“ storage file storage location ”” attribute in FIG. 13.
[0077]
In step S1405, the “storage file storage location” setting process is performed, and the process advances to step S1406. Here, in the list box 616 of the job submission start command setting screen shown in FIG. 6 or the list box 712 of the job submission start command setting screen shown in FIG. A list of “locations” is displayed, and the default “storage file storage location” obtained in step S1405 is highlighted in advance.
[0078]
In step S1406, a mode setting process that can be specified in the job submission start command is performed, and the process advances to step S1407. Here, the mode obtained in step S1401 is added to the list boxes 610, 612, and 614 of the job submission start command setting screen shown in FIG. 6 or the list box 710 of the job submission start command setting screen shown in FIG. List.
[0079]
In step S1407, the job submission start command setting screen shown in FIG. 6 or FIG. 7 is presented to the user, the mode and additional information necessary for the job submission start command are selected, and the process proceeds to step S1408.
[0080]
In step S1408, a job submission start command is sent to the controller of the peripheral device 101 together with the selected mode and additional information.
The processing from step S1409 to step S1412 is repeated until the setting of attributes necessary for the job processing desired by the user is completed. That is, in step S1410, job attribute parameters corresponding to job processing are set. In step S1411, a job attribute setting command is transmitted to the controller of the peripheral device 101 in order to set the job attribute parameter set in step S1410.
[0081]
In step S1413, data to be subjected to job processing, such as image data created by an application, is transmitted to the controller of the peripheral device 11 by a job data transmission command. In step S1414, a job submission completion notification command indicating completion of transmission of the job submission command is transmitted, and the process ends. With this series of job input processes, the series of job processing commands shown in FIG. 4 is transmitted to the controller of the peripheral device 101.
[0082]
16 to 18 show the process flow of job reception. The controller in the peripheral device 101 receives a series of job processing commands transmitted from the job issuing software. This processing flow is processed by the controller in the peripheral device 101.
[0083]
In step S1601, the mode specified in the job submission start command is determined. However, when the job submission start command received as the job start instruction is received, this determination is not performed, and after the mode specified in the job submission start command is stored in step S1701 of FIG. Is done.
[0084]
If the saved mode involves saving of the job, the process proceeds to step S1602, and if not, the process proceeds to step S1603. In step S1602, the received command is saved as a file, and the process advances to step S1603. In step S1603, the received command and its parameters are analyzed.
[0085]
Step S1604 and subsequent steps are processing when it is determined as a result of analysis that the received command is a job submission start command, and the processing is shown in FIG. In FIG. 17, processing unique to the present invention is described, and it is assumed that other processing necessary in accordance with the job input start command has been completed at the time of step S <b> 1604.
[0086]
Step S1605 and subsequent steps are processing when it is determined as a result of analysis that the received command is a job submission completion command, and the processing is shown in FIG. In FIG. 18, processing unique to the present invention is described, and it is assumed that other processing necessary for the job submission completion command has been completed at the time of step S <b> 1605.
[0087]
Step S1606 is processing when it is determined as a result of analysis that the received command is another command. The mode of the job submission start command stored in step S1701 in FIG. 17 is determined, and only job storage is shown. If it is not the mode, the process proceeds to step S1607, and if so, the process ends. In step S1607, processing corresponding to the designated command is performed, and the process ends.
[0088]
FIG. 17 shows the continuation of the processing when it is determined in step S1603 of FIG. 16 that the received command is a job submission start command. This processing flow is processed by the controller in the peripheral device 101.
[0089]
In step S1701, the mode specified in the job submission start command is saved. The stored mode is used for determination in step S1601, step S1606 in FIG. 16, and step S1801 in FIG. In step S1702, the specified mode is analyzed.
[0090]
Steps S1703 and S1704 are processes performed when it is determined that the mode is accompanied by an interrupt as a result of analysis, and the process proceeds to step S1704. In step S1704, the processing of the job that conflicts with the job processing instructed by the job submission start command is temporarily stopped and terminated.
[0091]
Steps S <b> 1705 to S <b> 1709 are processing when it is determined as a result of the analysis that the mode involves job storage, and the process proceeds to step S <b> 1706. In step S1706, it is determined whether a storage file storage location is specified. If the storage location is specified, the process proceeds to step S1707, and if not, the process proceeds to step S1708. In step S1707, a job storage file is generated in the designated storage location, and the process advances to step S1709.
[0092]
In step S1708, a job storage file is generated in the storage location obtained by referring to the “default“ storage file storage location ”attribute held by the peripheral device 101, and the process advances to step S1709. In step S1709, a job submission start command is recorded in the generated job storage file, and the process ends.
[0093]
Steps S1711, S1712, and S1709 are processes performed when it is determined as a result of the analysis that the mode is accompanied by an execution guarantee, and the process proceeds to step S1712. In step S1712, a job storage file is generated in a storage location internally defined by the peripheral device 101, and the process advances to step S1709. In step S1709, a job submission start command is recorded in the generated job storage file, and the process ends.
[0094]
If it is determined in step S1711 that the mode is not the execution guarantee mode, the process advances to step S1713 to determine whether there is any other mode specified by the job submission start command. As a result, if there is no other designated mode, the process ends. If there is, the process corresponding to the mode is performed in step S1714, and the process ends.
[0095]
Note that the files generated in steps S1707, S1708, and S1712 are stored in the DISK 210 in the peripheral device 101.
[0096]
FIG. 18 shows the continuation of the processing when it is determined in step S1603 of FIG. 16 that the received command is a job submission completion command. This processing flow is processed by the controller in the peripheral device 101.
[0097]
In step S1801, the process branches according to the mode of the job submission start command saved in step S1701 in FIG.
[0098]
If the mode is accompanied by an interrupt (step S1802), the process proceeds to step S1803. In step S1803, execution of the job whose processing is temporarily stopped by interruption of the job is resumed, and the processing ends.
[0099]
If the mode is accompanied by job storage (step S1804), the process ends.
[0100]
If the mode is accompanied by an execution guarantee (step S1805), the process proceeds to step S1806. In step S1806, the job storage file generated in step S1712 of FIG. 17 is deleted, and the process ends.
[0101]
If it is determined in step S1805 that the mode is not accompanied by execution guarantee, the process advances to step S1807 to determine whether there is any other mode specified by the job submission start command. As a result, if there is no other designated mode, the process ends. If there is, the process corresponding to the mode is performed in step S1808, and the process ends.
[0102]
FIG. 19 shows the processing flow of an execution guaranteed job. This processing flow is processed by the controller in the peripheral device 101. When the peripheral device 101 is started, it is determined whether or not a job for which execution guarantee is specified is left unexecuted. If there is, process to execute the job is performed.
[0103]
The processing from step S1901 to step S19304 is repeated until there is no unexecuted execution guarantee job stored in the storage location internally defined by the peripheral device 101. In step S1902, job processing is performed in accordance with a series of commands in the job storage file. When job processing is completed, the process advances to step S1903. This saved file is generated in step S1712 of FIG. 17 and is stored in the DISK 210 of the peripheral device 101.
[0104]
In step S1903, the job storage file is deleted. Through the loop processing from step S1901 to step S1904, all unexecuted execution guaranteed jobs are executed and deleted, and upon completion, this processing flow ends.
[0105]
[Second Embodiment]
FIG. 20 shows a configuration example of a job processed by the peripheral device 101 shown in FIGS. A job processed by the peripheral device 101 includes an attribute list 2001 that represents the job function and status, and job data 2002 that represents data to be processed by the job. The job data 2002 may be omitted depending on the job type.
[0106]
An attribute list 2001 is a list of attribute names and attribute values as indicated by 2011, 2012, 2021 to 2031 and indicates the status of a job submitted by the driver software (job issue software). The attribute list 2001 may have a configuration in which an attribute identifier is specified in the column 2011 instead of the attribute name.
[0107]
The attributes listed in the attribute list 2001 are the same as those listed in the “attribute list supported by job” in FIG. Job data 2002 indicates data to be subjected to job processing such as an image. A column 2011 shows attribute names. A column 2012 indicates attribute values of attributes indicated by the attribute names in the column 2011.
[0108]
An attribute 2021 indicates an identifier of the input job. The attribute value 2022 indicates that the “job identifier” is “1234”. An attribute 2023 indicates the name of the submitted job. The attribute value 2024 indicates that the “job name” is “test print”.
[0109]
An attribute 2025 indicates the job type of the input job such as a print job or a copy job. The attribute 2026 indicates that the “job type” is “print job”. An attribute 2027 indicates a job password requested at the start of the job processing. The attribute value 2028 indicates that the “job password” is “ABCD1234”.
[0110]
An attribute 2029 indicates paper selection used in the job. The attribute value 2030 indicates that “paper selection” is “A4”. An attribute 2031 indicates whether the print side is only the front side, the double side, or the back side in the job. The attribute value 2032 indicates that “printing surface” is “front”.
[0111]
In the present embodiment, the meaning of each attribute and attribute name or attribute identifier and each attribute value as described above is known both in the peripheral device 101 of FIG. 1 and in the driver software.
[0112]
FIG. 21 shows an example of an “attribute list supported by a job”, which is a list of job attributes held by the peripheral device 101, and is stored in the ROM 205 or DISK 210 of the peripheral device 101. However, the attributes listed in the “attribute list supported by job” may be other attributes than those shown in FIG.
[0113]
The “attribute list supported by a job” illustrated in FIG. 21 lists all the attributes held by the job processed by the peripheral device 101. Further, in the “attribute list supported by job”, the attribute name (column 2110) and whether or not the driver software can set an attribute value at the time of job submission (column 2111). Whether the attribute value can be changed for the already submitted job (column 2112), whether the attribute value can be acquired for the submitted job (column 2113), Those that are possible are indicated by TRUE, and those that are not possible are indicated by FA1SE.
[0114]
A row 2101 indicates the support status of the “job identifier” attribute. The “job identifier” attribute cannot be set, cannot be changed, or can be acquired. A row 2102 indicates the support status of the “job name” attribute. The “job name” attribute can be set, cannot be changed, and can be acquired.
[0115]
A row 2103 indicates the support status of the “job type” attribute. The “job type” attribute can be set, cannot be changed, and can be acquired. A row 2104 indicates the support status of the “job password” attribute. The “job password” attribute can be set, cannot be changed, and cannot be acquired.
[0116]
A row 2105 indicates the support status of the “paper selection” attribute. The “paper selection” attribute can be set, cannot be changed, and can be acquired. A row 2106 indicates the support status of the “duplex printing” attribute. The “duplex printing” attribute can be set, changed, and acquired. A row 2107 indicates the support status of the “deletable during job execution” attribute. The “deletable during job execution” attribute can be set, cannot be changed, and can be acquired.
[0117]
FIG. 22 shows a “list of attributes that can be specified for the job deletion mode” stored in the peripheral device 101, and is stored in the ROM 205 or DISK 210 of the peripheral device 101. The “list of attribute values that can be specified for job deletion mode” in FIG. 22 includes attribute values that can be specified by the driver software as values of the “job deletion mode” attribute held by the job processed by the peripheral device 101. Enumerate. However, the attribute values listed in the “list of attribute values that can be specified for job deletion mode” may be attributes other than the attributes shown in FIG.
[0118]
In the original embodiment, the “job deletion mode” attribute is listed in the “job support attribute list” of FIG. 21 held by the peripheral device 101, and the setting value of the “job deletion mode” attribute It is assumed that other attributes required according to the above are listed in the “attribute list supported by job” in FIG.
[0119]
The “job deletion mode” attribute indicates the setting of job deletion conditions submitted by the driver software to the peripheral device 101. Setting the “job deletion mode” attribute sets the job to be submitted. Deletion can be controlled.
[0120]
In FIG. 22, an attribute value “designated by absolute time” 2201 indicates that the deletion time after job submission is designated by absolute time, and indicates that the job is to be deleted when the deletion time is reached. Is also included.
[0121]
The attribute value “designated by relative time” 2202 indicates that the deletion time after the job is input is designated by relative time, and indicates that the job is deleted when the deletion time is reached, and the attribute value includes the designated deletion time.
[0122]
FIG. 23 shows a flow of processing in which the driver software inquires the peripheral device 101 about the attribute information of the peripheral device 101. In step S2301, the peripheral device 101 is requested to acquire an “attribute list supported by the job”, and the attribute list is acquired.
[0123]
In step S2302, it is checked whether or not the “attribute list supported by job” acquired in step S2301 includes an attribute A indicating a function required by the driver software. If the attribute A is included, the process proceeds to step S2303. On the other hand, if the attribute A is not included, the process proceeds to step S2305.
[0124]
In step S2303, regarding the attribute A in the attribute list acquired in step S2301, it is checked from the attribute list whether the attribute can be set by the driver software when the job is submitted. If the attribute A can be set, the process advances to step S2304. On the other hand, if the attribute A cannot be set, the process proceeds to step S2305.
[0125]
In step S2304, a list of attribute values that can be set in the attribute A is acquired from the peripheral device 101, and the process advances to step S2305. In step S2305, it is checked whether or not the attribute A is an attribute that can be acquired by the driver software. If it is an acquirable attribute, the process proceeds to step S2306. On the other hand, if the attribute cannot be acquired, the process ends. In step S2306, an attribute A value acquisition request is issued to the peripheral device 101, the attribute A value is acquired, and the process ends.
[0126]
Through the above processing, the driver software can obtain information on what attribute value the job processed by the peripheral device 101 holds and what attribute value can be designated for each layer. In addition, it is possible to obtain what value each attribute has.
[0127]
FIG. 24 shows an example of a setting screen for the “job deletion mode” attribute. This setting screen is a screen on which the user sets a “job deletion mode” attribute when a job is submitted to the peripheral device 101, and is displayed on the CRT 303 of the PCs 102 to 104 or the LCD 203 of the peripheral device 101.
[0128]
The PCs 102 to 104 or the peripheral device 101 displaying the setting screen of FIG. 24, before generating the setting screen, the driver software performs the “job deletion mode” attribute according to the device information acquisition flow shown in FIG. Assume that you have acquired a list of possible values for.
[0129]
In FIG. 24, a setting screen title 2400 represents a simple description of the setting screen, and indicates that the setting screen is a screen for designating a value of the “job deletion mode” attribute.
[0130]
The list box 2401 displays a list of attribute values that can be set in the “job deletion mode” attribute relating to the peripheral device 101 obtained by the device information acquisition flow shown in FIG. The attribute values listed in the list box 2401 correspond one-to-one with those listed in the list of values that can be set in the “job deletion mode” attribute in FIG. The user can select a desired value from the list box 2401 using the keyboard 304 or the pointing device 308 of the PCs 102 to 104.
[0131]
The reverse display 2402 indicates the value of the “job deletion mode” attribute that is currently selected. In FIG. 24, “designation by absolute time” is selected. An OK button 2403 is a button for determining the attribute value of the attribute of the job to be submitted to the value indicated by the reverse display 102.
[0132]
25, when the user designates “designation by absolute time” in the setting screen of the “job deletion mode” attribute in FIG. And is displayed on the CRT 303 of the PCs 102 to 104 or the LCD 203 of the peripheral device 101.
[0133]
The PCs 102 to 104 that display the setting screen of FIG. 25 or the peripheral device 101, according to the device information acquisition flow shown in FIG. It is assumed that “the maximum value of time” is acquired. Further, in the setting screen of FIG. 25, a check box 2504 for setting a “deletable during job execution” attribute by the user is also set.
[0134]
In FIG. 25, a setting screen title 2500 represents a simple description of the screen, and indicates that the setting screen is a screen for specifying the job deletion time in absolute time. In an edit box 2501, an absolute time when the user desires to delete a job is input and specified. In addition, there is a check box 2504 for designating what to do when a job is being executed when the absolute time designated by the user has arrived. In FIG. 25, it is specified that the job is forcibly deleted even if the job is being executed when the specified absolute time is reached.
[0135]
The OK button 2502 determines the deletion designation time of the job to be submitted as the value input in the edit box 2501, and determines whether or not to delete the job even if the job is being executed at the time designated in the edit box 2501. This button determines the value specified in the check box 214.
[0136]
A text 2503 indicates a time range that can be set by the user on the setting screen of FIG. In the present embodiment, “the maximum value of the elapsed time that can be specified as the job deletion time is 2 days” is calculated. From this value, the maximum value of the absolute time that can be specified is calculated in the text 2503. , 12:00 on January 25, 2000 AD is displayed.
[0137]
In addition, even when the user designates “designate by relative time” in FIG. 24, the job deletion time can be designated by relative time on the same screen as in FIG. 25, and the maximum value of the relative time that can be designated is displayed. .
[0138]
FIG. 26 shows a flow of processing for specifying job deletion time using the “job deletion mode” attribute when the driver software submits a job to the peripheral device 101.
[0139]
In step S2601, if it is desired to specify an absolute time mode in which a job is deleted at a specified date and time as the job deletion mode, the process proceeds to step S2602. On the other hand, if it is desired to designate a relative time mode in which the job is deleted after a designated time has elapsed since the time when the job was submitted, the process proceeds to step S2604.
[0140]
In step S2602, “specify in absolute time” is designated on the setting screen of the “job deletion mode” attribute in FIG. 24, and the process advances to step S2603. In step S2603, the desired job deletion time is input as an absolute time on the screen for specifying the absolute time in FIG. In step S2606, whether or not to delete the job is specified even if the job is being executed on the specified date and time on the screen for specifying the absolute time in FIG. 25, and the process ends.
[0141]
In step S2604, “designate by relative time” is designated on the setting screen of the “job deletion mode” attribute in FIG. 24, and the process advances to step S2605. In step S2605, a desired job deletion time is input as a relative time on the same relative time designation screen as in FIG. Further, on the screen for designating the relative time as in FIG. 25 in step S2606, whether or not to delete the job is designated even if the job is being executed after the designated time has elapsed, and the process is terminated.
[0142]
FIG. 27 shows the flow of processing when the driver software submits a job to the peripheral device 101. The processing from step S2701 to step S2704 is repeated until the setting of attributes necessary for the job processing desired by the driver software is completed.
[0143]
That is, in step S2702, the parameter (attribute) of the attribute setting command is set in order to set the job attribute as shown in the attribute list 2001 of FIG. 20 according to the job processing desired by the driver software. Here, of the job attributes, the parameters that can be set by the driver software are listed in the “attribute list supported by the job” in FIG. 21 obtained by the processing in FIG. 23, and column 2111 is TRUE. This attribute indicates that the attribute can be set. Further, attribute values that can be set for the attribute are indicated by a “list of settable values” obtained by the processing of FIG.
[0144]
In step S2703, the attribute setting command set in step S2702 is transmitted to the peripheral device 101 that is about to submit the job.
[0145]
In step S2705, data to be subjected to job processing such as image data created by an application or the like is transmitted to the peripheral device 101 by a job data transmission command. In step S2706, a job submission completion notification command indicating completion of transmission of the job submission command is transmitted, and the process ends. Through this series of job input processes, a job as shown in FIG.
[0146]
FIG. 28 shows the flow of processing when the peripheral device 101 receives a job input command from the driver software.
[0147]
In step S2801, the peripheral device 101 analyzes the command received from the driver software and its parameters, retains the result, and proceeds to step S2802. In step S2802, it is determined from the analysis result in step S2801 whether the received command is an attribute setting command. If it is an attribute setting command, the process proceeds to step S2803. On the other hand, if it is not an attribute setting command, the process advances to step S2806.
[0148]
In step S2803, the “attribute list supported by job” in FIG. 23 and the analysis result obtained in step S2801 are checked, and it is determined whether or not the attribute specified by the received attribute setting command can be set. judge. If it can be set, the process advances to step S2804. On the other hand, if setting is impossible, the process proceeds to step S2805.
[0149]
In step S2804, in accordance with the analysis result obtained in step S2801, the attribute value related to the specification is set in the attribute related to the specification, and the process ends. In step S2805, the attribute specified by the received attribute setting command cannot be set, the driver software is notified that the attribute cannot be set, and the process ends.
[0150]
In step S2806, it is determined from the analysis result obtained in step S2801 whether or not the received command is a job data transmission command. If it is a job data transmission command, the process advances to step S2807. On the other hand, if it is not a job data transmission command, the process advances to step S2808.
[0151]
In step S2807, the job data received following the command is stored in the RAM 202 or DISK 210 of the peripheral device 101, and the process ends. In step S2808, it is determined from the analysis result obtained in step S2801 whether or not the received command is a job submission end notification command. If it is a job submission end notification command, the process advances to step S2810. On the other hand, if it is not a job submission end notification command, the process advances to step S2809.
[0152]
In step S2810, preparations are made for starting job processing, and the flow advances to step S2811. In step S2811, the job process deletion condition is checked, and the process proceeds to the processes shown in FIGS. In step S2809, the received command is another command, processing depending on these commands is performed, and the process ends.
[0153]
FIG. 29 shows a processing flow when the peripheral device 101 receives an access command to the job attribute from the driver software.
[0154]
In step S2901, the received command and its parameters are analyzed, and the process proceeds to step S2902. In step S2902, whether or not the received command is an attribute acquisition command is checked from the analysis result in step S2901, and if it is an attribute acquisition command, the process proceeds to step S2903. If it is not an attribute acquisition command, the process proceeds to step S2907. move on. In step S2903, it is checked whether or not the attribute specified by the attribute command can be acquired. If it can be acquired, the process proceeds to step S2904. If it cannot be acquired, the process proceeds to step S2906.
[0155]
In step S2904, the value of the attribute held in the peripheral device 101 is acquired, and the process proceeds to step S2905. In step S2905, the attribute value acquired in step S2904 is set as a parameter of the reply command, a reply command for the attribute acquisition command is transmitted to the driver software, and the process ends. In step S2906, processing for notifying the driver software that attribute acquisition has failed is performed, and the process ends.
[0156]
In step S2907, it is checked from the analysis result in step S2901 whether or not the received command is an attribute value change command. If the received command is an attribute value change command, the process proceeds to step S2908. The process proceeds to S2912.
[0157]
In step S2908, it is checked whether or not the attribute specified by the attribute value change command can be changed. If it can be changed, the process proceeds to step S2909. If it cannot be changed, the process proceeds to step S2911.
[0158]
In step S2909, the designated attribute is changed to the designated attribute value in accordance with the designated command parameter, and the flow advances to step S2910. In step S2910, a process for notifying the driver software that the attribute value has been successfully changed is performed, and the process ends. In step S2911, a process of notifying the driver software that the change of the attribute value has failed is performed, and the process ends.
[0159]
In step S2912, the received command is another command, processing depending on these commands is performed, and the process ends.
[0160]
30 and 31 show the flow of job processing continued from step S2811 in the flow of processing the input job of FIG.
[0161]
In step S3001, it is determined whether the “job deletion mode” attribute is set. If the “job deletion mode” attribute is not set, the process advances to step S3002, and the job is deleted after execution and ends. On the other hand, if the “job deletion mode” attribute is set, the process advances to step S3003.
[0162]
In step S3003, it is checked whether or not the value of the “job deletion mode” attribute is “specified by relative time”. If “designated by relative time”, the process advances to step S3004. On the other hand, if it is not “designated by relative time”, the process proceeds to step S3010.
[0163]
In step S3004, it is checked whether or not the designated relative time exceeds the maximum value of the designated elapsed time. If the maximum value of the elapsed time that can be specified is not exceeded, the process advances to step S3005. On the other hand, if it exceeds the maximum value of the elapsed time that can be specified, the process proceeds to step S3016.
[0164]
In step S3005, it is determined whether or not the job is set to be forcibly deleted even when the job is being executed at the specified time. If the setting is such that the job is deleted even during execution, the process advances to step S3006 to wait until the specified time elapses. When the specified time elapses, the job is deleted in step S3007 and the process ends.
[0165]
On the other hand, if it is set not to delete the job during execution, the process advances to step S3008 to wait until the specified time elapses. When the specified time elapses, whether the job is being executed in step SS3009. Determine. If the job is not being executed, the process advances to step S3007 to delete the job and end the process. On the other hand, if the job is being executed, the process proceeds to step SS3002, where the job is deleted after being executed, and the process ends.
[0166]
In step S3010, it is checked whether or not the value of the “job deletion mode” attribute is “specified by absolute time”. If it is “designated by absolute time”, the process proceeds to step S3011. On the other hand, if it is not “absolute time”, the process proceeds to step S3017.
[0167]
In step S3011, the specified absolute time is compared with the current time, and it is checked whether or not the specified absolute time exceeds the maximum value of the elapsed time that can be specified. If the maximum value of elapsed time that can be specified is not exceeded, the process proceeds to step S3012. On the other hand, if it exceeds the maximum value of the elapsed time that can be specified, the process proceeds to step S3016.
[0168]
In step S3012, it is determined whether or not the job is set to be forcibly deleted even when the job is being executed at the specified time. If the setting is such that the job is deleted even during execution, the process proceeds to step S3013 to wait until the specified time is reached, and when the specified time is reached, the job is deleted in step S3007 and the process ends.
[0169]
On the other hand, if it is set not to delete the job during execution, the process proceeds to step S3014 and waits until the designated time is reached. When the designated time comes, it is determined in step S3015 whether the job is being executed. As a result, if the job is not being executed, the process advances to step S3007 to delete the job and end the process.
[0170]
On the other hand, if it is determined that the job is being executed, the process advances to step S3002, and after the job is executed, the job is deleted and the process ends.
[0171]
In step S3017, it is determined that the value of the designated “job deletion mode” attribute is invalid, and the process ends. In step S3016, an error process is performed assuming that a value exceeding the maximum value of the elapsed time that can be specified as the job deletion time is specified, and the process ends.
[0172]
[Third Embodiment]
In the second embodiment, the job deletion time after submitting the job can be specified by the “job deletion mode”. In the third embodiment, the job execution is performed by the “job deletion mode”. The job deletion time can be specified later.
[0173]
Since the third embodiment has much in common with the second embodiment, the differences will be mainly described.
[0174]
Although not shown in the third embodiment, a setting screen example of the “deletion mode after job execution” attribute similar to the setting screen shown in FIG. 24 is displayed on the CRT 303 of the PCs 102 to 104 or the LCD 203 of the peripheral device 101. Is displayed.
[0175]
For example, when “specified by relative time” is specified on this setting screen, a setting screen for the user to specify a desired time for job deletion after job execution as shown in FIG. 34 is displayed on the CRT 303 of the PCs 102 to 104. Or displayed on the LCD 203 of the peripheral device 101.
[0176]
The PCs 102 to 104 that display the setting screen of FIG. 34 or the peripheral device 101 perform “the job deletion time after job execution” by the device information acquisition flow shown in FIG. 23 before generating the setting screen of FIG. It is assumed that the maximum value of the elapsed time that can be specified is acquired.
[0177]
In FIG. 34, a setting screen title 3400 represents a simple description of the screen, and indicates that the setting screen is a screen for designating the time until deletion after job execution as a relative time. In an edit box 3401, a user inputs and specifies a relative time during which a job is desired to be deleted after the job is executed.
[0178]
An OK button 3402 is a button for determining the job deletion designation time after the job execution of the job to be input as the value input in the edit box 3401.
[0179]
A text 3403 indicates the maximum relative time that can be set by the user on the setting screen of FIG. In addition, even when the user designates “Specify by absolute time” on the same screen as in FIG. 24, the job deletion time after job deletion can be specified by absolute time on the screen similar to FIG. Displays the maximum absolute time.
[0180]
In the third embodiment, similarly to the second embodiment, the processes of FIGS. 23, 26, 27, 28, and 29 are executed. However, in the third embodiment, the process of step S2606 in FIG. 26 is omitted.
[0181]
In the third embodiment, after the processing in step S2810 in FIG. 28 is performed, the process proceeds to the processing flow in FIGS.
[0182]
That is, in step S3201 in FIG. 32, it is determined whether the “delete mode after job execution” attribute is set. If the “deletion mode after job execution” attribute is not set, the process advances to step S3202, and the job is immediately deleted after execution and ends. On the other hand, if the “deletion mode after job execution” attribute is set, the process advances to step S3203.
[0183]
In step S3203, it is checked whether the value of the “deletion mode after job execution” attribute is “specified by relative time”. If it is “designated by relative time”, the process proceeds to step S3204. On the other hand, if it is not “designated by relative time”, the process proceeds to step S3208.
[0184]
In step S3204, it is checked whether or not the designated relative time exceeds the maximum value of the designated elapsed time. If the maximum value of elapsed time that can be specified is not exceeded, the process advances to step S3205. On the other hand, if it exceeds the maximum value of the elapsed time that can be specified, the process proceeds to step S3012.
[0185]
In step S3205, the job is executed. In step S3206, the process waits until the specified time elapses. When the specified time elapses, the job is deleted in step S3207 and the process ends.
[0186]
In step S3208, it is checked whether the value of the “deletion mode after job execution” attribute is “specified by absolute time”. If it is “designated by absolute time”, the process proceeds to step S3209. On the other hand, if it is not “absolute time”, the process advances to step S3213.
[0187]
In step S3209, the designated absolute time is compared with the current time, and it is checked whether or not the designated absolute time exceeds the maximum value of the designated elapsed time. If the maximum value of the elapsed time that can be specified is not exceeded, the process advances to step S3210. On the other hand, if it exceeds the maximum value of the elapsed time that can be specified, the process proceeds to step S3212.
[0188]
In step S3210, the process waits until the designated absolute time is reached. When the designated absolute time arrives, it is determined in step S3211 whether or not the absolute time has arrived before the job processing is executed. As a result, if the absolute time according to the designation has arrived after the job processing is executed, the process proceeds to step S3207, where the job is deleted and the process ends.
[0189]
On the other hand, if the absolute time according to the specification has arrived before the execution of the job processing, the absolute time according to the specification becomes invalid, the process proceeds to step S3202, and the job is deleted immediately after the job is executed, and the process ends.
[0190]
In step S3213, it is determined that the value of the designated “deletion mode after job execution” attribute is invalid, and the process ends. In step S3212, an error process is performed assuming that a value exceeding the maximum value of the elapsed time that can be specified as the job deletion time is specified, and the process ends.
[0191]
【The invention's effect】
As described above, according to the present invention, in the peripheral device control system that controls the peripheral device by transmitting a control command from the external device to the peripheral device via the network, the peripheral device is processed by the peripheral device. Storage means for storing possible modes, wherein the external device acquires modes stored in the storage means via the network and displays a list; and modes displayed in a list by the display means Selection means for selecting a desired mode from the above, and transmission means for transmitting a job submission start command specifying the mode selected by the selection means to the peripheral device via the network Therefore, jobs can be issued from external devices to peripheral devices easily and inexpensively while effectively using system memory resources. Is possible.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram of a peripheral device control system to which the present invention is applied.
FIG. 2 is a block diagram illustrating a schematic configuration of hardware of a peripheral device.
FIG. 3 is a block diagram illustrating a schematic configuration of hardware of an external device (PC).
FIG. 4 is a diagram illustrating a command group for instructing job processing.
FIG. 5 is a flowchart showing processing when an attribute access command is received by a peripheral device.
FIG. 6 is a diagram showing a user interface for setting a “job submission start command mode” on the peripheral device control software.
FIG. 7 is a diagram (another configuration example) showing a user interface for setting a “job submission start command mode” on the peripheral device control software.
FIG. 8 is a diagram illustrating an example of a “mode (normal / interrupt) that can be specified for a job submission start command” attribute held by a peripheral device.
FIG. 9 is a diagram illustrating a “mode that can be specified for a job submission start command (job storage)” attribute held by a peripheral device.
FIG. 10 is a diagram illustrating a “mode (execution guaranteed) that can be specified for a job submission start command” attribute held by a peripheral device.
FIG. 11 is a diagram illustrating an example of a “mode (mixed) that can be specified in a job input start command” attribute held by a peripheral device.
FIG. 12 is a diagram showing a “list of“ storage file storage locations ”” attributes that the peripheral device holds.
FIG. 13 is a diagram showing a “default“ storage file storage location ”” attribute held by a peripheral device;
FIG. 14 is a flowchart illustrating processing for submitting a job to a peripheral device in the peripheral device control software.
FIG. 15 is a flowchart continued from FIG. 14;
FIG. 16 is a flowchart illustrating processing when a peripheral device receives a job.
FIG. 17 is a flowchart showing a continuation of FIG. 16 (job input start command processing).
FIG. 18 is a flowchart showing a continuation of FIG. 16 (job submission completion command processing).
FIG. 19 is a flowchart showing execution guaranteed job processing in a peripheral device.
FIG. 20 is a diagram illustrating a configuration example of a job processed by a peripheral device (second embodiment).
FIG. 21 is a diagram illustrating a list of job attributes held by a peripheral device.
FIG. 22 is a diagram illustrating a “list of attribute values that can be specified for a job deletion mode” held by a peripheral device.
FIG. 23 is a flowchart showing an attribute information inquiry process for a peripheral device;
FIG. 24 is a diagram illustrating a setting screen for a “job deletion mode” attribute;
FIG. 25 is a diagram illustrating a setting screen that is displayed when an absolute time is specified on the setting screen for the “job deletion mode” attribute;
FIG. 26 is a flowchart illustrating job deletion time designation processing.
FIG. 27 is a flowchart showing job input processing by an external device.
FIG. 28 is a flowchart showing processing when a job input command is received.
FIG. 29 is a flowchart illustrating processing when an access command to access job attributes is received.
30 is a flowchart continued from FIG. 28 (second embodiment).
FIG. 31 is a flowchart continued from FIG. 30;
FIG. 32 is a flowchart continued from FIG. 28 (third embodiment).
FIG. 33 is a flowchart continued from FIG. 32;
FIG. 34 is a diagram showing a setting screen that is displayed when relative time is specified on the setting screen for the “deletion mode after job execution” attribute (third embodiment);
[Explanation of symbols]
101 ... Peripheral devices
102, 103, 104 ... PC (personal computer)
105 ... Network
201, 301 ... CPU
202, 302 ... RAM
203 ... LCD
204, 304 ... keyboard
205, 307 ... ROM
206, 305 ... Communication interface
210, 306 ... DISK
303 ... CRT
308 ... Pointing device
401 ... Job submission start command
402: Job attribute setting command
403 ... Job transmission command
404 ... Job submission completion command
405 ... Mode
406 ... Additional information

Claims (15)

A peripheral device control system for controlling the peripheral device by transmitting a control command to the peripheral device from the external device via the network,
The peripheral device is,
A storage unit for storing an attribute list including attributes supported by the peripheral device and information indicating whether the supported attribute is an attribute whose attribute value can be set from software of the external device when a job is input; And
The external device is
A first acquisition means for acquiring the attribute list stored by the pre-term memory means from said peripheral device via the network,
A determination unit that determines whether each attribute included in the attribute list acquired by the first acquisition unit is an attribute whose attribute value can be set by software of the external device when a job is submitted;
A second acquisition for acquiring, from the peripheral device, an attribute value that can be set for the attribute that is determined to be an attribute whose attribute value can be set by software of the external device when the job is submitted by the determination unit Means,
Display means for displaying a setting screen for the attribute value reflecting the settable attribute value acquired by the second acquisition means ;
Generating means for generating a job according to the settings input through the setting screen shown by Ri table before Symbol display means,
Peripheral equipment control system, characterized in that and a transmission means for transmitting the job generated by the generation unit to the peripheral device via the network. The attribute list stored in the storage means includes information indicating whether or not the attribute value can be changed for a job already input from the external device,
  The peripheral device is
In accordance with an attribute change instruction received from the external device, attribute change determination means for determining whether or not the attribute instructed to change the attribute value by the attribute change instruction is an attribute that can change the attribute value;
Changing means for changing the attribute value according to the attribute change instruction when the attribute change determining means determines that the attribute is an attribute whose attribute value can be changed;
When the attribute change determination means determines that the attribute is not an attribute whose attribute value can be changed, information indicating that the attribute value change based on the attribute change instruction has failed is sent to the external device. The peripheral device control system according to claim 1, further comprising notification means for notifying. The attribute list stored in the storage unit includes information indicating whether or not an attribute value can be acquired for a job already input from the external device,
The peripheral device is
In accordance with an attribute acquisition instruction received from the external device, attribute acquisition determination means for determining whether the attribute instructed to acquire an attribute value by the attribute acquisition instruction is an attribute that can acquire the attribute value;
When the attribute acquisition determining means determines that the attribute is an attribute that can acquire an attribute value, the attribute acquisition value is acquired according to the attribute acquisition instruction, and the acquired attribute value is notified to the external device; When the attribute acquisition determination unit determines that the attribute is not an attribute that can acquire an attribute value, information indicating that acquisition of the attribute value based on the attribute acquisition instruction has failed is transmitted to the external device. The peripheral device control system according to claim 1, further comprising acquisition notification means for notifying. The peripheral device control system according to claim 1, wherein the display unit displays a setting screen on which a plurality of attribute values that can be set for the attribute are displayed as a list. The peripheral device control system according to claim 4, wherein the display unit displays a setting screen in a state where any one of the plurality of attribute values displayed in the list is selected. The display means displays a setting screen in which an attribute value that can be set for the attribute can be input and a value within the range of the attribute value that can be set for the attribute has already been input. The peripheral device control system according to claim 1. The peripheral device control system according to claim 1, wherein the display unit displays a setting screen in a state where a maximum value has already been input in the settable attribute value range. A control method of a peripheral device control system for controlling the peripheral device by transmitting a control command from the external device to the peripheral device via a network,
In the peripheral device ,
A storage step for storing an attribute list including information supported by the peripheral device and information indicating whether the supported attribute is an attribute whose attribute value can be set from software of the external device when a job is submitted ;
In the external device,
A first acquisition step of acquiring the attribute list stored in the storage step from the peripheral device via the network ;
A determination step of determining whether or not each attribute included in the attribute list acquired in the first acquisition step is an attribute whose attribute value can be set by software of the external device when a job is submitted;
A second acquisition for acquiring, from the peripheral device, an attribute value that can be set for an attribute that is determined to be an attribute that can be set by the software of the external device at the time of job submission in the determination step. Steps,
A display step for displaying a setting screen for the attribute value reflecting the settable attribute value acquired by the second acquisition step ;
A generation step of generating a job according to the setting input via the setting screen displayed by the display step ;
The method of the peripheral device control system characterized by having, a transmission step of transmitting the job generated by the generation step to the peripheral device via the network. The attribute list stored by the storing step includes information indicating whether or not the attribute value can be changed for the job already input from the external device,
In the peripheral device,
An attribute change determination step for determining whether or not an attribute whose attribute value is instructed by the attribute change instruction is an attribute that can change the attribute value, in response to the attribute change instruction received from the external device;
  A change step of changing the attribute value according to the attribute change instruction when the attribute change determination step determines that the attribute is an attribute whose attribute value can be changed;
When the attribute change determination step determines that the attribute is not an attribute whose attribute value can be changed, information indicating that the change of the attribute value based on the attribute change instruction has failed is transmitted to the external device. The method of controlling a peripheral device control system according to claim 8, further comprising a notification step of notifying. The attribute list stored by the storing step includes information indicating whether or not the attribute can be acquired for the job already input from the external device,
In the peripheral device,
In accordance with an attribute acquisition instruction received from the external device, an attribute acquisition determination step for determining whether or not the attribute instructed to acquire an attribute value by the attribute acquisition instruction is an attribute that can acquire the attribute value;
When it is determined by the attribute acquisition determination step that the attribute is an attribute capable of acquiring an attribute value, the attribute value is acquired according to the attribute acquisition instruction, and the acquired attribute value is notified to the external device; If the attribute acquisition determination step determines that the attribute is not an attribute capable of acquiring an attribute value, information indicating that acquisition of the attribute value based on the attribute acquisition instruction has failed is transmitted to the external device. The peripheral device control system control method according to claim 8 or 9, further comprising an acquisition notification step of notifying. 11. The peripheral device control system according to claim 8, wherein in the display step, a setting screen on which a plurality of attribute values that can be set for the attribute are displayed in a list is displayed. Control method. 12. The control method for a peripheral device control system according to claim 11, wherein the display step displays a setting screen in a state where any one of the plurality of attribute values displayed in the list is selected. . In the display step, a setting screen in which an attribute value that can be set for the attribute can be input and a value within the attribute value range that can be set for the attribute has already been input is displayed. The control method of the peripheral device control system according to claim 8, wherein 9. The control method for a peripheral device control system according to claim 8, wherein in the display step, a setting screen is displayed in a state where a maximum value is already input in the settable attribute value range. A program for causing a computer to execute the control method of the peripheral device control system according to claim 8.

Images