JP2010201776A - Image processing apparatus, control method of the same, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a mechanism which promptly prints printing data by anticipating beforehand the printing data processed with an image processing apparatus and developing it and making the preparation for printing. <P>SOLUTION: With the image processing apparatus which makes the printing data developed into image data and printed, a rendering reservation table and a printing frequency management table are prepared and managed based on history information of printing processing. When performing power-on or date change, the printing data for which rendering has not been carried out among the printing data managed by the rendering reservation table or the printing frequency management table is developed into raster data (S506). Then, if the printing data which should be printed by a user is chosen, the printing processing is performed using the raster data prepared beforehand. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an image processing apparatus having a function of reading and printing print data stored in a storage means, a control method therefor, and a program.

  Conventionally, it is known that print data that has been subjected to print processing is stored in a storage device even after the print processing is completed, and the print data is read from the storage device and reprinted. In particular, according to the technique described in Patent Document 1, after developing print data into bitmap image data, the bitmap image data is stored in a memory, and the image data is read out during reprinting. It is known to print.

JP-A-11-175290

However, in the case of Patent Document 1 described above, since all bitmap image data that has been subjected to printing processing is stored, there is a problem that a large-capacity memory is required.
Further, Patent Document 1 also describes that when the memory is full, the bitmap image data is erased from the oldest one. However, reprinting is not necessarily performed because it is old. For this reason, there may be a case where desired data has already been erased when reprinting is attempted.
Furthermore, for example, it is conceivable to store print data (or image data) in an external storage device after completion of the printing process.
However, in this case, it may take time to download print data (or image data) from an external storage device when reprinting is attempted. For this reason, as a result, printing cannot be performed promptly, and work efficiency is reduced.

  The present invention has been made in order to solve the above-described problems. To print print data quickly by predicting print data to be processed by an image processing apparatus in advance and preparing it in image data. The purpose is to provide a mechanism.

  It is another object of the present invention to provide a mechanism for printing print data quickly by predicting print data to be processed by an image processing apparatus in advance and obtaining it from an external apparatus.

  In order to achieve the above object, an image processing apparatus of the present invention includes a storage unit that stores print data, and a developing unit that executes a developing process that reads the print data stored in the storage unit and develops the image data. And a printing unit that executes a printing process based on the image data obtained by the developing unit, a management unit that manages history information of the printing process executed by the printing unit, and the management unit. And a control unit that causes the expansion unit to execute the expansion process based on history information.

According to the present invention, print data to be processed by the image processing apparatus can be predicted in advance, and can be quickly printed by developing the image data into image data.
In addition, print data to be processed by the image processing apparatus can be predicted in advance, acquired from an external apparatus, and prepared, so that the print data can be printed quickly.

It is a block diagram which shows the hardware of the image processing apparatus which shows this embodiment. It is a figure which shows the structure of the document file preserve | saved within an image processing apparatus. It is a figure which shows the document management state in the image processing apparatus which shows this embodiment. It is a figure which shows an example of the document management table managed by HDD shown in FIG. It is a flowchart of the data processing of the image processing apparatus which shows this embodiment. It is a flowchart of the data processing of the image processing apparatus which shows this embodiment. It is a figure which shows the document management state in the image processing apparatus which shows this embodiment. It is a figure which shows the operation history management table managed by HDD shown in FIG. It is a flowchart of the data processing of the image processing apparatus which shows this embodiment. It is a flowchart of the data processing of the image processing apparatus which shows this embodiment. It is a figure which shows the structure of the document file preserve | saved within an image processing apparatus. It is a flowchart of the data processing of the image processing apparatus which shows this embodiment.

Next, the best mode for carrying out the present invention will be described with reference to the drawings.
<Description of system configuration>
[First Embodiment]
FIG. 1 is a block diagram illustrating a hardware configuration of the image processing apparatus according to the present embodiment. In this embodiment, an MFP (Multi Function Peripheral) including a printer unit and a scanner unit is shown as an example of an image processing apparatus. The image processing apparatus has a function of receiving print data from a host computer via a network and developing it into bitmap format image data that can be printed by a printer unit. Here, the print data includes PDL data and PDF files based on the page description language. In the present embodiment, the print data is called a document file, and the print data is managed by the HDD 108.
In FIG. 1, reference numeral 100 denotes a controller that controls the entire image processing apparatus, and includes the following. The CPU 101 executes a software program for the image processing apparatus and controls the entire apparatus. The ROM 102 stores an apparatus boot program, fixed parameters, and the like. The RAM 103 is used for temporary data storage when the CPU 101 controls the apparatus.

  A hard disk drive (HDD) 108 is used for storing various data such as storage of print data printed by the printer 110, action history log, and index information associated with a document. Note that the image data in the present embodiment is data generated by processing (rendering processing) for developing print data into a raster image, and indicates data that can be processed by the printer 110.

