JP2004128708A - Image processing apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image processing apparatus for performing print processing on the basis of recall data generated by copy processing on other MFP on a network. <P>SOLUTION: A flowchart denoting control contents performed by a control section in an operation of memory recall print includes steps of: (S4) storing image data produced in a process of copy processing in two kinds of data forms, that is, scanner data and print data, and registering them to a recall data management table; (S5) informing the other MFP about registration of new recall data; (S7) discriminating presence / absence of recall data in its own apparatus when it is discriminated that a memory recall print operation is made (Yes in step S1 and No in step S2); (S9) inquiring of the other MFP when no recall data exist in its own apparatus; (S14) discriminating whether print data can be used by its own apparatus when the recall data exist; (S15) requesting the print data when the print data can be used: (S18) or (S20) requesting recall data of a data form other than that of the print data to the other MFP when the print data cannot be used; and (S6) performing the print processing on the basis of the recall data. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an image processing apparatus that can be connected to a network, and more particularly, to an image processing apparatus that can output a memory recall.
[0002]
[Prior art]
In recent years, digital copiers and image forming apparatuses such as printers that can also be used as printers in many workplaces, computers such as servers that manage image information, and the like are used by being network-connected to a plurality of client terminals. Is becoming more common.
[0003]
On the other hand, when a copy process is performed, the print data is stored in an internal memory, and thereafter, the stored print data is read out from the memory and printed out (hereinafter, referred to as a “memory recall function”). Digital copiers equipped with are being developed. According to this memory recall function, a document once read can be printed out without reading it again, which is very convenient when, for example, the number of copies is to be added later.
[0004]
In order to further utilize the functions of the network, the applicant of the present application receives print data instructed to print from a client terminal such as a PC in an environment in which a plurality of digital copying machines are connected to the network, and performs printing based on the print data. While executing the operation, the print data is temporarily stored in the print server, and another digital copying machine on the network acquires the print data and executes printing by memory recall (hereinafter, referred to as “memory recall print”). A printing system has been devised (see Patent Document 1).
[0005]
By sharing the image data to be subjected to memory recall (hereinafter abbreviated as “recall data”) in this manner, even if the digital copier is not the first digital copier to be printed out, the nearest digital copier can easily be used. It is very convenient because memory recall printing is possible.
[0006]
[Patent Document 1]
Japanese Patent Application Laid-Open No. H11-2325205
[0007]
[Problems to be solved by the invention]
However, in the print system disclosed in the above publication, the data to be subjected to the memory call is only the print data transmitted from the client terminal, the image information source is limited, and the usability is not always good.
[0008]
The present invention has been made in view of such a problem, and image information other than print data once processed by one image processing device on a network can be easily used by another image processing device. It is an object to provide an image processing device.
[0009]
[Means for Solving the Problems]
In order to achieve the above object, the present invention provides an image processing apparatus connectable to a network, wherein a storage unit stores one image information in two or more types of data formats,
Transmission request receiving means for receiving a transmission request for image information from another device on the network, and one of the two or more data format image information stored in the storage means based on the received transmission request Transmitting means for transmitting the image information in the format to the requesting apparatus.
[0010]
As described above, one image information is stored in two or more types of data formats, and transmitted in one data format in response to a transmission request of the other device, a data format that can be output by the other device as the one data format Can be included.
Here, “two or more data formats for one image information” refers to image data generated in the course of a specific image processing and having a different data format. For example, if the image information is obtained by copying the original, the format of the RGB image data obtained by scanning the original and the output means of its own device after further processing this data For example, if the output unit is an electrophotographic printer, the data format may be cyan, magenta, yellow, or black print data. The data format in the case where the image information is print data transmitted from the client terminal means the print data and print data obtained by subjecting the print data to data output.
[0011]
Further, the present invention is an image processing apparatus connectable to a network,
An output request receiving unit for receiving an image information output request; an inquiry unit for inquiring another device on the network about the presence or absence of the corresponding image information based on the received output request; Is received in two or more types of data formats, an image of one of the two or more types of image information is transmitted to the device that transmitted the response. It is characterized by comprising transmission request means for requesting transmission of information, receiving means for receiving image information transmitted from the other device, and output means for outputting the received image information.
[0012]
As described above, when another device has one image information in two or more types of data formats, a request is made to transmit the image information in one data format. A request in a suitable data format becomes possible, and the output of information in another device becomes possible in its own device.
Here, it is desirable that the specific one data format is a data format suitable for an output function of the output unit. As a result, the image information can be output by the own device.
[0013]
Here, it is desirable that the image information transmitted from the other device is the most recently processed image information among the image information processed by the devices on the network. In this way, if the operator who has requested the copy processing or the print processing wants to immediately output the image information related to the processing again, it takes time to select the corresponding image information. Disappears.
[0014]
Further, the present invention includes identification information receiving means for receiving identification information associated with the image information, and the transmission requesting means includes image information selected by an operator from image information associated with the received identification information. And requesting another device on the network to transmit the image information in the one data format.
[0015]
As described above, the image information is stored in association with the identification information. Therefore, even if a plurality of pieces of image information are stored on the network, the image information desired to be output based on the identification information input by the operator is stored. Can be easily selected.
[0016]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment in which the image processing apparatus according to the present invention is a multi-function digital copying machine (Multiple Function Peripheral: hereinafter simply referred to as “MFP”) will be described with reference to the drawings.
<First embodiment>
(1) Image processing system configuration
First, an overall configuration of an image processing system including an MFP according to the present embodiment (hereinafter, simply referred to as “system”) will be described.
[0017]
FIG. 1 is a diagram illustrating an example of the configuration of the present system. As shown in FIG. 1, the system includes MFPs 11 to 14, printers 21 and 22, client terminals 31 to 33, and a print server 40, which are connected via a LAN (Local Area Network) 50. The number of MFPs, printers, client terminals, servers, and the like is not limited to the number shown in FIG. 1, and any number can be connected.
[0018]
Each of the MFPs 11 to 14 is, for example, a digital color copying machine, and includes a document reading unit and an image forming unit. In addition to a normal copy function, the MFP 11 to 14 print jobs in response to requests from client terminals 31 to 33. Is performed.
FIG. 2 is a schematic diagram illustrating a configuration of the MFP 11. The other digital copying machines 12 to 14 have substantially the same configuration.
[0019]
As shown in FIG. 1, the MFP 11 includes a document reading unit 100, a printer unit 200, and a control unit 300. The document reading unit 100 includes an automatic document feeder (ADF) 110 and a scanner unit 120. The ADF 110 automatically sends the documents placed on the document tray 111 one by one to the platen glass 121 of the scanner unit 120. The scanner unit 120 scans a document surface on the platen glass 121 by moving a scanner 122 equipped with an exposure lamp. Light reflected from the document is guided to the color CCD image sensor 123 via a plurality of reflection mirrors, converted into R, G, and B image signals, and transmitted to the control unit 300.
[0020]
The image signal of each color is subjected to various kinds of signal processing in the control unit 300 and is converted into image data of four reproduced colors of C (cyan), M (magenta), Y (yellow), and K (black). . First, for example, the laser diode 201 is driven based on the cyan image data to form an electrostatic latent image on the surface of the photosensitive drum 203, and this is developed with the cyan toner of the developing unit 210 to develop the latent image of the color. A toner image is formed on the photosensitive drum 203. On the other hand, transfer paper of an appropriate size is supplied from the paper supply unit 230, is held on the peripheral surface of the intermediate transfer drum 220, and the toner image on the photosensitive drum 203 is transferred onto the transfer paper. This operation is repeatedly executed for the subsequent image data of magenta, yellow, and black. After the four color toners are transferred onto one sheet in a multiplex manner, the sheet is peeled off from the intermediate transfer drum 220, heat-pressed in the fixing unit 240, and discharged onto the discharge tray 250.
[0021]
An operation panel 90 (see FIG. 10) for allowing the operator to make a predetermined input is provided at an easily operable position on the front surface of the scanner unit 100.
The operation panel 90 is provided with a display unit 91 having a transparent touch panel disposed on the surface of a liquid crystal display panel, ten keys 92 for inputting the number of copies, etc., a start button 93 for starting a copy operation, and the like. Various setting screens can be displayed on the screen, and various copy modes can be input by pressing buttons and the like displayed on the screen, and necessary messages can be displayed as described later. It has become.
[0022]
Returning to FIG. 1, the client terminals 31 to 33 and the print server 40 each include a CPU and a CPU main body including a RAM, a ROM, an EEPROM, a hard disk device (HDD), a monitor device, and input devices such as a keyboard and a mouse. A network communication program and other necessary control programs are installed, connected to other terminals and MFPs 11 to 14 by an existing communication protocol (such as TCP / IP), Can be transmitted and received.
[0023]
Hereinafter, the client terminal and the print server are simply referred to as “PC” and “server”, respectively.
In this specification, “print data” refers to data indicating image information to be formed by the MFP and the printer, which is transmitted together with a print request from the PC to the MFP and the printer, and is usually PDL (page description). Language) data format.
[0024]
The “scanner data” indicates R, G, and B image data of a document read by the scanner.
Further, "print data" refers to data obtained by subjecting the print data or scanner data to data processing and converting the data for image output in the own apparatus. Details will be described later.
(Configuration of Control Unit of MFP 11)
FIG. 3 is a block diagram illustrating a configuration of the control unit 300 of the MFP 11.
[0025]
As shown in the figure, the control unit 300 includes a main control unit 400, an image reading control unit 500, a printer control unit 600, a communication control unit 700, and the like.
The main control unit 400 executes signal processing of image information, sends various instructions to the control units 500, 600, and 700, and controls the MFP as a whole to operate smoothly. It comprises a processing unit 410, a second signal processing unit 430, a memory unit 440, a bitmap data creation unit 450, a CPU 460, and the like. The CPU 460 temporarily stores a copy mode set from the operation panel 90, a RAM 461 serving as a work area when executing a program, a ROM 462 storing a control program in the main control unit 400 and initial values of various control parameters, and An EEPROM 463 in which a recall data management table described later is stored is connected.
[0026]
The first signal processing unit 410 includes an A / D conversion unit 411, a shading correction unit 412, and a density conversion unit 413.
The image signal photoelectrically converted by the CCD image sensor 122 of the scanner unit 120 (FIG. 2) is converted into R, G, B multi-value digital image data by an A / D conversion unit 411, and a shading correction unit at the next stage is provided. At 412, a known shading correction for correcting output unevenness caused by illuminance unevenness of the exposure lamp and sensitivity unevenness of the CCD image sensor 122 itself is performed. The reading operation of the original by the scanner unit 120 is controlled by the image reading control unit 500.
[0027]
Since the image data after the shading correction is still the reflectance data of the original, after being converted into the actual density data by the density conversion unit 413, one page of image data for each of the R, G, and B color components is obtained. , Are once written to the frame memory 420 and stored in the memory unit 440.
The RGB image data read at the scanner unit 120 and processed at the first signal processing unit 410 in this manner is hereinafter referred to as “scanner data”. The scanner data is a format of image data representing image information together with print data and print data described later.
[0028]
The second signal processing unit 430 includes a color correction unit 431 and an MTF correction unit 432, and further performs data processing on the scanner data.
The color correction unit 431 converts the scanner data including the R, G, and B density data into C, M, Y, and K density data that are reproduction colors based on predetermined parameters provided from the CPU 460.
[0029]
Specifically, based on the density data of R, G, and B, black addition processing (BP processing) is performed in which the density data having a predetermined ratio α among the common density values of the density data is set as the black density data K. On the other hand, undercolor removal processing (UCR processing) is performed in which the black density data K of a predetermined ratio β is subtracted from the density data of each color. Further, using the masking coefficient, the density data of each color of R, G, and B after the UCR process is linearly corrected to obtain density data C, M, and Y of the reproduced color (masking process).
[0030]
The C, M, Y, and K density data of the reproduced colors generated in this manner are output to an MTF (spatial frequency) correction unit 432, and subjected to MTF correction.
The MTF correction unit 432 selects an appropriate two-dimensional spatial filter on the image data output from the color correction unit 431 based on the MTF correction conditions specified by the CPU 460, and performs well-known edge enhancement processing or smoothing processing. Do.
[0031]
The above α and β, the masking coefficient, the MTF correction conditions, and the like are used to reproduce an image in a central portion of image formation such as a photosensitive drum, a developing unit, and a transfer unit of the printer unit 200 (hereinafter, referred to as a “printer engine”). An optimum value is set in consideration of characteristics.
In the second signal processing unit 430, the image data subjected to the necessary correction is stored as print data in the memory unit 440, read out in synchronization with the print operation in the printer unit 200, and stored in the printer control unit 600. To a laser diode drive circuit (not shown).
[0032]
Document reading control section 500 controls each operation of ADF 110 and scanner section 120 when reading a document.
The printer control unit 600 controls the operation of the printer unit 200, and controls the output of the laser diode 201 based on the image data output from the main control unit 400. , The operations such as the rotation of the photosensitive drum 203 and the transfer drum 220 and the application of a voltage to each charger are controlled in a unified manner so as to execute image formation.
[0033]
The communication control unit 700 establishes connections with other MFPs 12 to 14, PCs 31 to 33, the server 40, and the like via the LAN 50 based on TCP / IP (Transmission Control Protocol / Internet Protocol), and executes data transmission and reception. In the present embodiment, for example, FTP (File Transfer Protocol) or the like is used as a protocol for transmitting data to another terminal. Further, the communication control unit 700 includes a communication interface such as a LAN board compatible with a predetermined network standard.
[0034]
Upon receiving a print job from any of the client terminals 31 to 33, the communication control unit 700 notifies the main control unit 400 of the fact and sends print data related to the print job to the bitmap data creation unit 450. . Since the print data is sent from the client terminal in a PDL (Page Description Language) data format such as PostScript, the bitmap data generation unit 450 converts this into R, G, B bitmap data. The print data is temporarily stored in the frame memory 420, converted into C, M, Y, and K print data in the second signal processing unit 430 and stored in the memory unit 440, and then sent to the printer control unit 600 for print processing. Is executed.
[0035]
At this time, the print data is stored in the memory unit 440 in the PDL format.
Note that the control units 500, 600, and 700 other than the main control unit 400 also include a CPU and a ROM therein, and execute respective controls based on a control program stored in the ROM.
[0036]
(Control Contents in Control Unit 300)
Hereinafter, the control contents of the control unit 300 will be described with reference to flowcharts.
FIG. 4 is a flowchart showing the control contents of control unit 300 when the operator causes MFP 11 to execute copying or memory recall printing.
[0037]
First, it is determined whether or not the start button 93 (FIG. 10) has been pressed by the operator (step S1). If it is determined that the start button 93 has been pressed, then the document on the document tray 111 of the ADF 110 or the platen glass 123 Is determined (step S2). This can be easily determined by detecting the presence or absence of the document by a document detection sensor including a photoelectric sensor or a limit switch installed at each location.
[0038]
If an original is detected, it is determined that the operator wants to perform a copy process of the original, and the original is scanned by the scanner unit 120 (step S3), and the obtained image signal is sent to the main control unit. 400 to process the image signal, store the two data formats (scanner data and print data) of the image information obtained in the course of this process in its own memory unit 440, and recall the data in the EEPROM 463. That fact is registered in the data management table T1 (steps S4, S5).
[0039]
FIG. 5 is a diagram illustrating an example of the recall data management table T1. When the copy processing is performed, two types of scanner data and print data are registered in the column of the data format of the image information stored as shown in FIG. Further, a memory address on the memory unit 440 indicating a storage position of image data of each data format and a registration date thereof are registered in corresponding columns. If a print job is received from a client terminal and print processing is executed, two types of print data, print data and print data, are registered.
[0040]
Returning to FIG. 4, in the next step S5, the fact that the recall data has been registered is notified to the other MFPs 12 to 14 via the LAN 50.
Thereafter, the printer unit 200 is controlled to execute a printing process for forming an image on a sheet based on the print data (step S6).
If it is determined in step S2 that there is no original, it is considered that there is a request for memory recall printing from the operator, and the process proceeds to step S7 to determine whether there is recall data in the own apparatus. (Step S7). This can be easily determined from the registered state of the recall data management table T1 in FIG.
[0041]
If the recall data is registered in the own device, the print data of the recall data is read from the memory unit 440, and the printing process is executed based on the read data (steps S8 and S6). The reason for selecting the print data format in this manner is that the print data is signal-processed by the control unit 300 of the own apparatus, so that the print data can be used as it is and the print processing can be performed. This is because there is no need to perform the processing again in the second signal processing unit 430.
[0042]
If the recall data has not been registered in the own apparatus, it is sequentially inquired via the LAN 50 to the other MFPs 12 to 14 whether or not the recall data has been registered (step S9).
For example, when the MFP 12 is first inquired and there is no recall data (step S10: No, S11: No), the display unit 91 of the operation panel 90 of the MFP 11 indicates that there is no recall data in the MFP 12. The current state is displayed, and another MFP 13 is inquired (step S9).
[0043]
When all the other MFPs 12 to 14 are inquired and recall data is not registered in all of them (step S10: No, S11: Yes), the display unit 91 displays "No recall data exists". (Step S13), the control operation in the memory recall print processing ends. For example, each of the MFPs 11 to 14 initializes the memory when the power is turned on. If the print processing and the copy processing are not performed in any of the MFPs after the respective power-ups, all the MFPs 11 to 14 are initialized as described above. Is determined that there is no recall data.
[0044]
If a response indicating that the recall data has been registered is received from another MFP (for example, the MFP 12) (step S10: Yes), then the recall data of the MFP 12 is changed to a print data format. It is determined whether the device can be used as it is (step S14).
As will be described later, the other MFPs 12 to 14 that have received the inquiry about the presence or absence of the recall data, if there is recall data in the own device, the data format and the model name of the own device together with the reply that the recall data exists. The MFP 11 that has received the response, if the model name included in the response is the same as the model name of its own device, prints the data of the other MFP. Judge that it can be used. Note that the model name of each of the MFPs 11 to 14 is stored in advance in a nonvolatile memory such as a ROM of each control unit at the time of manufacture or the like.
[0045]
As described above, the print data is generated by the second signal processing unit 430 based on the parameters corresponding to the reproduction characteristics in the printer unit of the own device. Therefore, when the model name is the same, the printer engine is also the same. This is because it is considered that the same reproducibility can be obtained even if the print data generated by another MFP is used and printed by the own apparatus.
[0046]
Therefore, even if the model name and, in some cases, the maker are different, as long as the printer engine is the same, it can be said that the print data is compatible. Therefore, the compatible model is registered in advance and other models are registered. If the MFP matches the registered model, it may be determined that the print data is usable.
As described above, when it is determined that the print data of the other device can be used by the own device, the MFP 11 requests the MFP 12 having the recall data to transmit the recall data in the format of the print data (step In step S15, when the print data is received (step S16), a print process is executed based on the print data (step S6).
[0047]
Conversely, if the model name of the MFP 12 having the recall data is different from its own device, it is determined “No” in step S14, and in the next step S17, another data format included in the recall data is determined. It is determined whether or not there is print data, that is, whether or not the recall data is data obtained by the print processing.
[0048]
If the data format is print data, the print data is requested from the MFP 12, the print data transmitted from the MFP 12 is received in response to the request, and the printing process is executed based on the print data (step S18, S19, S6).
This print data is usually a data format common to printers according to a predetermined standard as PDL, and is data before data processing by the second signal processing unit. Even if is used as it is, the problem as in the above print data does not occur.
[0049]
If it is determined in step S17 that the recall data does not have the data format of the print data, the recall data is obtained by the copy process, and is stored in the data format stored together with the print data. Is the scanner data, the MFP requests the MFP 12 for the scanner data, and executes the printing process based on the scanner data received from the MFP 12 (steps S20, S21, S6).
[0050]
Like the print data, the scanner data is data before being processed by the second signal processing unit. Therefore, data processing dependent on the reproduction characteristics of the printer engine is not added, and the scanner data of another MFP is used as it is. This is because, if print data is generated using parameters corresponding to the printer engine of the apparatus, there is no problem in image reproduction.
[0051]
Thus, the control operation at the time of memory recall printing is completed.
FIG. 6 is a flowchart illustrating a control operation in control unit 300 when print processing is executed in MFP 11.
First, it is determined whether or not a print job has been received from any of the PCs 31 to 33 via the communication control unit 700 (step S22). It is stored in the memory unit 440 and registered in the recall data management table T1 (step S23). The print job received from the PC includes print data and a header. Since the header includes a print request command, the determination in step S22 can be easily performed by detecting the command.
[0052]
Then, the fact that new recall data has been registered is notified to the other MFPs 12 to 14 via the LAN 50, and a printing process is executed based on the received print data (steps S24 and S25).
FIG. 7 is a flowchart of a response process executed in the control unit of the partner MFP that receives various requests from the MFP that has received the memory recall print operation. Here, a case will be described as an example where MFP 11 receives a memory recall print operation and MFP 12 receives various requests from MFP 11 and responds.
[0053]
The control unit of the MFP 12 first determines whether or not any information has been received from the MFP 11 (step S31), and if so, analyzes what the received content is (steps S32 to S36). A corresponding response is made (steps S37 to S43).
That is, if the received content is a notification that new recall data has been registered in the MFP 11 (see step S5 in FIG. 4 and step S24 in FIG. 6) (step S32), the own recall data management table Referring to T1, it is determined whether or not the recall data is in the own device, and if so, the registration of the recall data is deleted, and the recall data in the unit memory is set to a state in which the recall data can be erased or overwritten (step S37: Yes, step S38).
[0054]
As a result, only the recall data in the MFP that has executed the most recent copy processing or print processing is stored, and the other recall data is deleted. Therefore, only the most recent recall data is always stored on the network. On the MFPs 11 to 14.
If it is determined in step S33 that a confirmation request for the presence or absence of recall data (see step S9 in FIG. 4) has been received from MFP 11, it refers to its own recall data management table T1 to determine whether there is recall data. Confirmation is performed (step S39), and the confirmation result is transmitted to MFP 11 as recall data presence / absence transmission information (step S40). At this time, if the recall data is registered in the own device, the registration date and the model name of the own device are transmitted to the MFP 11 together.
[0055]
If it is determined in step S34 that a print data transmission request (see step S15 in FIG. 4) has been received from the MFP 11, it refers to its own recall data management table T1 and stores the data in the memory address of the registered print data. The print data is read from the memory unit based on the data and transmitted to the MFP 11 (step S41).
[0056]
Similarly, if it is determined in step S35 that a request for scanner data (step S20 in FIG. 4) has been received from the MFP 11, the scanner data is read from the memory unit and transmitted to the MFP 11 (step S42). If it is determined in S36 that a request for print data has been received from the MFP 11 (FIG. 4, step S18), the print data is read from the memory unit and transmitted to the MFP 11 (step S43).
[0057]
As described above, in the first embodiment, when a copy process or a print process is executed, the device is registered in the own device's recall data management table T1, and the fact is notified to another MFP. The received MFP deletes the registration of the recall data in its own device, so that only the recall data of the most recently executed MFP remains on the network.
[0058]
When a memory recall operation is performed from one of the MFPs, a print process is automatically performed based on the latest recall data remaining in the own device or another device. Recall operation can be performed, and labor for specifying recall data can be omitted.
Also, when print data from another device cannot be used, scanner data is used, so image information that can always be generated by copy processing of another device can be used. The types of target image information are expanded, and convenience is greatly improved.
[0059]
FIGS. 8A and 8B are sequence diagrams in which only the communication procedure performed between the MFP 11 and another MFP is extracted from the flowcharts of FIGS. (A) is a normal communication sequence in which copy processing or print processing is executed in the MFP 11, and when executing these processings, the MFP 11 is notified to other MFPs that new recall data has been registered (▲). 1 ▼).
[0060]
On the other hand, (b) shows a communication sequence when executing the memory recall print. If there is no recall data in the own device, the operation side MFP 11 transmits a notification inquiring about the presence or absence of the recall data to other MFPs ((2)), and in response to this, the presence or absence of the presence or absence of the recall data from each of the other MFPs. Receive a reply (3).
If any other MFP receives a response indicating that it has the recall data, it requests that MFP to transmit the recall data by designating the data format ([4]). .
[0061]
The MFP receiving this request transmits the recall data in the corresponding data format to the operation side MFP 11 ([5]).
<Second embodiment>
Next, a second embodiment of the present invention will be described.
The configuration of the MFP according to the present embodiment is the same as that of the first embodiment, and only a part of the control contents of the memory recall performed in the control unit 300 is different. The following description focuses on portions having different contents (the same applies to other embodiments).
[0062]
FIG. 9 is a flowchart in which steps S22 to S25 different from the flowchart of FIG. 4 in the first embodiment and steps around the steps are extracted.
If it is determined in step S10 that there is recall data in another MFP (step S10: Yes), it is determined in step S14 whether or not the print data of the recall data can be used by the own apparatus. For example, the process proceeds to step S22, where the type of the recall data and a message prompting the user to select one of them are displayed on the display unit 91 of the operation panel 90.
[0063]
FIG. 10 is an example of a screen displayed on the display unit 91 when recall data registered in another MFP is generated by a copy process. In this case, since the data format of the recall data is the print data and the scanner data, first, a message indicating that both the print data and the scanner data can be used and a message prompting the user to select one of them are displayed in a message display column 911. Is displayed. In the recall data list 912 below the recall data list 912, the two types of data format, the model name, and the registration date are displayed, and an OK button 913 is displayed at the lower right of the screen.
[0064]
When the operator presses a displayed portion of either data format with a finger, the density of the column is inverted, and when the OK button 913 is further pressed, it is regarded that the selected content has been determined, and the control unit 300 Accepts the operator's selection (step S23). Then, a request for the recall data in the selected data format is made to the MFP holding the recall data (step S24). When the recall data is transmitted, it is received (step S25), and the recall data is received. The printing process is executed based on the data (step S6: see FIG. 4).
[0065]
If it is determined in step S14 that the print data cannot be used as it is, as in the case of FIG. 4, it is determined whether or not the recall data is obtained by the printing process (step S17), and the determination result is obtained. In response to the request, the MFP requests the partner MFP for print data or scanner data (step S18 or S20), receives the transmitted data (step S19 or S21), and shifts to the printing process in step S6.
[0066]
Although the print data of the other device can be used in step S14 in this way, the requested data format is deliberately left to the selection of the operator because the model name of the own device and the partner device are the same. The print data generated by each MFP is output to the second signal processing unit 430 according to the current state of each printer engine, for example, the remaining amount of toner, the density of a reproduced image, and the usage time of the photosensitive drum. In the above, the parameters such as the transfer voltage and the developing bias which are optimal for the apparatus are set, so in a strict sense, the print data in the other MFP is used as it is as the optimal print data in the MFP in which the memory recall print operation is performed. This is because it may not be possible.
[0067]
In the present embodiment, in order to meet an operator's desire to perform print processing based on the print data optimized as described above, another data format that has not undergone data processing in the second signal processing unit of another MFP ( This allows the operator to select the use of scanner data and print data.
Since the scanner data and the print data have not been subjected to the correction peculiar to each printer engine, the second signal processing unit 430 generates the optimum print data according to the current characteristics of the printer engine of the own apparatus based on the data. Better reproducibility can be obtained.
[0068]
<Third embodiment>
In the first and second embodiments, only the most recent recall data is left on the network (see FIG. 7, step S38, etc.). This eliminates the trouble of selecting the target recall data from the large number of recall data.
[0069]
On the other hand, if another operator uses one of the MFPs before performing a memory recall print operation after one operator has performed his or her own copy processing, the processing of the other operator will be performed. Since the recalled data remains as recalled data, it is no longer possible to print out based on the own recalled data.
Therefore, in the third embodiment, the recall data is associated with the identification information of the operator (hereinafter, referred to as “personal ID”) so that a plurality of recall data can be held, and the operator can perform his or her own memory recall print operation. Recall data can be easily selected and printed out.
[0070]
FIG. 11 is a flowchart illustrating a control operation performed by control unit 300 of MFP 11 during a memory recall print operation according to the present embodiment.
First, in step S51, it is determined whether or not the start button has been pressed, and if it has been pressed, the input of the operator's personal ID is accepted (step S52). The general method of inputting the personal ID is that the operator inputs a password of about four digits from a numeric keypad, but is not limited to this. A special personal authentication unit may be provided in the MFP 11 to authenticate the individual. For example, an IC card reader may be provided to read the personal ID recorded on the IC card, or the fingerprint of the operator may be detected by a fingerprint sensor and the feature point thereof may be registered. . A well-known authentication system for recognizing a person by recognizing a voiceprint, retina, skull shape, height and weight, etc., in addition to such fingerprints as identification information depending on physical characteristics of the individual may be used.
[0071]
Further, the identification information of an individual in the present embodiment may be information indicating a group such as a department or section to which the individual belongs. In this case, enter the code assigned to the group, or if the color of the uniform is different at each workplace, image the uniform with a CCD camera or the like, analyze the image data, and change the group color. The form which recognizes and determines the group to which it belongs may be used.
[0072]
Here, in short, in registering the recall data, any method can be used as long as it is possible to obtain information that can be used to identify itself or the recall data to which the self belongs when referring to the registration list of the recall data later. May be used.
Next, it is determined whether there is a document on the document tray 111 of the ADF 110 or the platen glass 123 (step S53). If there is a document, it is determined that the operator desires a copy process of the document. Therefore, the document is scanned by the scanner unit 120 (step S54), and the image signal is processed by the main control unit 400. The scanner data and print data obtained in this way are stored in the memory unit 440 of the own device, and are registered with the registration number 1 in the recall data management table T2 (see FIG. 12) (step S55). After that, another MFP is notified that its own device has newly registered recall data (step S56).
[0073]
In the present embodiment, the recall data is configured to be able to be registered up to n (n = 2, 3, 4,...) On the network, and the recall data is newly registered. Exceeds the upper limit number (the number of registrable cases) n, the oldest recall data is deleted.
That is, when registering the new recall data, it is determined whether or not another recall data has already been registered in the recall data management table T2 (step S57). If any recall data has been registered, the registration of each registered recall data is performed. The number is incremented by 1 (step S58), and the registration number of the newly registered recall data is set to 1. If the incremented registration number exceeds the upper limit number (the number of registrable cases) n (step S59: Yes), the recall data corresponding to the registration number is deleted (step S60).
[0074]
FIG. 12 is a diagram showing an example of the recall data management table T2 registered as described above. As shown in the drawing, the recall data management table T2 has a registration number column, a personal ID column, a registration date column, and a data format column. Each time a new copy process or print process is performed, data is stored in the top row. It has been added.
[0075]
In the table, each column of the registration number 4 is blank, indicating that the notification that the recall data has been generated by another MFP has been received. At this stage, since information about the data format and the model name of the recall data has not been received from another MFP, the recall data is registered in the form shown in FIG. .
[0076]
Thereafter, a printing process is executed based on the read image data (step S73).
If it is determined in step S53 that there is no document on the document tray or the platen glass, it is assumed that an input operation for memory recall print has been performed, and the recall data management table T2 in the own device is first searched. Then, the presence / absence of recall data associated with the personal ID received in step S52 is checked, and other MFPs are sequentially inquired about the presence / absence of recall data corresponding to the personal ID (steps S61 and S62).
[0077]
Until the inquiry to all the MFPs is completed, the display unit 91 of the operation panel 90 displays, for example, "Your recall data is currently being searched. Please wait for a while." (No in step S63, step S64) ).
The MFP that has received this inquiry replies to the inquiry-originating MFP 11 whether or not the corresponding recall data exists (see FIG. 15, step S102 described later). If there is applicable recall data, reply with the data format, registration date, and model name.
[0078]
Then, as a result of inquiring all MFPs, if no recall data is found in the network including the own device for the received personal ID (step S63: No), the display unit 91 displays “Your recall data is , Was not found. "(Step S66), and the memory recall print processing is terminated.
[0079]
If it is determined in step S65 that there is recall data associated with the received personal ID in the network, the list is displayed on the display unit 91.
FIG. 13 is a diagram showing an example of this list display. The message field 915 displays a message indicating that the recall data of the operator XX has been displayed and a message prompting selection of data to be printed from the recall data.
[0080]
Below that, a list of recall data is displayed along with the model name and registration date. Reference numerals 917 and 918 denote up and down scroll buttons, and data that cannot be displayed in the list can be scrolled and displayed by operating the scroll buttons.
Then, when the operator presses the data to be printed out from this list, the density is inverted, and when the OK button 919 is further pressed, it is assumed that the selected content has been determined and accepted (step S68 in FIG. 11). Then, it is determined whether or not the selected data is the recall data of the own device (step S69), and if so, the recall data is read from the memory unit of the own device to execute the printing process (step S70, S73). In the list display of FIG. 13, the recall data in the own device is not displayed, but in the case of the own device, only the print data is displayed. In the case of the recall data of the own device to distinguish it from the recall data of another device, some kind of identification may be added or the font may be changed.
[0081]
Conversely, if the selected recall data is the recall data held by another MFP, the MFP requests the MFP to transmit the selected recall data, and receives the data transmitted from the requested MFP ( Step S72), print processing is executed (step S73).
FIG. 14 is a flowchart illustrating a control operation of the control unit 300 when the MFP 11 receives a request for a print job from a client terminal and executes print processing.
[0082]
First, in step S81, it is determined whether a print job has been received from the client terminal. If so, a personal ID is extracted from the header (step S82), and the received print data is associated with the personal ID to recall data. Register it in the management table T2 (step S83).
Then, it notifies another MFP that the recall data has been newly registered (step S84).
[0083]
On the other hand, it is determined whether there is registered recall data in the own device (step S85), and if so, the registration numbers are incremented by one.
(Step S86), and if any of them exceeds the upper limit number (the number of registrable cases) n, the recall data is deleted (Step S87: Yes, Step S88). Then, the control of the printing process is executed based on the received print data (step S89).
[0084]
FIG. 15 is a flowchart of a response process executed by the control unit of the partner MFP that receives various requests from the MFP that has received the memory recall print operation. As in the case of FIG. 7, a case will be described as an example where the MFP 11 receives the operation of the memory recall print and the MFP 12 receives the above various requests from the MFP 11 and responds.
[0085]
It is determined whether or not any information has been received from the MFP 11 (step S91: Yes), and if so, what the information is is analyzed (steps S92 to S96), and a response corresponding to each received content is made. Is performed (steps S97 to S105).
That is, first, if the received information is a notification that new recall data has been registered in the MFP 11 (see step S56 in FIG. 11 and step S84 in FIG. 14) (step S92), the own recall data Referring to the management table T2, it is determined whether or not the recall data is in the own device, and if so, the registration number of the recall data is incremented by one (step S98), and as a result, if the registration number is If there is more than the upper limit number (registrable number) of n that can be registered in the network, the recall data of the registration number is deleted and the recall data in the memory unit can be deleted or overwritten. (Step S99: Yes, Step S100).
[0086]
This is done so as not to hold the recall data of more than the registrable number (n) on the network. It is considered that the recall data with the old registration number is no longer likely to be used for the memory recall print operation, and there is no need to use the capacity in the memory unit more than necessary for the recall data, thus saving memory. .
[0087]
Also, in step S93, when a request for confirming the presence or absence of recall data for a specific personal ID (see step S62 in FIG. 11) is received from MFP 11, reference is made to the own recall data management table T2 to make an inquiry. The presence or absence of recall data corresponding to the personal ID is confirmed (step S101), and the confirmation result is transmitted to MFP 11 as recall data presence / absence information (step S102). When replying that there is recall data, the model name of the own device and the registration date are included in the recall data presence / absence information.
[0088]
If it is determined in step S94 that a print data transmission request has been received from the MFP 11, the corresponding print data is read from its own memory unit and transmitted to the MFP 11 (step S103).
Similarly, if it is determined in step S95 that a request for scanner data has been received from the MFP 11, the scanner data is read from the memory unit and transmitted to the MFP 11 (step S104). If it is determined that the request has been received, the print data is read from the memory unit and transmitted to the MFP 11 (step S105).
[0089]
As described above, the latest plurality of recall data is stored on the network in association with the personal ID, so that after the self-copying process or the printing process, the recall of the third party is performed before the memory recall printing operation is performed. Even if the data is created, its own recall data is not deleted, and can be easily selected by a personal ID.
[0090]
In the present embodiment, the number of cases (n) that can be registered in the entire network is determined regardless of the personal ID, but the number of cases that can be registered (m) (m = 1, 2) for each personal ID. , 3,...) May be determined.
In this case, in step S55 of FIG. 11 and step S83 of FIG. 14, a registration number is assigned for each personal ID, and in steps S57 and S85, the presence or absence of recall data registered for the personal ID is determined. Is incremented by one, and the registration number is deleted from those whose number exceeds the number of registrable cases (m).
[0091]
Further, in step S56 of FIG. 11 and step S84 of FIG. 14, the MFP notifies the other MFP of the new registration of the recall data and the personal ID thereof, and the MFP that has received the information notifies the MFP of FIG. In step S97, the presence or absence of recall data is checked for the personal ID, and if there is, the registration number is incremented by one, and if the registration number exceeds the registrable number (m), a process of deleting the registration number is executed. Will be.
[0092]
In this way, since up to m call data for one personal ID is always stored on the network, after the self copy processing or print processing, how many third party recall data are stored. Even if it is held, its own recall data is always left, so that the expectation of a person who wants to perform a memory recall print based on his already processed data will not be disappointed.
[0093]
<Fourth embodiment>
FIG. 16 is a flowchart illustrating a control operation of a memory recall print process executed in control unit 300 of MFP 11 according to the fourth embodiment of the present invention.
In the above-described first to third embodiments, the recall data is held in each MFP. However, in the present embodiment, the feature is that the server 40 manages the recall data in a centralized manner.
[0094]
That is, in step S111, it is determined whether or not the start button has been turned ON. If so, it is determined whether or not there is a document to be read (step S112). (Step S113).
Then, the scanner data and the print data of the read document are transmitted to the server 40, and a printing process is executed based on the print data (step S115).
[0095]
The scanner data and the print data are respectively transmitted to the server 40 according to a known file transmission protocol (for example, FTP). The header of the server data includes the normal IP address of the transmission source, the IP address of the transmission destination, and the like. , The data format, the registration date, and the model name of the own device are added.
If it is determined in step S112 that there is no original, it is determined that a memory recall print operation has been performed, and the process proceeds to step S116 to query the server 40 for the presence or absence of recall data. As will be described later, in response to this inquiry, information about the recall data (presence / absence of recall data, data format, model name) is transmitted from the server 40, and the presence / absence of the recall data in the server 40 is determined based on the information (step). S117).
[0096]
If there is recall data, it is determined from the model name of the MFP that generated the data whether or not the print data is usable in the own apparatus (step S118). A request is made to the server 40, and the print data transmitted from the server 40 is received (steps S119, S120), and a printing process is executed based thereon (step S115).
[0097]
If it is determined in step S118 that print data cannot be used, it is next determined whether there is print data in the recall data. Data is requested from the server 40, the recall data transmitted from the server 40 is received (steps S122 and S123 or steps S124 and S125), and a printing process is executed based on the received print data or scanner data (step S122). S115).
[0098]
The flowchart executed by the control unit 300 when the MFP 11 performs the print processing is that the step S23 in the flowchart of FIG. 6 in the first embodiment is the step of “transmitting print data and print data to the server as recall data”. And only step S24 is eliminated, so illustration is omitted. The transmission of the print data and the print data to the server 40 is executed according to the same protocol as in step S114 in FIG. 16, and the data format, the registration date, the model name, etc. are added to each header.
[0099]
FIG. 17 is a flowchart showing the contents of a response process to MFP 11 executed by server 40 in the present embodiment.
First, it is determined whether or not any transmission data has been received from the MFP 11 (step S131). If it has been received, in steps S132 to S136 below, the contents of the received data are analyzed, and processing corresponding to the data is performed. Is performed (steps S137 to S142).
[0100]
That is, if the received data is new recall data (see step S114 in FIG. 16), the old recall data stored in the storage device such as the HDD of the own device is overwritten with the new recall data (the old recall data is If not, write it as is). At this time, the information of the header of the received recall data is read, and thereby the internal recall data management table T3 is updated.
[0101]
This recall data management table T3 is stored in a nonvolatile memory such as an EEPROM in the server 40. FIG. 18 shows an example of this table T3, in which data such as the data format of the received recall data, the model name, the registration date, and the memory address indicating the storage location in the storage device are stored in the header of the received data. Read and stored.
[0102]
If the received content is an inquiry about the presence or absence of the recall data transmitted from the MFP 11 (see FIG. 16, step S116) (step S133: Yes), the server 40 determines whether the recall data is registered in the recall data management table T3. (Step S138), if the recall data is registered, the information of the data format and the model name is transmitted to the MFP 11, and if not, the reply that there is no recall data is transmitted to the MFP 11. (Step S139).
[0103]
If it is determined in step S134 that a print data transmission request has been received from the MFP 11, the print data is read from its own memory unit and transmitted to the MFP 11 (step S140).
Similarly, if it is determined in step S135 that a request for scanner data has been received from the MFP 11, the scanner data is read from the memory unit and transmitted to the MFP 11 (step S141). If it is determined that the request has been received, the print data is read from the memory unit and transmitted to the MFP 11 (step S142).
[0104]
FIGS. 19A and 19B are sequence diagrams in which only the communication procedure between the MFP 11 and the server 40 is extracted from the flowcharts of FIGS.
(A) is a normal communication sequence in which copy processing or print processing is executed by the MFP 11, and when these processings are executed, new recall data is transmitted to the server 40 ((1)).
[0105]
(B) shows a communication sequence at the time of executing the memory recall print.
When receiving the operation of the memory recall print, the MFP 11 transmits a notification for inquiring the presence or absence of the recall data to the server 40 ((2)), and in response to this, the server 40 answers the presence or absence of the recall data ((3)). ).
If the server 40 has the recall data, the MFP 11 requests the MFP 11 to specify the data format and transmit the recall data ([4]).
[0106]
Upon receiving this request, the server 40 transmits the recall data in the corresponding data format to the operation side MFP 11 ([5]).
As described above, according to the present embodiment, the recall data can be centrally managed by the server. Therefore, when a memory recall print operation is received, the other MFPs are inquired about the presence or absence of the recall data. Saves time. Further, since it is not necessary for the MFP itself to hold the recall data, there is an advantage that the memory capacity can be reduced correspondingly and the manufacturing cost of the MFP can be reduced.
[0107]
Lastly, a description will be given of the correspondence between constituent elements in the claims and the present embodiment.
(1) The "storage means" in claim 1 of the claims corresponds to the memory unit 440 (see FIG. 3) in the present embodiment. The memory unit 440 mainly includes a hard disk device, but is not limited thereto.
[0108]
The “transmission request receiving unit” mainly corresponds to the communication control unit 700 and the main control unit 400 (for the control operation of the main control unit 400 at this time, for example, steps S34, S35, S36, etc. in the flowchart of FIG. 7) reference). Further, the “transmission unit” mainly corresponds to the communication control unit 700 and the main control unit 400 (similarly, see steps S41, S42, S43, etc. in the flowchart of FIG. 7).
[0109]
(2) The “output request receiving means” in claim 2 mainly corresponds to the operation panel 90 and the main control unit 400 (for the control operation of the main control unit 400 at this time, for example, step S1 in the flowchart of FIG. S2 etc.). The “inquiry means” corresponds to the communication control unit 700 and the main control unit 400 (similarly, see step S9 in the flowchart of FIG. 4). The “transmission request unit” corresponds to the communication control unit 700 and the main control unit 400 (similarly, see steps S10, S14, S15, S18, S20, etc. in the flowchart of FIG. 4). The “receiving unit” mainly corresponds to the communication control unit 700.
[0110]
“Output unit” mainly corresponds to the printer unit 200. In the above-described embodiment, the printer unit 200 is an electrophotographic image forming unit. However, as long as an image can be reproduced based on image data, all the image forming methods such as an ink jet system and a thermal transfer system can be used. Means apply.
(3) The “identification information receiving means” in claim 5 mainly corresponds to the numeric keypad 92 of the operation panel 90 and the main control unit 400 (for the control operation of the main control unit 400 at this time, for example, the flowchart of FIG. 11) In step S52). As described above, the input means of the identification information is not limited to the numeric keypad 92 but may be an IC card reader or a fingerprint sensor.
[0111]
<Modification>
As described above, the present invention has been described based on the embodiments. However, it goes without saying that the technical scope of the present invention is not limited to the above-described embodiments, and the following modified examples can be considered.
{Circle around (1)} In each of the above embodiments, when new recall data is registered, old recall data registered in the past is deleted in response to this registration (first, second, and fourth recall data). In the embodiment, only the most recent recall data is retained, and older recall data is deleted. In the third embodiment, each time a new recall data is registered, the registration number of the past recall data is incremented by one. Increment and delete the old one whose registration number exceeds the predetermined value.)
[0112]
However, the method of deleting old recall data is not limited to this. If a predetermined time (for example, 5 hours) elapses from the time when the recall data is registered, there is almost no possibility that a print request is issued for the recall data. Because it is conceivable, in such a case, a configuration may be adopted in which the new recall data is automatically deleted without waiting for registration.
[0113]
(2) Not only in the fourth embodiment but also in other embodiments, the recall data may be centrally managed in the server.
For example, in the third embodiment, the recall data generated by the MFP is transmitted to the server 40 with header information such as the data format, model name, and personal ID attached to each data format, and the server 40 side Alternatively, it may be configured to hold a plurality of recall data.
[0114]
(3) In each of the above embodiments, when the start button is pressed by the operator, the presence or absence of a document is determined, and when there is no document, it is determined that the memory recall print operation has been performed. It is needless to say that an operation button dedicated to memory recall printing may be provided in the printer.
{Circle around (4)} In the above embodiment, a color MFP has been considered as an image processing apparatus for generating recall data. However, even for a monochrome MFP, print data is generated according to the characteristics of the printer engine. The present invention applies.
[0115]
Further, the present invention is not limited to the MFP, but may be a printer or scanner unit that can be connected to a network.
Furthermore, according to the present invention, the image processing apparatus may be a printer controller that is directly connected to a printer or the like and manages a job executed in the image processing apparatus. In this case, the recall data generated by the print processing executed by the printer is stored in the printer controller or transferred from the printer controller to the server. Further, the image processing device according to the present invention may be the server itself. In the case of these printer controllers and servers, the concept of "image processing" can be broadly grasped, and storage and transfer processing of image information can be included in the scope of the present invention by being a kind of image processing. . In the case where the present invention is applied to a printer controller or a server, "output" can be regarded as transmission to another device, and in a server or the like, the transmission unit is regarded as "output means" in claim 2. Can be.
[0116]
(5) In the above embodiment, only the recall data in the selected data format was requested from the other MFPs. However, image data in all data formats was transmitted once, and then the best data format was selected. Then, it is also possible to perform a printing process based on the image data of the selected data format.
Further, for example, when the contents of the image processing are copy processing, two types of data formats, that is, scanner data and print data, are described. However, when the contents of the data processing increase in the future, the data is further subdivided. At this stage, there is a possibility that a data format to which the present invention is applied may be generated. In short, the data format in the present invention may be any of a plurality of data formats generated in the course of specific image processing. Needless to say, it is desirable that the data format include a data format that can be commonly used by other devices.
[0117]
{Circle around (6)} The present invention can be understood as an image processing method in an image processing apparatus. In this case, for example, the content of the invention of the image processing method corresponding to the image processing apparatus of claim 1 is “an image processing method executed by an image processing apparatus connectable to a network, wherein one piece of image information is A storage step of storing in two or more types of data formats, a reception step of receiving a transmission request for image information from another device on the network, and a storage step of storing the image information in the storage unit based on the received transmission request. A transmitting step of transmitting image information in one of the data formats described above to the requesting apparatus. "
[0118]
The present invention can also be understood as a program for causing a computer in an image processing apparatus to execute the image processing method. Furthermore, the present invention can also be understood as a program recorded on a computer-readable recording medium such as a flexible disk, a hard disk, a CD-ROM, an MO, a DVD, a DVD-ROM, a DVD-RAM, and a semiconductor memory. Can be
[0119]
【The invention's effect】
As described above, according to the image processing apparatus of the present invention, one image information is stored in two or more types of data formats, and the image information in one data format is transmitted to the other device. In addition, it is possible to include a data format that can be output by the other device as the one data format, and the range of image information sources that can be used by other devices on the network is greatly expanded.
[0120]
Further, the image processing apparatus according to the present invention, when another apparatus holds one image information in two or more types of data formats as described above, the image information of one specific data format Is transmitted, the request can be made in a data format compatible with the output unit of the own device, and the output based on the image information in the other device can be performed by the own device.
[Brief description of the drawings]
FIG. 1 is a diagram showing an overall configuration of an image processing system using an MFP according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration of the MFP.
FIG. 3 is a block diagram illustrating a configuration of a control unit in the MFP.
FIG. 4 is a flowchart showing control contents executed by the control unit when a memory recall print operation is performed in the first embodiment of the present invention.
FIG. 5 is a diagram showing a configuration of a recall data management table provided in an EEPROM in the control unit.
FIG. 6 is a flowchart showing control contents executed by the control unit at the time of print processing in the first embodiment of the present invention.
FIG. 7 is a flowchart illustrating control contents of a response process executed by a control unit of another MFP according to the first embodiment of the present invention.
FIGS. 8A and 8B are sequence diagrams illustrating a communication procedure exchanged between an MFP that has received a memory recall print operation and another MFP in the first embodiment.
FIG. 9 is a flowchart showing characteristic steps of control contents at the time of a memory recall print operation executed by the control unit in the second embodiment of the present invention.
FIG. 10 is a diagram showing a selection screen of a data format of recall data displayed on a display unit of an operation panel in the second embodiment.
FIG. 11 is a flowchart showing control contents executed by the control unit when a memory recall print operation is performed in the third embodiment of the present invention.
FIG. 12 is a diagram showing a configuration of a recall data management table provided in an EEPROM in a control unit in the third embodiment.
FIG. 13 is a diagram illustrating a recall data selection screen displayed on a display unit of an operation panel according to the third embodiment.
FIG. 14 is a flowchart showing control contents executed by a control unit at the time of print processing in the third embodiment of the present invention.
FIG. 15 is a flowchart illustrating control contents of a response process executed by a control unit of another MFP according to the third embodiment of the present invention.
FIG. 16 is a flowchart illustrating processing executed by the control unit when a memory recall print operation is performed in the fourth embodiment of the present invention.
FIG. 17 is a flowchart showing the contents of a response process executed by the control unit of the server in the fourth embodiment.
FIG. 18 is a diagram showing a configuration of a recall data management table provided in a memory of a control unit of the server.
FIGS. 19A and 19B are sequence diagrams illustrating a communication procedure exchanged between an MFP that has received a memory recall print operation and a server in the fourth embodiment.
[Explanation of symbols]
11-14 MFP (image processing device)
21 and 22 printers
31-33 Client terminal (PC)
40 server (image processing device)
50 LAN
100 Original reading unit
200 Printer unit (output means)
300 control unit
400 Main control unit (transmission request receiving means, output request receiving means, inquiry means, transmission request means, identification information receiving means)
410 first signal processing unit
430 second signal processing unit
440 memory unit (storage means)
460 CPU
500 Image reading control unit
600 Printer control unit
700 communication control unit (transmission request receiving means, inquiry means, transmission means, transmission request means, reception means)
T1, T2, T3 Recall data management table

