Printing device, control method and program
Patent Information
- Application Number
- JP2021030628
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-26
- Publication Date
- 2025-02-20
- Estimated Expiration
- 2041-02-26
Smart Images
Figure 0007633834000001 
Figure 0007633834000002 
Figure 0007633834000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a printing apparatus, a control method, and a program for controlling a job. [Background technology]
[0002] An image processing device automatically stores received print jobs in a job spool area in a storage device. Therefore, when the job spool area in the storage device becomes full, it is necessary to delete one of the jobs in the job spool area in order to secure an appropriate amount of free space in the job spool area for storing the next print job received.
[0003] Patent Document 1 describes that when a print job to be stored in a storage unit is received, a determination unit is provided that determines whether the received print job can be stored in the storage unit. Patent Document 1 also describes that when the determination unit determines that the print job cannot be stored, a print job that matches attributes to be deleted is preferentially deleted from among multiple print jobs stored in the storage unit.
[0004] Incidentally, some image processing devices have a data invalidation function (hereinafter referred to as secure erase) that, in addition to deleting management information, overwrites print data once or multiple times with hexadecimal values such as 0x00, 0xFF, or 0xAA when deleting data. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2012-162041 A Summary of the Invention [Problem to be solved by the invention]
[0006] Patent Document 1 describes that print jobs that match the attributes to be deleted are given priority for deletion. However, even if a print job with high security is to be deleted quickly after printing, if the attributes do not match, data invalidation due to deletion will be delayed, resulting in reduced security. For example, if a subsequent job is received before deleting a preceding job with high security and printing of the subsequent job is started, data invalidation due to deletion of the preceding job will be delayed, resulting in reduced security.
[0007] An object of the present invention is to provide a printing device, a control method, and a program that, when a job is subsequently received, appropriately deletes job data in accordance with the attributes of the job. [Means for solving the problem]
[0008] In order to solve the above problem, a printing device according to the present invention includes a receiving unit that receives a job, a printing unit that executes printing of job data of the job received by the receiving unit, and a deleting unit that deletes the job data after printing by the printing unit is completed. ,before After the printing of the first job data of the first job received by the receiving means is completed, the receiving means receives a second job before the first job data is deleted by the deleting means. Before Attributes of the first job data is an attribute corresponding to a first type of job data that should be deleted using secure erasure in which the first job data is overwritten once or multiple times with a value for invalidation after printing, and an attribute of second job data of the second job is an attribute corresponding to a second type of job data that should not be securely erased, control is performed so that the first job data is deleted using the secure erasure before printing of the second job data, and when an attribute of the first job data is an attribute corresponding to the second type of job data and an attribute of the second job data is an attribute corresponding to the first type of job data, control is performed so that the first job data is deleted using the secure erasure before printing of the second job data, a control means for controlling the printing of the first job data after the printing of the first job data is completed, to perform the deletion of the second job data using the secure erasure and then to delete the first job data, and when an attribute of the first job data and an attribute of the second job data are both attributes corresponding to the first type of job data, to hold off on the deletion of the first job data using the secure erasure and to print the second job data, and for controlling the printing of the second job data after the printing of the second job data is completed, to delete, using the secure erasure, one of the first job data and the second job data which has been determined to be deleted first based on a predetermined condition, wherein the predetermined condition is a condition based on the number of occurrences of confidential characters and / or images in each of the first job data and the second job data. It is characterized by: Effect of the Invention
[0009] According to the present invention, when a job is subsequently received, the job data can be appropriately deleted in accordance with the attributes of the job. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a diagram illustrating a schematic configuration of an image processing device. [Diagram 2] FIG. 1 is a schematic cross-sectional view of an image processing device. [Diagram 3]4 is a time chart for explaining job control. [Figure 4] FIG. 4 illustrates a job management table. [Diagram 5] 13 is a flowchart showing a job control process. [Figure 6] 4 is a time chart for explaining job control. [Figure 7] FIG. 4 illustrates a job management table. [Figure 8] 13 is a flowchart showing a job control process. [Figure 9] 4 is a time chart for explaining job control. [Figure 10] FIG. 4 illustrates a job management table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, the embodiments will be described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe a number of features, not all of these features are essential to the invention, and the features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.
[0012] [First embodiment] FIG. 1 is a diagram showing a schematic configuration of an image processing apparatus in this embodiment. In this embodiment, the image processing apparatus is shown to have only a printing function, but is not limited to this. For example, the image processing apparatus may be configured as a copying machine further equipped with a reading device that optically reads an image on a document, or may be configured as a multi-function peripheral (MFP). In FIG. 1, the image processing apparatus 100 includes a printer controller 120, a printer engine 150, a HDD (Hard Disk Drive) 161, and an input / output device 162. The image processing apparatus 100 can be connected to a host computer 190 such as a PC via a network 191.
[0013] The printer controller 120 includes an HDD interface (I / F) 121, an input / output device I / F 122, a ROM I / F 125, and a memory controller 126. The printer controller 120 also includes a host I / F 127, a CPU (Central Processing Unit) 128, a controller engine interface 129, and an image processing unit 130. These are connected to each other so as to be able to communicate with each other via a system bus 132. The printer controller 120 also includes a Flash ROM 123 and a RAM 124, which are connected to the system bus 132 via the ROM I / F 125 and the memory controller 126, respectively.
[0014] The CPU 128 is a central processing unit in the form of a microprocessor (microcomputer) and generally controls the operation of the entire image processing device 100 by executing programs and starting hardware. The Flash ROM 123 stores data, tables, etc. required for programs executed by the CPU 128 and various operations of the image processing device 100. The RAM 124 is used as a work area for the CPU 128 and a temporary storage area (buffer area) for various received data and setting data.
[0015] The image processing unit 130 executes various image processes. For example, the image processing unit 130 executes a process of expanding (converting) print data expressed in a page description language into bitmap image data. Also, the image processing unit 130 executes a process of converting the color space (for example, YCbCr) of the image data included in the input print data into a standard RGB color space (for example, sRGB). Also, the image processing unit 130 executes a resolution conversion process for the image data into a number of pixels that can be processed by the image processing device 100. Also, the image processing unit 130 executes various image processes as necessary, such as image analysis and image correction. Image data obtained by these image processes is stored in the RAM 124 or the HDD 161.
[0016] The printer engine 150 is a printing unit that forms an image. The printer engine 150 includes an inkjet recording head 151, a cutter unit 152, a conveying motor 153, a controller-engine interface 154 with the printer controller 120, and an optical sensor 155. Each component is connected to each other via a system bus 156 so as to be able to communicate with each other.
[0017] The inkjet recording head 151 is a printing unit that prints an image, and prints an image on a sheet, which is a recording medium, based on image data. The inkjet recording head 151 has, for example, a plurality of recording heads for a plurality of colors, and forms an image on the sheet by ejecting ink droplets from the recording heads in synchronization with the conveyance of the sheet. Note that the image processing device 100 in this embodiment will be described as an example of an inkjet recording printer that uses ink as a recording material, but is not limited to this. For example, it may be a printer that prints by another recording method, such as a thermal printer (sublimation type, thermal transfer type, etc.), a dot impact printer, an LED printer, or an electrophotographic method such as a laser printer.
[0018] The cutter unit 152 is, for example, a mechanism for cutting roll paper used as a printing sheet, for example, cutting the roll paper to a predetermined length after an image has been printed on it. The transport motor 153 is a motor for driving a transport roller that transports the roll paper, and is controlled by the CPU 128. The optical sensor 155 is a measurement unit for measuring the attribute values of the sheet, and is a reflective optical sensor including an LED (Light Emitting Diode) as a light emitting element, a specular reflection light receiving element, a diffuse light receiving element, etc. The image processing device 100 uses the optical sensor 155 to measure attribute values such as the intensity of the specular reflection light and diffuse reflection light of the sheet on the platen, and the thickness of the paper.
[0019] The input / output device 162 includes hardware keys and a panel for the user to perform various operations, and a display unit for displaying (notifying) various information to the user. The input / output device 162 may also be configured to present information to the user by outputting a sound (buzzer, voice, etc.) based on sound information from a sound generator. For example, when the user selects a paper type using the input / output device 162 during paper feeding, the device is controlled to perform the transport set for each paper type.
[0020] HDD 161 is a non-volatile storage area, and stores programs executed by CPU 128, print data, and setting information required for various operations of image processing device 100. Note that, in addition to HDD 161, a large-capacity storage device such as a flash memory may be used.
[0021] In this embodiment, the input / output device 162 is described as being configured inside the image processing device 100, but the present invention is not limited to this. For example, the input / output device 162 may be connected as an external configuration via a network 191. Also, the host computer 190 may operate as the input / output device 162. Also, the image processing device 100 may be configured so that, in addition to the input / output device 162, other input / output devices are further connected via the network 191 or the like.
[0022] The host computer 190 is, for example, an external device that serves as a supply source of print data, and has a printer driver installed therein. Instead of the host computer 190, the image processing device 100 may be provided with a data providing device that serves as a supply source of print data, such as an image reader, a digital camera, or a smartphone. The network 191 may be any of a wired communication network, a wireless communication network, and a network including both.
[0023] The image processing device 100 performs printing processing based on, for example, a print job and print data transmitted from the host computer 190. The image processing device 100 also has a reprint function, and when, for example, a user instructs reprint processing by operating a panel of the image processing device 100, a document or the like is reprinted. In the reprint processing, even after the end of the printing processing, the image forming device 100 does not delete the print data stored in the internal storage area, but continues to store the data based on the free space in the storage area. This allows the host computer 190 to reprint the same print data as the print data printed once, based on an instruction via the panel operation of the image processing device 100, without resending the print data to the image processing device 100.
[0024] FIG. 2 is a schematic cross-sectional view of the image processing device 100 in this embodiment. FIG. 2 shows a portion related to the transport of roll paper. The image processing device 100 is equipped with two roll paper tubes, and different types of roll paper can be installed on each of them. FIG. 2 shows the positional relationship in the image processing device 100, from the upper roll paper tube 201 to the roll paper 204, which is transported along the transport path by the transport roller 205 and measured by the optical sensor 155 provided at a position facing the platen. The inkjet recording head 151 forms an image by ejecting ink droplets onto the roll paper 204 transported from the upper roll paper tube 201. In addition, the image processing device 100 can supply roll paper from the lower roll paper tube 202 after switching from the upper to the lower roll paper using the transport roller 205. During paper feeding, the image processing device 100 transports the roll paper 204 installed on the upper roll paper tube 201 or the lower roll paper tube 202 to the platen by the transport roller 205. At that time, the optical sensor 155 measures the specular reflection light intensity, diffuse reflection light intensity, and roll paper thickness of the roll paper 204 as well as the roll paper width. After printing is completed, the roll paper is cut by the cutter unit 152 to the length desired by the user.
[0025] Next, a flow of print job control processing executed by the image processing device 100 in this embodiment will be described. Normally, even if only the management information of a print job is deleted, there is a high possibility that a third party can restore the original data by removing the HDD and using a data recovery tool, which may lead to information leakage. For this reason, the image processing device 100 has a data invalidation function (secure erase function) that overwrites the print data (job data) with hexadecimal values such as 0x00, 0xFF, and 0xAA once or multiple times in addition to deleting the management information when invalidating data. In this embodiment, a print job that performs data invalidation using such a secure erase function is called a secure print job. Moreover, jobs other than a secure print job are called normal print jobs to distinguish them from secure print jobs.
[0026] If a normal print job is received while deleting job data of a secure print job, the deletion by secure erase is interrupted, and from the viewpoint of processing efficiency, printing of the received normal print job may be prioritized. However, from the viewpoint of security, it is desirable for the job data of a secure print job to be erased by the secure erase function as soon as possible after printing is completed. In this embodiment, even if a normal print job is received while deleting job data of a secure print job, the deletion of the job data of the secure print job is prioritized. With such a configuration, the security of the job data of the secure print job can be ensured.
[0027] FIG. 3 is a time chart for explaining job control when a normal print job is received while deleting job data of a secure print job. FIG. 4 is a diagram showing an example of a job management table for managing the state of a job. A job table 400 includes information on a job ID 401, a job save time 402, a job type 403, and a state 404. FIGS. 4(a) to 4(g) respectively show the state of the job management table 400 at the timings 301, 302, 303, 304, 305, 306, and 307 in FIG. 3. FIG. 5 is a flowchart showing the process of job control. It is not limited to the job type, and the state of a newly received job becomes "waiting to print", and when printing starts, it becomes "printing", and when printing is completed, it transitions to "waiting to delete". Also, when deletion starts from "waiting to delete", it becomes "deleting", and when deletion is completed, it transitions to "deletion completed". Also, there are cases where the state transitions from "waiting to print" to "printing pending" where the start of printing is pending. Furthermore, there are cases where the state transitions from "waiting to delete" to "deletion pending" where the start of deletion is pending.
[0028] Hereinafter, with reference to FIGS. 3 to 5, a process of prioritizing deletion of job data of a secure print job when a normal print job is received while job data of a secure print job is being deleted will be described.
[0029] In the image processing device 100, the host I / F 127 stores job data received from the host computer 190 in the RAM 124 or the HDD 161. After storing the received job data, the host I / F 127 notifies the CPU 128 of the completion. At this time, the CPU 128 secures a job management table 400 for managing the job status in a storage area of the RAM 124 or the HDD 161. The CPU 128 determines whether the received job is a secure print job or not from attribute information added by the sender of the job data, and stores the determination result in the job type 403 on the job management table 400. For example, the CPU 128 may determine that the job data is a secure print job if it is job data transmitted from a specific relay server by using the device information of the sender, which is the attribute information. The CPU 128 may also determine that the job data is a secure print job if it is job data transmitted by a specific user, by using the print executor information, which is the attribute information. CPU 128 may also determine whether a job is a secure print job based on the attribute information, such as the software of the sender, whether interrupt printing is performed, the print mode, color / monochrome, CAD / photo, etc. Furthermore, CPU 128 may determine whether a received job is a secure print job based on the type of job data. For example, CPU 128 may determine whether a job is a secure print job based on the type of job data, such as printing from a USB memory, printing performed by operating a user interface provided in the device, or FAX printing.
[0030] In S501, CPU 128 waits until the job status is changed, and proceeds to S502 when the job status is changed. As a configuration for detecting a change in the job status, for example, CPU 128 may store the contents of job management table 400 in HDD 161, and compare the last stored table status with the latest table status at regular time intervals. Also, for example, CPU 128 may provide a job management table change flag in RAM 124 separately from job management table 400, and turn the job management table change flag ON when the job status is changed. After that, CPU 128 may determine whether the flag is ON at regular time intervals. Also, for example, CPU 128 may detect a change based on the timing when job data deletion or recording is completed.
[0031] In S502, the CPU 128 judges whether or not a new job has been received. If it is judged that a new job has been received, the process proceeds to S503, and if it is judged that a new job has not been received, the process proceeds to S504. For example, the CPU 128 may store the contents of the job management table 400 in the HDD 161 and make the judgment by comparing the state of the last stored table with the latest table at regular time intervals. Also, for example, the CPU 128 may provide a new job reception flag in the RAM 124 in addition to the job management table 400, turn the new job reception flag ON when a new job is received, and judge whether the flag is ON at regular time intervals. Also, for example, the CPU 128 may make the judgment based on an interrupt or communication performed from the host I / F 127 to the CPU 128 when a new job is received.
[0032] At timing 301 in FIG. 3, a new job is received, so it is determined in S502 that a new job has been received, and the process proceeds to S503.
[0033] In S503, CPU 128 adds information about the received job to job management table 400, and proceeds to S504. At timing 301 in Fig. 3, at the end of S503, job management table 400 is in the state shown in Fig. 4(a). That is, JOB1 is received at 10:10 and saved. Note that JOB1 is determined to be a secure print job based on its attribute information, and status 404 is set to "waiting to print."
[0034] In S504, the CPU 128 determines whether or not there is a job whose status 404 is "printing" in the job management table 400. If it is determined that there is a job whose status is "printing", the process repeats the process from S501, and if it is determined that there is no job whose status is "printing", the process proceeds to S505.
[0035] At timing 301 in FIG. 3, as shown in FIG. 4A, there is no job in the "printing" state, so the process proceeds to S505.
[0036] In S505, the CPU 128 determines whether or not there is a job whose status 404 is "print pending" in the job management table 400. If it is determined that there is a job whose status is "print pending", the process proceeds to S506, and if it is determined that there is no job whose status is "print pending", the process proceeds to S507.
[0037] At timing 301 in FIG. 3, as shown in FIG. 4A, there is no job in the "print pending" state, so the process proceeds to S507.
[0038] In S507, the CPU 128 determines whether or not there is a job whose status 404 is "waiting to print" in the job management table 400. If it is determined that there is a job whose status is "waiting to print", the process proceeds to S508, and if it is determined that there is no job whose status is "waiting to print", the process proceeds to S512.
[0039] At timing 301 in FIG. 3, as shown in FIG. 4A, there is JOB1 which is "waiting to be printed," so the process proceeds to S508.
[0040] In S508, the CPU 128 determines whether or not there is a job whose status 404 is "being deleted" in the job management table 400. If it is determined that a job whose status is "being deleted" exists, the process proceeds to S509, and if it is determined that a job whose status is "being deleted" does not exist, the process proceeds to S511.
[0041] At timing 301 in FIG. 3, as shown in FIG. 4(a), there is no job in the "being deleted" state, so the process proceeds to S511.
[0042] In S511, CPU 128 changes the status 404 of JOB1 in job management table 400 to "printing" and proceeds to S501. At this time, CPU 128 starts printing the job that is "waiting to print". CPU 128 commands image processing unit 130 to generate print data based on the job data stored in RAM 124 or HDD 161. Image processing unit 130 generates print data based on the job data stored in RAM 124 or HDD 161 in accordance with the command, and stores the generated print data in RAM 124 or HDD 161. Print engine 150 records an image on a sheet using inkjet print head 151 based on the stored print data.
[0043] 3, the CPU 128 starts printing of JOB1, whose status 404 is "waiting to print." Then, as shown in FIG. 4B, the CPU 128 changes the status 404 of JOB1 in the job management table 400 to "printing," and the status transitions to timing 302.
[0044] Thereafter, when the recording operation is completed, the state transitions to timing 303, and the CPU 128 changes the state 404 of JOB1 to "waiting for deletion" as shown in FIG. 4(c). When the state is changed to "waiting for deletion", the process proceeds from S501 to S502. In S502, it is determined that no new job has been received. Then, since the job management table 400 is in the state of FIG. 4(c), it is determined in S504 that there is no job that is "printing", and in S505 that there is no job that is "pending printing". Furthermore, in S507, it is determined that there is no job that is "waiting to print", and the process proceeds to S512.
[0045] In S512, the CPU 128 determines whether or not there is a job whose status 404 is "deletion pending" in the job management table 400. If it is determined that there is a job whose status is "deletion pending", the process proceeds to S513, and if it is determined that there is no job whose status is "deletion pending", the process proceeds to S514.
[0046] At timing 303 in FIG. 3, as shown in FIG. 4C, there is no job whose status 404 is "deletion pending," so the process proceeds to S514.
[0047] In S514, the CPU 128 determines whether or not there is a job whose status 404 is "waiting to be deleted" in the job management table 400. If it is determined that there is a job waiting to be deleted, the process proceeds to S515, and if it is determined that there is no job "waiting to be deleted", the process proceeds to S501.
[0048] At timing 303 in FIG. 3, as shown in FIG. 4C, there exists a JOB1 whose status 404 is "waiting for deletion," so the process proceeds to S515.
[0049] In S515, the CPU 128 changes the status 404 of JOB1 in the job management table 400 that is "waiting to be deleted" to "being deleted" as shown in FIG. 4(d) and proceeds to S501. At this time, the CPU 128 starts deleting the job data of JOB1 that is "waiting to be deleted". The CPU 128 overwrites the data in the storage area of the job data stored in the RAM 124 or the HDD 161 with a fixed value in hexadecimal notation such as 0x00, 0xFF, or 0xAA or a random number once or multiple times. At this time, the fixed value and the number of times to overwrite the data may be changed in consideration of the difference in confidentiality from a normal print job.
[0050] 3, the CPU 128 starts deleting the job data of JOB1, whose status 404 is "waiting for deletion." At this time, as shown in FIG 4(d), the CPU 128 changes the status 404 of JOB1 in the job management table 400 to "being deleted," and proceeds to S501.
[0051] Thereafter, the host I / F 127 receives JOB2 as a new job. It is assumed that JOB2 was received and saved at 10:15. The state transitions to timing 304. In S502, it is determined that a new job has been received, and in S503, although not yet shown in FIG. 4(d), at this point in time, the state 404 of JOB2 becomes "waiting to print."
[0052] Since the job management table 400 is in the state shown in Fig. 4(d), it is determined in S504 that there is no job in the "printing" state, and in S505 that there is no job in the "print pending" state. Then, in S507, it is determined that there is a job in the "waiting to print" state, and the process proceeds to S508. In S508, since JOB1 in the "deleting" state exists, the process proceeds to S509.
[0053] In S509, the CPU 128 determines whether or not a job whose job type 403 is "secure printing" and whose status 404 is "being deleted" exists in the job management table 400. If it is determined that a job whose job type is "secure printing" and whose status is "being deleted" exists, the process proceeds to S516, and if it is determined that a job whose job type is "secure printing" and whose status is "being deleted" does not exist, the process proceeds to S510.
[0054] At timing 304 in FIG. 3, as shown in FIG. 4D, there is a JOB1 that is "secure printing" and "being deleted", so the process proceeds to S516.
[0055] 4D, the CPU 128 changes the status 404 of JOB2, which is "waiting to print", to "print pending" and proceeds to S501. In this manner, in this embodiment, if the status of JOB1, a secure print job, is "deleting", printing of JOB2, a normal print job that was subsequently received and is in the "waiting to print" status, is not started, JOB2 is set to "print pending", and priority is given to deleting the job data of JOB1.
[0056] Thereafter, when the job data deletion is completed, the state transitions to timing 305, and the CPU 128 changes the state 404 of JOB1 to "deletion completed" as shown in FIG. 4(e). When the state is changed to "deletion completed", the process proceeds from S501 to S502. In S502, it is determined that no new job has been received. Then, since the job management table 400 is in the state shown in FIG. 4(e), it is determined in S504 that there is no job that is "printing", and the process proceeds to S505. At this point, although not shown in FIG. 4(e), the state 404 of JOB2 is still "print pending". In S505, since there is a JOB2 in "print pending", the process proceeds to S506.
[0057] In S506, the CPU 128 changes the status 404 of JOB2 to "printing" as shown in Fig. 4(e) and proceeds to S501. At this time, the CPU 128 starts printing JOB2 which is in "print pending" status.
[0058] 3, the CPU 128 starts printing JOB2, whose status 404 is "printing pending." After that, the CPU 128 changes the status 404 of JOB2 to "printing," as shown in FIG. 4(e), and the status transitions to timing 305.
[0059] Thereafter, when the recording operation is completed, the state transitions to timing 306, and the CPU 128 changes the state 404 of JOB2 to "waiting for deletion" as shown in FIG. 4(f). When the state is changed to "waiting for deletion", the process proceeds from S501 to S502. In S502, it is determined that a new job has not been received. Then, since the job management table 400 is in the state of FIG. 4(f), it is determined in S504 that there is no job that is "printing", and in S505 that there is no job that is "pending printing". Then, in S507, it is determined that there is no job that is "waiting to print", and in S512, it is determined that there is no job that is "pending deletion", and the process proceeds to S514.
[0060] At timing 306 in FIG. 3, as shown in FIG. 4(f), there is JOB2 which is "waiting for deletion", so the process proceeds from S514 to S515.
[0061] In S515, the CPU 128 changes the status 404 of JOB2 from "waiting to be deleted" to "being deleted" and proceeds to S501. At this time, the CPU 128 starts deleting the job data of JOB2 that is "waiting to be deleted." As shown in FIG. 4(g), the CPU 128 changes the status 404 of JOB2 to "being deleted" and proceeds to S501.
[0062] Thereafter, when the job data deletion is completed, the state transitions to timing 307, and the CPU 128 changes the state 404 of JOB2 to "deleting", as shown in FIG. 4G. When the state is changed to "deleting", the process proceeds from S501 to S502. In S502, it is determined that a new job has not been received. Then, since the job management table 400 is in the state of FIG. 4G, it is determined in S504 that there is no job that is "printing", and in S505 that there is no job that is "print pending". Then, in S507, it is determined that there is no job that is "waiting to print", and in S512, it is determined that there is no job that is "deletion pending", and the process proceeds to S514. Since there is no job that is "waiting to delete" in S514, the process proceeds to S501.
[0063] As described above, according to the present embodiment, when the next normal print job is received while the job data of the secure print job is being deleted, the job data of the secure print job is deleted preferentially. With such a configuration, it is possible to quickly delete highly confidential job data to a state where it is difficult to restore it. In addition, since it is determined whether or not the job is a secure print job from the attribute information given by the sender of the print data and the type of the print data without user operation, it is possible to improve convenience.
[0064] [Second embodiment] The second embodiment will be described below with respect to the differences from the first embodiment. In the first embodiment, a configuration was described in which if the next normal print job is received while job data of a secure print job is being deleted, the job data of the secure print job is preferentially deleted. In this embodiment, if the next secure print job is received while job data of a normal print job is being deleted, the job data of the secure print job is preferentially deleted when all jobs have been printed. With such a configuration, the security of the secure print job can be ensured.
[0065] Fig. 6 is a time chart for explaining job control when a secure print job is received while job data of a normal print job is being deleted. Fig. 7 is a diagram showing an example of a job management table for managing the job status. A job table 700 includes information such as a job ID 701, a job save time 702, a job type 703, and a status 704. Figs. 7(a) to (g) respectively show the status of the job management table at the times 601, 602, 603, 604, 605, 606, and 607 in Fig. 6. Fig. 8 is a flowchart showing the job control process.
[0066] Hereinafter, with reference to FIGS. 6 to 8, a process of prioritizing deletion of job data of a secure print job when printing of a secure print job is received while job data of a normal print job is being deleted will be described.
[0067] In the image processing device 100, the host I / F 127 stores job data received from the host computer 190 in the RAM 124 or the HDD 161. After storing the received job data, the host I / F 127 notifies the CPU 128 of the completion. At this time, the CPU 128 secures a job management table 700 for managing the job status in a storage area of the RAM 124 or the HDD 161. The CPU 128 determines whether the received job is a secure print job or not from attribute information added by the sender of the job data, and stores the determination result in the job type 703 on the job management table 700. For example, the CPU 128 may determine that the job data is a secure print job if it is job data transmitted from a specific relay server by using the device information of the sender, which is the attribute information. The CPU 128 may also determine that the job data is a secure print job if it is job data transmitted by a specific user, by using the print executor information, which is the attribute information. CPU 128 may also determine whether a job is a secure print job based on the attribute information, such as the software of the sender, whether interrupt printing is performed, the print mode, color / monochrome, and CAD / photo. CPU 128 may also determine whether a received job is a secure print job based on the type of print data. For example, CPU 128 may determine whether a job is a secure print job based on the type of job data, such as printing from a USB memory, printing performed by operating a user interface provided in the device, or FAX printing.
[0068] In S801, CPU 128 waits until the job status is changed, and proceeds to S802 when the status is changed. As a configuration for detecting a change in the job status, for example, CPU 128 may store the contents of job management table 700 in HDD 161, and compare the last stored table status with the latest table status at regular time intervals. Also, for example, CPU 128 may provide a job management table change flag in RAM 124 separate from job management table 700, and turn the job management table change flag ON when the job status is changed. Thereafter, CPU 128 may determine whether the flag is ON at regular time intervals. Also, for example, CPU 128 may detect a change based on the timing when job data deletion or recording is completed.
[0069] In S802, the CPU 128 judges whether or not a new job has been received. If it is judged that a new job has been received, the process proceeds to S803, and if it is judged that a new job has not been received, the process proceeds to S815. For example, the CPU 128 may store the contents of the job management table 700 in the HDD 161 and make the judgment by comparing the state of the last stored table with the latest table at a certain time interval. Also, for example, the CPU 128 may provide a new job reception flag in the RAM 124 in addition to the job management table 700, turn the new job reception flag ON when a new job is received, and judge whether the flag is ON at a certain time interval. Also, for example, the CPU 128 may make the judgment based on an interrupt or communication performed from the host I / F 127 to the CPU 128 at the time when a new job is received.
[0070] At timing 601 in FIG. 6, a new job is received, so it is determined in S802 that a new job has been received, and the process proceeds to S803.
[0071] In S803, the CPU 128 adds the information of the received job to the job management table 700, and proceeds to S815. At timing 601 in Fig. 6, at the end of S803, the job management table 700 is in the state shown in Fig. 7(a). That is, JOB3 is received and saved at 10:10. Note that JOB3 is determined to be a normal print job based on its attribute information, and the status 704 is set to "waiting to print."
[0072] In S815, the CPU 128 determines whether or not there is a job whose status 704 is "printing" in the job management table 700. If it is determined that a job whose status is "printing" exists, the process proceeds to S801, and if it is determined that a job whose status is "printing" does not exist, the process proceeds to S804.
[0073] At timing 601 in FIG. 6, as shown in FIG. 7A, there is no job in the "printing" state, so the process proceeds to S804.
[0074] In S804, the CPU 128 determines whether or not there is a job whose status 704 is "waiting to print" in the job management table 700. If it is determined that there is a job whose status is "waiting to print", the process proceeds to S805, and if it is determined that there is no job whose status is "waiting to print", the process proceeds to S807.
[0075] At timing 601 in FIG. 6, as shown in FIG. 7A, there is JOB3 which is "waiting to be printed," so the process proceeds to S805.
[0076] In S805, the CPU 128 determines whether or not there is a job whose status 704 is "being deleted" in the job management table 700. If it is determined that a job whose status is "being deleted" exists, the process proceeds to S816, and if it is determined that a job whose status is "being deleted" does not exist, the process proceeds to S806.
[0077] At timing 601 in FIG. 6, since there is no job in the "being deleted" state, the process proceeds to S806.
[0078] In S806, the CPU 128 changes the status 704 in the job management table 700 to "printing" as shown in FIG. 7B, and proceeds to S801. At this time, the CPU 128 starts printing the job that is "waiting to print". The CPU 128 commands the image processing unit 130 to generate print data based on the job data stored in the RAM 124 or HDD 161. The image processing unit 130 generates print data based on the job data stored in the RAM 124 or HDD 161 in accordance with the command, and stores the generated print data in the RAM 124 or HDD 161. The print engine 150 uses the inkjet print head 151 to print an image on a sheet based on the stored print data.
[0079] 6, the CPU 128 starts printing of job JOB3, whose status 704 is "waiting to print." Then, as shown in FIG 7B, the CPU 128 changes the status 704 of JOB3 to "printing," and the status transitions to timing 602.
[0080] Here, when the recording operation is completed, the CPU 128 may change the deletion priority depending on the state of the job data (whether printing was completed normally, whether the user canceled printing midway, or whether printing was interrupted due to an error) at the end of the recording operation. For example, the job type 703 may be switched from "normal printing" to "secure printing."
[0081] When the recording operation is completed, the state transitions to timing 603, and the CPU 128 changes the state 704 of JOB3 to "waiting for deletion" as shown in Fig. 7(c). When it is changed to "waiting for deletion", the process proceeds from S801 to S802. In S802, it is determined that no new job has been received. Then, since the job management table 700 is in the state of Fig. 7(c), it is determined in S815 that there is no job that is "printing", and in S804 that there is no job that is "waiting to print", and the process proceeds to S807.
[0082] In S807, the CPU 128 determines whether or not a job whose job type 703 is "secure printing" and whose status 704 is "deletion pending" exists in the job management table 700. If it is determined that a job whose job type is "secure printing" and whose status is "deletion pending" exists, the process proceeds to S814, and if it is determined that a job whose job type is "secure printing" and whose status is "deletion pending" does not exist, the process proceeds to S808.
[0083] At timing 603 in FIG. 6, as shown in FIG. 7C, there is no job whose job type 703 is "secure printing" and whose status 704 is "deletion pending," so the process proceeds to S808.
[0084] In S808, the CPU 128 determines whether or not a job whose job type 703 is "secure printing" and whose status 704 is "waiting for deletion" exists in the job management table 700. If it is determined that a job which is "secure printing" and "waiting for deletion" exists, the process proceeds to S812, and if it is determined that a job which is "secure printing" and "waiting for deletion" does not exist, the process proceeds to S809.
[0085] At timing 603 in FIG. 6, as shown in FIG. 7C, there is no job whose job type 703 is "secure printing" and whose status 704 is "waiting to be deleted," so the process proceeds to S809.
[0086] In S809, the CPU 128 determines whether or not a job whose job type 703 is "normal printing" and whose status 704 is "deletion pending" exists in the job management table 700. If it is determined that a job whose job type is "normal printing" and whose status is "deletion pending" exists, the process proceeds to S813, and if it is determined that a job whose job type is "normal printing" and whose status is "deletion pending" does not exist, the process proceeds to S810.
[0087] At timing 603 in FIG. 6, as shown in FIG. 7C, there is no job whose job type 703 is "normal print" and whose status 704 is "deletion pending," so the process proceeds to S810.
[0088] In S810, the CPU 128 determines whether or not a job whose job type 703 is "normal printing" and whose status 704 is "waiting for deletion" exists in the job management table 700. If it is determined that a job which is "normal printing" and "waiting for deletion" exists, the process proceeds to S811, and if it is determined that a job which is "normal printing" and "waiting for deletion" does not exist, the process proceeds to S801.
[0089] At timing 603 in FIG. 6, as shown in FIG. 7C, there is JOB3 whose job type 703 is "normal print" and whose status 704 is "waiting for deletion," so the process proceeds to S811.
[0090] In S811, the CPU 128 changes the status 704 of JOB3, which is "waiting to be deleted," to "being deleted," as shown in Fig. 7(d), and proceeds to S801. At this time, the CPU 128 starts deleting the job data of JOB3, which is "waiting to be deleted." The CPU 128 overwrites the data in the storage area of the job data stored in the RAM 124 or the HDD 161, once or multiple times with a fixed hexadecimal value such as 0x00, 0xFF, or 0xAA, or a random number.
[0091] At timing 603 in Fig. 6, the CPU 128 starts deleting the job data of JOB3, whose status 704 is "waiting for deletion." At this time, as shown in Fig. 7(d), the CPU 128 changes the status 704 of JOB3 to "being deleted" and proceeds to S801.
[0092] Thereafter, the host I / F 127 receives JOB4 as a new job. It is assumed that JOB4 is received and saved at 10:15. The state transitions to timing 604. In S802, it is determined that a new job has been received, and in S803, although not shown in FIG. 7D, at this point in time, the state 704 of JOB4 becomes "waiting to print."
[0093] 7D, it is determined in S815 that there is no job in the "printing" state, and in S804 that there is a job in the "waiting to be printed" state, and the process proceeds to S805. In S805, since JOB3 in the "deleting" state exists, the process proceeds to S816.
[0094] In S816, CPU 128 changes the status 704 of JOB3, which is "being deleted," to "deletion pending," as shown in Fig. 7(e), and proceeds to S806. At this time, CPU 128 temporarily suspends the deletion of job data of the job, which is "being deleted." In this manner, in this embodiment, when the status of JOB3, a normal print job, is "being deleted," and a secure print job is subsequently received, the deletion of the job data of JOB3 is temporarily suspended, thereby starting recording of the secure print job, and making it possible to promptly start deletion of the job data of the secure print job after the recording operation is completed.
[0095] At timing 604 in Fig. 6, the deletion of job data of JOB3, whose status 704 is "deleting", is temporarily stopped. At this time, in consideration of the difference in confidentiality from normal print jobs, the deletion of job data may be temporarily stopped after overwriting the job data a predetermined number of times or more, for example, zero or more times for normal printing and one or more times for secure printing. At this time, the CPU 128 changes the status 704 of JOB3 to "deletion pending" as shown in Fig. 7(e) and proceeds to S806. In S806, the CPU 128 starts printing of JOB4, whose status 704 is "waiting to print", and proceeds to S801.
[0096] After that, when the recording operation is completed, the state transitions to timing 605, and the CPU 128 changes the state 704 of JOB4 to "waiting for deletion" as shown in FIG. 7E. When the state is changed to "waiting for deletion", the process proceeds from S801 to S802. In S802, it is determined that a new job has not been received. Then, since the job management table 700 is in the state of FIG. 7E, it is determined in S815 that there is no job in "printing", and in S804 that there is no job in "waiting for printing". Then, in S807, it is determined that there is no job in "secure printing" and "deletion pending", and the process proceeds to S808. In S808, since there is JOB4 with the job type 703 of "secure printing" and the state 704 of "waiting for deletion", it is determined that there is a job in "secure printing" and "waiting for deletion", and the process proceeds to S812.
[0097] In S812, the CPU 128 changes the status 704 of JOB4, which is "waiting to be deleted," to "being deleted," as shown in FIG. 7(f), and proceeds to S801. At this time, the CPU 128 starts deleting the secure printing job data that is "waiting to be deleted." The CPU 128 overwrites the data in the storage area of the job data stored in the RAM 124 or the HDD 161 with a fixed hexadecimal value such as 0x00, 0xFF, or 0xAA, or a random number, once or multiple times. At this time, the fixed value and the number of times to overwrite the data may be changed in consideration of the difference in confidentiality from normal printing.
[0098] At timing 605 in Fig. 6, the CPU 128 starts deleting the job data of JOB4, whose status 704 is "waiting for deletion." At this time, as shown in Fig. 7(f), the CPU 128 changes the status 704 of JOB4 to "being deleted" and proceeds to S801.
[0099] After that, when the job data deletion is completed, the state transitions to timing 606, and the CPU 128 changes the state 704 of JOB4 to "deletion completed" as shown in FIG. 7G. When the state is changed to "deletion completed", the process proceeds from S801 to S802. In S802, it is determined that a new job has not been received. Then, since the job management table 700 is in the state of FIG. 7G, it is determined in S815 that there is no job that is "printing", and in S804 that there is no job that is "waiting to print". Then, in S807, it is determined that there is no job that is "secure printing" and "deletion pending", and in S808, it is determined that there is no job that is "secure printing" and "waiting to delete", and the process proceeds to S809. In S809, since JOB3 that is a normal print job and "deletion pending" exists, the process proceeds to S813.
[0100] In S813, the CPU 128 changes the status 704 of JOB3, which is "deletion pending," to "deleting," as shown in FIG. 7G, and proceeds to S801. At this time, the CPU 128 resumes the deletion of job data of the normal print job, which is "deletion pending." When resuming job data deletion, the CPU 128 may record the number of times overwriting was performed when deferring deletion in S816, and resume job data deletion from the point where it was recorded. The CPU 128 may also restart job data deletion from the beginning.
[0101] 6, the CPU 128 resumes deleting the job data of JOB3, whose status 704 is "deletion pending." At this time, the CPU 128 changes the status 704 of JOB3 to "deleting," as shown in FIG 7(g), and proceeds to S801.
[0102] After that, when the job data deletion is completed, the state transitions to timing 607, and the CPU 128 changes the state 704 of JOB3 to "deletion completed". When it is changed to "deletion completed", the process proceeds from S801 to S802. In S802, it is determined that a new job has not been received. Then, since the job management table 700 is in a state in which the state 704 of JOB3 has been changed to "deletion completed" in FIG. 7(g), it is determined in S815 that there is no job that is "printing" and that there is no job that is "waiting to print" and in S804 that there is no job that is "secure printing" and "pending deletion" and in S808 that there is no job that is "secure printing" and "waiting to delete". Then, in S809, it is determined that there is no print job that is "normal printing" and "pending deletion" and the process proceeds to S810. In S810, it is determined that there is no job that is "normal printing" and "waiting to delete" and the process proceeds to S801.
[0103] As described above, according to this embodiment, if a secure print job is received while deleting job data of a normal print job, the job data of the secure print job is preferentially deleted when all jobs have been printed. With such a configuration, highly confidential print job data can be quickly deleted to a state where restoration is difficult. In addition, in this embodiment, whether or not the print data is securely printed is determined without user operation from attribute information added by the sender of the print data and the type of the print data, thereby improving convenience.
[0104] [Third embodiment] The third embodiment will be described below with respect to the differences from the first and second embodiments. In the second embodiment, a configuration was described in which, when a secure print job is received while deleting job data of a normal print job, the job data of the secure print job is preferentially deleted when all jobs have been printed. In this embodiment, when multiple jobs of the same job type are received in succession, a determination is made as to which job is to be preferentially deleted. As an example of such a case, a case in which a secure print job is received while a secure print job is being printed will be described below.
[0105] Fig. 9 is a time chart for explaining job control when a secure print job is received during printing of a secure print job. Fig. 10 is a diagram showing an example of a job management table for managing the status of a job in this embodiment. A job table 1000 includes information such as a job ID 1001, a job save time 1002, a job type 1003, a status 1004, a total level of secrecy 1005, a data size 1006, and a data update date and time 1007. (a) to (f) of Fig. 10 respectively show the status of the job management table at timings 901, 902, 903, 904, 905, and 906 in Fig. 9.
[0106] Hereinafter, with reference to FIGS. 9, 10 and 8, a process for determining which job is to be preferentially deleted when a secure print job is received during printing of another secure print job will be described.
[0107] 9, when the host I / F 127 receives a new job, the CPU 128 secures a job management table 1000 for managing the job status in a storage area of the RAM 124 or the HDD 161. The process proceeds from S801 to S802, and if it is determined in S802 that a new job has been received, the process proceeds to S803. In S803, the CPU 128 changes the status 1004 of JOB5 in the job management table 1000 in FIG. 10 to "waiting to print" as shown in FIG. 10(a), and the status transitions to the timing 902.
[0108] At timing 902 in Fig. 9, the CPU 128 determines in S815 that there is no job in the "printing" state, and determines in S804 that there is a job in the "waiting to print" state, and proceeds to S805. Since the job management table 1000 is in the state shown in Fig. 10(a), it is determined in S805 that there is no job in the "being deleted" state, and proceeds to S806. In S806, the CPU 128 changes the state 1004 of JOB5 in the job management table 1000 to "printing", starts printing JOB5, and proceeds to S801, as shown in Fig. 10(b). When the state is changed to "printing", the process proceeds from S801 to S802.
[0109] Thereafter, when the host I / F 127 receives a new job JOB6, it is determined in S802 that a new job has been received, and in S803 the CPU 128 sets JOB6 to "waiting to be printed" and proceeds to S815. Here, since JOB5 which is "being printed" exists, it is determined in S815 that a job which is "being printed" exists, and the process proceeds to S801.
[0110] When the printing operation of JOB5 is completed, the state transitions to timing 903, and the CPU 128 changes the state 1004 of JOB5 in the job management table 1000 to "waiting for deletion" as shown in FIG. 10C. When the state is changed to "waiting for deletion", the process proceeds from S801 to S802. In S802, it is determined that a "new job" has not been received, and the process proceeds to S815. In S815, it is determined that there is no job that is "printing", and the process proceeds to S804. In S804, since JOB6 that is "waiting to print" exists, it is determined that there is a job that is "waiting to print", and the process proceeds to S805. In S805, it is determined that there is no job that is "being deleted", and the process proceeds to S806. In S806, the CPU 128 changes the state 1004 of JOB6 in the job management table 1000 to "printing", and the process proceeds to S801, as shown in FIG. 10C.
[0111] When the printing operation of JOB6 is completed, the state transitions to timing 904, and the CPU 128 changes the state 1004 of JOB6 in the job management table 1000 to "waiting for deletion" as shown in Fig. 10(d). When it is changed to "waiting for deletion", the process proceeds from S801 to S802. In S802, it is determined that no new job has been received, and in S815, it is determined that no job is "printing", and the process proceeds to S804. In S804, it is determined that no job is "waiting to print", and the process proceeds to S807.
[0112] In S807, it is determined that there is no job that is both "secure printing" and "pending deletion", and the process proceeds to S808. In S808, since JOB5 and JOB6 that are both "secure printing" and "waiting for deletion" exist, it is determined that there is a job that is both "secure printing" and "waiting for deletion", and the process proceeds to S812.
[0113] In S812, since there are multiple jobs (JOB5, JOB6) that are "secure printing" and "waiting for deletion", the CPU 128 determines the job to be deleted based on parameters held on a data basis. In this embodiment, the CPU 128 determines JOB5, which is submitted first, as the job to be deleted based on the job save time 1002. However, the CPU 128 may determine the job to be deleted based on other criteria. For example, the CPU 128 may determine the job to be deleted based on any one of the total confidentiality 1005, the data size 1006, and the data update date and time 1007, or may determine the job to be deleted by combining the above parameters. The CPU 128 may determine the job to be deleted not as the job that is first, but as the job to be deleted. In addition, as a method of calculating the total confidentiality 1005, the CPU 128 may count the number of pages that contain the characters or image "confidential", or may count the number of occurrences. In addition, as a method of calculating the total confidentiality 1005, the CPU 128 may use a statistical value. For example, the average value of the number of occurrences per page may be calculated, or the median value may be calculated.
[0114] In S812, when the CPU 128 starts deleting the job data of JOB5 determined to be deleted, it changes the status 1004 of JOB5 in the job management table 1000 to "being deleted" as shown in FIG. 10(e) and proceeds to S801.
[0115] When the deletion of JOB5 is complete, the state transitions to timing 905, and the CPU 128 changes the state 1004 of JOB5 in the job management table 1000 to "deletion completed" as shown in Fig. 10(f). When the state is changed to "deletion completed", the process proceeds from S801 to S802. In S802, it is determined that no new job has been received, and the process proceeds to S815. In S815, it is determined that no job is "printing", and the process proceeds to S804. In S804, it is determined that no job is "waiting to be printed", and the process proceeds to S807. In S807, it is determined that no job is "secure printing" and "deletion pending", and the process proceeds to S808.
[0116] In S808, since JOB6 which is "secure printing" and "waiting for deletion" exists, the CPU 128 determines that a job which is "secure printing" and "waiting for deletion" exists, and proceeds to S812. In S812, as shown in Fig. 10(f), the CPU 128 changes the status 1004 of JOB6 in the job management table 1000 to "being deleted", and proceeds to S801. When the deletion of JOB6 is completed, the status transitions to timing 906, and the CPU 128 changes the status 1004 of job JOB6 in the job management table 1000 to "deletion completed".
[0117] As described above, according to this embodiment, when there are multiple job data with the same deletion priority, the job data to be deleted is determined based on the corresponding parameters for each job data "waiting for deletion." With such a configuration, it is possible to perform appropriate deletion control according to the application.
[0118] The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.
[0119] The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]
[0120] 100 Image processing device: 120 Printer controller: 124 RAM: 127 Host I / F: 128 CPU: 150 Printer engine: 161 HDD
Claims
1. A receiving means for receiving a job; a printing means for executing printing of the job data of the job received by the receiving means; a deletion means for deleting the job data after the printing means has finished printing; When the receiving means receives a second job after the printing of the first job data of the first job received by the receiving means is completed and before the first job data is deleted by the deleting means, when an attribute of the first job data corresponds to a first type of job data that should be deleted using secure erasure in which the first job data is overwritten once or multiple times with a value for invalidation after printing, and an attribute of the second job data of the second job corresponds to a second type of job data that should not be deleted using secure erasure, control is performed so that the first job data is deleted using the secure erasure before printing the second job data, when an attribute of the first job data corresponds to the second type of job data and an attribute of the second job data corresponds to the first type of job data, control is performed such that the deletion of the first job data using the secure deletion is suspended and the second job data is printed, and after the printing of the second job data is completed, the second job data is deleted using the secure deletion and then the first job data is deleted; a control means for controlling, when an attribute of the first job data and an attribute of the second job data are both attributes corresponding to the first type of job data, to suspend the deletion of the first job data using the secure erasure and to print the second job data, and, after the printing of the second job data is completed, to control to delete, using the secure erasure, one of the first job data and the second job data that has been determined to be deleted first based on a predetermined condition; having the predetermined condition is a condition based on the number of occurrences of confidential characters and / or images in each of the first job data and the second job data, A printing device comprising:
2. 2. The printing apparatus according to claim 1, wherein the attribute is a job type.
3. 3. The printing apparatus according to claim 1, wherein the predetermined condition is further based on at least one of a security attribute and a reception order.
4. The predetermined condition is a condition based on the occurrence count, the data size, and the data update date and time in each of the first job data and the second job data, 4. The printing device according to claim 1, wherein the control unit determines which job data to delete first by combining the number of occurrences, data size, and data update date and time of each of the first job data and the second job data.
5. A control method executed in a printing device, comprising: a receiving step of receiving a job; a printing step of executing printing of the job data of the job received in the receiving step; a deletion step of deleting the job data after the printing step is completed; When a second job is received in the receiving step after printing of the first job data of the first job received in the receiving step is completed and before the first job data is deleted in the deleting step, when an attribute of the first job data corresponds to a first type of job data that should be deleted using secure erasure in which the first job data is overwritten once or multiple times with a value for invalidation after printing, and an attribute of the second job data of the second job corresponds to a second type of job data that should not be deleted using secure erasure, control is performed so that the first job data is deleted using the secure erasure before printing the second job data, when an attribute of the first job data corresponds to the second type of job data and an attribute of the second job data corresponds to the first type of job data, control is performed such that the deletion of the first job data using the secure deletion is suspended and the second job data is printed, and after the printing of the second job data is completed, the second job data is deleted using the secure deletion and then the first job data is deleted; a control step of controlling to print the second job data while suspending the deletion of the first job data using the secure erasure when an attribute of the first job data and an attribute of the second job data both correspond to the first type of job data, and, after the printing of the second job data is completed, controlling to delete, using the secure erasure, one of the first job data and the second job data that has been determined to be deleted first based on a predetermined condition; having the predetermined condition is a condition based on the number of occurrences of confidential characters and / or images in each of the first job data and the second job data, A control method comprising:
6. A program for causing a computer to function as each of the means of the printing device according to any one of claims 1 to 4.