The timer 112 manages the elapsed time in the timer process. The printer I / F control unit 104 controls the printer 110. The NVRAM 105 is a non-volatile memory and stores various setting values of the image processing apparatus.
The panel control unit 106 controls the operation panel 109 to display various information and input instructions from the user. The network I / F control unit 107 controls data transmission / reception with an external device on the LAN 111.
A CPU 101, ROM 102, RAM 103, HDD 108, timer 112, printer I / F control unit 104, NVRAM 105, panel control unit 106, and network I / F control unit 107 are connected to the bus 113. The CPU 101 transmits and receives control signals from the above devices connected to the bus 113 and data signals between the devices.

FIG. 2 is a diagram showing a configuration of a document file stored in the image processing apparatus shown in FIG. In this embodiment, document files are managed by the HDD 108 shown in FIG. Further, in this example, history information of print processing executed by the user is managed in association with the logged-in user.
In FIG. 2, reference numeral 201 denotes an image processing apparatus including an HDD 108 that can store a document and index information associated with the document.
Document files 202, 203, and 204 are stored in the HDD 108. The document files 202, 203, and 204 are composed of document data composed of a plurality of pages. Reference numeral 205 denotes an index information table associated with the document file 204. The index information includes information such as action classification, print settings, use date (day of week), and user name used.

Reference numeral 206 denotes a user whose user name is “B”, and when the user 206 prints the document file 204 stored in the image processing apparatus 201, the index information table 205 is updated to the contents of the index information table 207. In this example, the user 206 prints the document file 204 at an equal magnification on Thursday, June 14, 2007. As a result, the history by the user 206 is added to the index information stored in the image processing apparatus 201.
In the example illustrated in FIG. 2, when new information is added to the state of the index information table 205 of the document 204 by the printing operation with the user name “B”, the index information table 207 is updated.

  FIG. 3 is a diagram illustrating a document file management method in the image processing apparatus according to the present embodiment. In FIG. 3, raster data 301 is raster data generated by the CPU 101 using the RAM 103 to render the document file 204. The raster data 301 is image data that can be interpreted by the printer 110. The raster data is managed in association with the document file 204 that is the original data.

FIG. 4 is a diagram showing an example of a document management table managed by the HDD 108 shown in FIG. The document management table shown in FIG. 4A is a rendering reservation table, and manages document files and raster files by day of the week. For example, the row “Friday” shows the document 205 and raster data named “Raster_Fri 1”. This indicates that since the document 205 is frequently printed on Friday, it is necessary to prepare “raster_gold 1”, which is raster data corresponding to the document 205, every Friday. Yes.
The document management table shown in FIG. 4B manages the printing frequency of document files and raster files. In this example, in the rendering reservation table, documents printed on the same day for three or more consecutive weeks are listed. In addition, the file names when rasterized are stored in the listed documents are also stored in the same table. However, there is a restriction that only a maximum of three documents can be registered on one day of the week.
On the other hand, in the print frequency management table shown in FIG. 4B, the number of prints per month is managed separately for each document file, and the top three documents are listed.

5 and 6 are flowcharts illustrating an example of a data processing procedure of the image processing apparatus according to the present exemplary embodiment. The process shown in FIG. 5 corresponds to the preliminary process, and the process shown in FIG. 6 corresponds to the print process. Each step shown in the flowchart is realized by the CPU 101 shown in FIG. 1 loading a control program stored in the ROM 102 and HDD 108 into the RAM 103 and executing it.
In this embodiment, the CPU 101 identifies print data that is likely to be reprinted by the user based on the history information shown in FIG. 2, and the rendering reservation table shown in FIG. The history information management table shown in FIG. Then, the expansion of the print data is automatically performed in advance according to the procedure shown in FIG. 5, triggered by the power of the image processing apparatus being turned on or the date being changed.
First, in step S501 shown in FIG. 5, when the power of the image processing apparatus 201 is turned on or the date is changed, the process proceeds to step S502. In step S502, the CPU 101 accesses the rendering reservation table and the print frequency management table held in the HDD 108 which is a storage device in the image processing apparatus 201, and refers to the contents thereof.
Next, in step S503, the CPU 101 determines whether there is unnecessary raster data among the raster data held in the HDD 108 based on the contents of the rendering reservation table and the print frequency management table referenced in step S502. Determine.