Claims (5)

An image processing device connectable to a network,
Storage means for storing one image information in two or more types of data formats;
Transmission request receiving means for receiving a transmission request for image information from another device on the network,
And transmitting means for transmitting image information in one data format among the image information in the two or more data formats stored in the storage means to the requesting apparatus based on the received transmission request. Characteristic image processing device. An image processing device connectable to a network,
Output request receiving means for receiving an image information output request;
Inquiring means for inquiring other devices on the network about the presence or absence of the corresponding image information based on the received output request,
When a response is received from another device that the corresponding image information is held in two or more types of data formats, the device that transmitted the response receives the image of the two or more types of data format. Transmission request means for requesting transmission of image information in one data format of the information,
Receiving means for receiving image information transmitted from the other device;
An image processing apparatus comprising: an output unit that outputs the received image information. 3. The image processing apparatus according to claim 2, wherein the one specific data format is a data format adapted to an output function of the output unit. 4. The image information transmitted from the other device is the most recently processed image information among the image information processed by the devices on the network. Image processing device described in Comprising identification information receiving means for receiving identification information associated with the image information,
The transmission request unit transmits the image information of the one data format, which is the image information selected by the operator from the image information associated with the received identification information, to another device on the network. The image processing apparatus according to claim 2, wherein the request is issued.

Images