Specifically, first, the rendering reservation table is referred to, and it is determined that the raster data of the document file that does not correspond to the day of the week on which the process is executed is unnecessary. That is, for example, assuming that processing is executed on Friday in the example shown in FIG. 4A, it is determined that raster data corresponding to the document 205 is necessary, and raster data corresponding to the document 204 is unnecessary. It will be judged.
Next, the print frequency management table is referred to, and it is determined that the raster data of the document file not included in the table is unnecessary. That is, in the example shown in FIG. 4B, it is determined that the raster data corresponding to the document aaa is necessary, and the raster data corresponding to the document bbb is determined to be unnecessary.
If it is determined in step S503 that unnecessary raster data does not exist, the process proceeds to step S505. If it is determined that unnecessary raster data exists, the process proceeds to step S504. In step S504, the raster data determined to be unnecessary is deleted (deleted). Here, it is assumed that the raster data determined to be unnecessary is erased from the HDD 108, but the data may not be actually erased but simply rendered unusable.
In step S505, the CPU 101 determines whether it is necessary to newly generate raster data based on the contents of the rendering reservation table and the print frequency management table referred to in step S502.

Specifically, referring to the rendering reservation table, when there is a document file corresponding to the day of the week on which the processing is being executed, the corresponding raster data is not held in the HDD 108, It is determined that it is necessary to generate raster data. That is, for example, assuming that processing is executed on Thursday in the example shown in FIG. 4A and raster data corresponding to the document 204 is not held, new raster data corresponding to the document 204 is generated. It will be judged that it is necessary to do.
Next, referring to the print frequency management table, it is necessary to generate raster data when there is a document file that is not included in the table and the corresponding raster data is not held in the HDD 108. judge. That is, in the example shown in FIG. 4B, if raster data corresponding to the document aaa is not held, it is determined that it is necessary to newly generate raster data corresponding to the document aaa. .

If it is determined in step S505 that it is not necessary to newly generate raster data, the process ends. If it is determined that new raster data needs to be generated, the process proceeds to step S506. In step S506, a document file determined to require raster data generation is read from the HDD 108, rendering processing is performed, and raster data is generated. The above corresponds to the pre-processing of print processing.
Next, a document file printing process will be described with reference to FIG. In step S601 shown in FIG. 6, when a user selects a document file held in the HDD 108 and instructs execution of print processing using the user interface displayed on the operation panel 109, the process proceeds to step S602.
In step S602, the CPU 101 determines whether raster data corresponding to the document file selected by the user has already been created. If the result of determination in step S602 is that raster data has been created, processing proceeds to step S604, and if not, processing proceeds to step S603. In step S603, the selected document file is read from the HDD 108, rendering processing is executed, and raster data is generated.

In step S604, raster data corresponding to the selected document file is read from the HDD 108, and printing processing by the printer 110 is executed. In subsequent step S605, the index information corresponding to the printed document file is updated by the method described with reference to FIG.
In step S606, based on the updated index information, it is determined whether or not the document file subjected to the printing process in step S604 is subjected to the printing process on the same day for three consecutive weeks. If the result of this determination is that printing has been performed on the same day of the week for three consecutive weeks, processing advances to step S607, and a new addition is made in the rendering reservation table of FIG.

  In subsequent step S608, the number of times the document file that has undergone the printing process in step S604 has been printed in one month is counted, and the number of times other document files recorded in the print frequency management table in FIG. 4B are printed. (Step S609). As a result of the comparison, if the number of times of printing of the document file subjected to the printing process in step S604 is larger than that of other documents, the process proceeds to step S610, and the document file subjected to the printing process in step S604 is newly added to the print frequency management table. To record.

In step S611, the rendering reservation table in FIG. 4A and the print frequency management table in FIG. 4B are referred to, and it is determined whether or not to save the raster data of the document file subjected to the printing process in step S604. Here, if it is recorded in at least one of the rendering reservation table and the printing frequency management table, it is determined that the raster data is stored, but it is determined that the raster data is stored only when it is recorded in the printing frequency management table. You may do it.
If it is determined in step S611 that the raster data is not to be saved, the process proceeds to step S612, and the raster data used for the printing process is deleted. On the other hand, if it is determined that the raster data is to be saved, the processing is terminated as it is.
Through the above processing, a document file that is highly likely to be instructed to be printed is automatically selected from the document files stored in the HDD 108, and raster data of the document file can be prepared in advance. . As a result, when the printing of the document file is instructed, the printing process can be executed promptly.
In other words, the document file recorded in the rendering reservation table or the print frequency management table can be printed immediately without executing the rendering process again when the document file is printed next time.
In the present embodiment, the behavior of a document is predicted by an algorithm such as “whether there is a document printed by the same processing method on the same day of the week for three consecutive weeks” or “how many times it is printed in one month”. Explained the case. However, the present invention is not limited to the above algorithm, and other modes may be used.

[Second Embodiment]
In the first embodiment, a case has been described in which rendering processing is performed in advance based on the operation history information or printing frequency of a document file managed in a storage device included in the image processing apparatus itself. Hereinafter, an example will be described in which document files stored in a storage device of another image processing device or a storage device on a network are acquired (downloaded) in advance and processed based on operation history information managed by the image processing device. .
In the above embodiment, the case where “history information” is managed as attribute information of print data (or image data) has been described. In this embodiment, an embodiment in which output preparation processing (rendering processing, download, etc.) is performed based on (operation) history information managed by the image processing apparatus will be described.

FIG. 7 is a diagram illustrating a document management state in the image processing apparatus according to the present embodiment. This example is an example of a network system in which an image processing apparatus can communicate with an external apparatus including a storage device via a network. In this embodiment, an example of an image processing apparatus connected to a network is shown as an external apparatus, but various information processing apparatuses such as a server and a PC may be used.
In FIG. 7, the image processing apparatus 701 is connected to the LAN 111, and can transmit and receive data to and from other devices connected to the LAN 111, for example, the image processing apparatus 702. The image processing apparatus 701 has a built-in HDD 108, and stores an operation history (action history) performed on the image processing apparatus 701 by a user and a document 705 in the HDD 108.
The image processing apparatus 702 is connected to the same network 111 as that of the image processing apparatus 701, and can exchange data with devices connected to the network 111.
The image processing apparatus 702 includes an HDD 703 for holding data therein, and a document file 704 and a document file 706 are stored in the HDD 703.
An arrow 707 indicates a state in which a document file 704 stored in the HDD 403 is transferred to the HDD 108 of the image processing apparatus 701 via the LAN 111 based on an instruction from a user who operates the image processing apparatus 701.

  FIG. 8 is a diagram showing an example of an operation history management table managed by the HDD 108 provided in the image processing apparatus 701 shown in FIG. In this example, the operation history stored in the HDD 108 of the image processing apparatus 701 is classified and managed for each action. Therefore, in the management table, a history in which the image processing apparatus 701 acquires the document file 704 from the image processing apparatus 702 and performs pull printing is managed.

  In FIG. 8, an operation history management table 801 is information stored in the HDD 108, and corresponds to a history of operation contents when the user executes the image processing apparatus 701 such as FAX transmission, BOX printing, and copying operation. To do. The operation history management table 801 manages the items of the action classification 802, the file path 803, the telephone number 804, and the date 805 as the action history.

Here, the action classification 802 classifies actions executed by the image processing apparatus 701 by FAX transmission, copy, BOX print, pull print, SEND, and the like. A file path 803 indicates the location of a FAX or printed document, and manages not only the image processing apparatus 701 but also an image processing apparatus 702 connected by the LAN 111 and a server (not shown). . A telephone number 804 is a destination telephone number when a FAX operation is performed. The date and time 805 is a time when FAX transmission, copy operation, print operation, and the like are performed.
Reference numeral 806 denotes an example of a file path, which indicates that a file “¥¥ image processing device 402 ¥ BOX No. 01 ¥ document 404” has been downloaded from another image processing device 702 and pulled printed.
In addition, the CPU 101 included in the image processing apparatus 701 prints the operation history management table 801 stored in the HDD 108 “whether there is a document printed by the same processing method on the same day of the week” or “every day at the same time” Analyzes using an algorithm such as “whether there is a document in progress”.

9 and 10 are flowcharts showing an example of a data processing procedure of the image processing apparatus showing the present embodiment. The process shown in FIG. 9 corresponds to the preliminary process, and the process shown in FIG. 10 corresponds to the print process. Each step shown in the flowchart is realized by the CPU 101 shown in FIG. 1 loading a control program stored in the ROM 102 and HDD 108 into the RAM 103 and executing it.
In the present embodiment, the CPU 101 identifies print data that is likely to be reprinted by the user based on the operation history management table 801 shown in FIG. Then, the document data download process is automatically performed in advance according to the procedure shown in FIG. 9, triggered by the power-on of the image processing apparatus or the date change.

First, in step S901 shown in FIG. 9, when the image processing apparatus 201 is turned on or the date is changed, the process proceeds to step S902. In step S902, the CPU 101 accesses the operation history management table 801 held in the HDD 108 which is a storage device in the image processing apparatus 201, and refers to the contents.
Next, in step S903, the CPU 101 determines whether there is unnecessary download data among the download data held in the HDD 108 based on the contents of the operation history management table referred to in step S902.
Specifically, the operation history management table is referred to, and it is determined that the data of the document file that has not been printed on the day of the week on which the process is executed is unnecessary. Further, it may be determined that data of a document file in which a predetermined number or more records are not recorded in the operation history management table is unnecessary.

If it is determined in step S903 that unnecessary download data does not exist, the process proceeds to step S905. If it is determined that unnecessary download data exists, the process proceeds to step S904. In step S904, the download data determined to be unnecessary is deleted. Here, it is assumed that the process of erasing download data determined to be unnecessary from the HDD 108 is performed, but the process of making the data unusable instead of actually erasing the data may be performed.
In step S905, the CPU 101 determines whether a new document file needs to be downloaded based on the contents of the operation history management table 801 referred to in step S902.

  Specifically, referring to the operation history management table, if there is a document file that has been printed on the day of the week on which the process is being executed and the data is not held in the HDD 108, the document It is determined that the file data needs to be downloaded. In addition, when there is a document file in which a predetermined number or more records are recorded in the operation history management table and data is not downloaded, it may be determined that the document file data needs to be downloaded. .

If it is determined in step S905 that it is not necessary to download a new document file, the process ends. If it is determined that a new document file needs to be downloaded, the process proceeds to step S906. In step S906, the data of the document file that is determined to be required to be downloaded is downloaded. The above corresponds to the pre-processing of print processing.
Next, a document file printing process will be described with reference to FIG. In step S1001 shown in FIG. 10, when a user selects a document file held in the HDD 108 and instructs execution of a printing process using the user interface displayed on the operation panel 109, the process proceeds to step S1002.

In step S1002, the CPU 101 determines whether data corresponding to the document file selected by the user has already been downloaded. If the result of determination in step S1002 is that data has been downloaded, processing proceeds to step S1004, and if it has not been created, processing proceeds to step S1003. In step S1003, the data of the selected document file is downloaded.
In step S <b> 1004, data corresponding to the selected document file is read from the HDD 108 and printing processing by the printer 110 is executed. In step S1005, the operation history management table 801 is updated.

In step S1006, based on the updated operation history management table 801, it is determined whether or not the document file that has undergone the printing process in step S1004 has been printed on the same day of the week for three consecutive weeks. If the result of this determination is that printing has been performed on the same day of the week for three consecutive weeks, the processing is terminated as it is. On the other hand, if the printing process is not performed on the same day of the week for three consecutive weeks, the process proceeds to step S1007, and the number of times the document file subjected to the printing process in step S1004 is printed in one month is counted. The number of times of printing of other document files recorded is compared (step S1008). As a result of the comparison, if the number of times of printing of the document file that has been subjected to the printing process in step S1004 is larger than that of other documents, the process is terminated as it is. As a result of the determination in step S1008, if it is determined that the printing frequency is not higher, the process proceeds to step S1009, and the download data used for the printing process is deleted.
Through the above processing, it is possible to automatically download the document file data that is highly likely to be instructed to be printed out of the document files stored in the HDD 108 and prepare the document file data in advance. it can. As a result, when the printing of the document file is instructed, the printing process can be executed promptly.

[Third Embodiment]
In the second embodiment, a case has been described in which behavior prediction is performed using the operation history management table 501 of the entire image processing apparatus. On the other hand, an operation history (operation log) is held for each user, and behavior prediction is performed for each logged-in user. And when user ID is input, it is good also as a structure which displays the recommended operation screen adapted to the user ID based on the action required prediction result. The embodiment will be described below.

FIG. 11 is a diagram illustrating an example of an operation history table managed by the image processing apparatus according to the present embodiment. In this example, the operation history table is managed separately for each user who can be authenticated. The operation history tables 1103 to 1105 are managed in a user log area in the storage medium 1102 provided in the image processing apparatus 1101. Further, although the HDD 1102 is configured by the HDD 108 illustrated in FIG. 1, for example, other storage media may be used. In addition to the user log area, the recording medium 1102 has a system data area and a document data area.
In FIG. 11, reference numeral 1101 denotes an image processing apparatus, which has hardware resources equivalent to those of the image processing apparatus shown in FIG. An HDD 1102 is built in the image processing apparatus 1101 and stores system data, document data, and user logs in the HDD 1102.
Reference numeral 1103 denotes an example of user A's operation log, which is stored in the HDD 1102. In particular, the operation log of user A indicates that there are many copies and fax operations in the action classification. Reference numeral 1104 denotes an example of the operation log of the user B, which is stored in the HDD 1102. In particular, this operation log of user B indicates that there are many BOX prints in the action classification.
Reference numeral 1105 denotes an example of the operation log of the user C, which is stored in the HDD 1102. In particular, the operation log of user C indicates that there are many copies in the action classification.

FIG. 12 is a flowchart illustrating an example of a data processing procedure in the image processing apparatus according to the present embodiment. This example is a processing example for managing a user operation history. Each step is realized by the CPU 101 shown in FIG. 1 loading a control program stored in the ROM 102 and HDD 108 into the RAM 103 and executing it.
First, in step S <b> 1201, the user A operates the operation panel 109 to input user ID authentication information to the image processing apparatus 1101 and log in to the image processing apparatus 1101.

In step S1202, when the user makes a setting on the operation panel 109 and presses the start key, the CPU 101 executes image processing according to the set mode. Here, if it is the user A, a FAX transmission process will be performed. When executing FAX transmission, the user determines whether or not the document file to be transmitted may be specified as A by specifying the document file to be transmitted as A from the FAX transmission history registered in the operation log. You may contact us.
In step S1203, the CPU 101 additionally registers an action classification, a file name, and the like in the operation history of the user in the storage medium 1102 in accordance with the image processing function executed in step S1014.

In step S <b> 1204, the image processing apparatus 1101 calculates the usage frequency for each function based on the additionally registered operation history, and stores it in the operation history of the user as an analysis result of action classification of the operation history. Then, this process ends.
As described above, by managing the history information separately for each user, the selection of the document file that should hold the raster data or the download data described in the first embodiment or the second embodiment is performed with higher accuracy. be able to.
The object of the present invention can also be achieved by executing the following processing. That is, a storage medium that records a program code of software that realizes the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU, MPU, etc.) of the system or apparatus is stored in the storage medium. This is the process of reading the code.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code and the storage medium storing the program code constitute the present invention.

101 CPU
102 ROM
103 RAM
108 HDD
109 Operation Panel 110 Printer 112 Timer

Claims (8)

Storage means for storing print data;
A developing unit that executes a developing process of reading the print data stored in the storage unit and developing the print data into image data;
Printing means for executing a printing process based on the image data obtained by the developing means;
Management means for managing history information of print processing executed by the printing means;
Control means for causing the expansion means to execute the expansion process based on history information managed by the management means;
An image processing apparatus comprising:   The image processing apparatus according to claim 1, wherein the expansion process is a process of generating raster data by executing a rendering process on print data stored in the storage unit. An authentication unit for authenticating the user;
The image processing apparatus according to claim 1, wherein the management unit manages the history information separately for each user authenticated by the authentication unit.   The image processing apparatus according to claim 1, wherein the storage unit stores print data acquired from an external apparatus connected to the image processing apparatus via a network.   The control unit selects print data having a high printing frequency from print data stored in the storage unit based on the history information managed by the management unit, and performs the expansion processing of the print data. The image processing apparatus according to claim 1, wherein the image processing apparatus is executed by a developing unit.   The control unit selects, based on the history information managed by the management unit, print data that is periodically subjected to print processing from print data stored in the storage unit, The image processing apparatus according to claim 1, wherein the expansion unit executes data expansion processing. A control method for an image processing apparatus comprising: storage means for storing print data; and expansion means for executing expansion processing for reading the print data stored in the storage means and expanding the image data into image data,
A printing process for executing a printing process based on the image data obtained by the developing means;
A management process for managing history information of the printing process executed in the printing process;
Based on the history information managed in the management step, the control step for causing the expansion means to execute the expansion processing,
An image processing apparatus control method comprising:   A program for causing a computer to execute the control method of the image processing apparatus according to claim 7.

Images