JP2014096680A - Image forming system, image forming device, control method therefor, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To switch whether to immediately execute processing corresponding to data received from a client device depending on a type of the data.SOLUTION: Data is received from a client device. It is determined whether the received data is print data or FAX data. When it is determined that the received data is FAX data, the FAX data is transmitted to a specified destination by FAX. When it is determined that the received data is print data, the print data is stored in a storage device. Bibliographic information data for managing the print data is generated.

Description

  The present invention relates to an image forming system for storing print data in an image forming apparatus and printing the stored print data from a desired image forming apparatus, an image forming apparatus, a control method therefor, and a program.

  When printing the print data, the print data is once stored in the storage device, and after the print instruction for the print data stored in the storage device is received by the image forming apparatus such as a multifunction peripheral, the print data Accumulated printing for starting the printing process is widely performed. As an advantage of performing accumulated printing, since it is necessary to issue a printing instruction on the image forming apparatus, there is prevention of diffusion of information by leaving the printed matter. In addition, since the print data stored in the storage device can usually be deleted, even if a print instruction is made by mistake, the print can be easily canceled. These contribute to improving information security and reducing printing costs (for example, Patent Document 1).

JP 2008-6778 A

  When performing such accumulation printing, usually, data received at a port used for receiving print data or FAX data transmitted from a client apparatus is often accumulated in a storage device. Due to such specifications, even when FAX data is received from the client device, the data is stored in the storage device.

  In such a case, in order to complete the FAX transmission instruction, it is necessary to issue a FAX operation instruction on the image forming apparatus. However, a user who has issued a FAX transmission instruction on the client apparatus instructs the FAX transmission instruction on the client apparatus. May be misunderstood as having completed the FAX transmission. As a result, urgent FAX data may be retained without being transmitted.

  An object of the present invention is to provide an image forming system capable of switching whether or not to immediately execute a process corresponding to data according to the type of data received from a client device.

In order to achieve the above object, an image forming system according to the present invention comprises the following arrangement. That is,
An image forming system capable of storing print data, wherein a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus are connected via a network,
The first image forming apparatus includes:
First receiving means for receiving data from the client device;
First determination means for determining whether the data received by the first reception means is print data or FAX data;
A FAX transmission unit configured to perform FAX transmission of the FAX data to a designated destination when the first determination unit determines that the data received by the first reception unit is FAX data;
Storage means for storing the print data in a storage device when the first determination means determines that the data received by the first reception means is print data;
Generating means for generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Means for sending
First request means for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
Second receiving means for receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information by the first requesting means; ,
Second request means for requesting print data to the image forming apparatus specified by the name information received by the second receiving means;
Printing means for printing the print data received from the image forming apparatus in response to the second request means,
The second image forming apparatus includes:
Third receiving means for receiving the name information transmitted from the first image forming apparatus;
Managing means for managing name information received by the third receiving means in a name information file for managing information on which image forming apparatus the print data is stored in;
Second transmission means for transmitting name information managed in the name information file in response to a request for name information from the first image forming apparatus;
Is provided.

  According to the present invention, according to the type of data received from the client device, it is possible to switch whether or not to immediately execute the process according to the data.

1 is an explanatory diagram illustrating an example of a system configuration of an image forming system. FIG. It is a hardware block diagram of the information processing apparatus applicable to a client apparatus. FIG. 3 is an explanatory diagram illustrating an example of a hardware configuration of a multifunction peripheral. FIG. 2 is a functional configuration diagram of a multifunction peripheral. 6 is a flowchart illustrating print data / fax data generation and transmission processing. It is a flowchart which shows the detailed flow of a data reception process. 6 is a flowchart illustrating a detailed flow of print data reception processing. 6 is a flowchart illustrating processing at the time of printing executed by the multifunction peripheral. 6 is a flowchart illustrating a detailed flow of print data list display processing. It is a flowchart which shows the detailed flow of a printing process. It is a flowchart which shows the detailed flow of a deletion process. It is a flowchart which shows bibliographic information data and print data deletion processing. It is a figure which shows an example of a data structure of a user information table. FIG. 6 is a diagram illustrating an example of name information notification destination MFP list information. It is a figure which shows an example of the data structure of a name information file. 6 is a diagram illustrating an example of a printer group management table. FIG. It is a figure which shows an example of a data structure of bibliographic information data. It is a figure which shows an example of the accumulation print data operation screen.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 illustrates an example of a system configuration of an image forming system according to the present invention. As shown in FIG. 1, an image forming system according to the present invention is a multifunction peripheral (ordinary) 101- that is an image forming apparatus capable of storing print data. 1, a multifunction peripheral (name service) 101-2, a client device 102, and a LAN 103. In the following description, the multifunction peripheral (normal) 101-1 and the multifunction peripheral (name service) 101-2 may be collectively referred to as the multifunction peripheral 101.

  The multifunction peripheral (normal) 101-1 is a multifunction peripheral having a print data receiving function, a print data bibliographic information extraction function, and a print data and bibliographic information management function. Communication ports (LPR ports, etc.) used for receiving print data and FAX data are set so as to be able to receive data only from specific devices (other multifunction devices, own device). Will not accept. When data is transmitted from the client apparatus 102 to the multi-function peripheral 101, the data is transmitted to a port to be monitored by a data management service described later.

  The multifunction device (name service) 101-2 is a multifunction device in which the name service is executed. This multifunction device is the same as the multifunction device 101-1, except that the name service is executed. The name service is a service for managing which user's print data is stored in which MFP.

  The client device 102 is installed with a printer driver and a FAX driver. These drivers have a function of creating print data and FAX data based on data received from the application program and transmitting the print data and FAX data to the designated multifunction peripheral 101 via the network (LAN 103).

  The LAN 103 is a network for connecting the multifunction machine 101-1, the multifunction machine 101-2, and the client device 102 so that they can communicate with each other.

  The above is an example of the system configuration of the image forming system of the present invention.

2 is a hardware configuration diagram of an information processing apparatus applicable to the client apparatus 102. Next, an example of a hardware configuration of the information processing apparatus applicable to the client apparatus 102 of FIG. 1 will be described with reference to FIG. To do. FIG. 2 is a block diagram illustrating an example of a hardware configuration of an information processing apparatus that can be applied to the client apparatus 102.

  In FIG. 2, reference numeral 201 denotes a CPU that comprehensively controls each device and controller connected to the system bus 204. The ROM 203 or the external memory 211 stores a BIOS (Basic Input / Output System) and an operating system program (hereinafter referred to as OS) that are control programs of the CPU 201. Further, the ROM 203 or the external memory 211 stores various programs described below necessary for realizing the functions executed by the client device 102.

  A RAM 202 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program necessary for execution of processing from the ROM 203 or the external memory 211 into the RAM 202 and executing the loaded program.

  An input controller 205 controls input from an input device 209 such as a keyboard and a pointing device. A video controller 206 controls display on a display device such as the display device 210. These are used by the operator as needed.

  A memory controller 207 controls access to the external memory 211 that stores a boot program, various applications, font data, user files, edit files, various data, and the like. Examples of the external memory 211 include a hard disk (HD), a flexible disk (FD), and a compact flash (registered trademark) memory connected to the PCMCIA card slot via an adapter.

  A communication I / F (interface) controller 208 is connected to and communicates with an external device via a network (for example, the LAN 103 in FIG. 1), and executes communication control processing in the network. For example, communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the display device 210 by, for example, executing outline font rasterization processing on a display information area in the RAM 202. Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) or the like on the display device 210.

  The processing of each step shown in the flowchart described later for realizing the present invention is executed by a computer-readable program. The program is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 202 as necessary. Furthermore, a definition file and various information tables used when executing this program are also stored in the external memory 211, and a detailed description thereof will be described later.

[FIG. 3] Description of an Example of Hardware Configuration of the Multifunction Device 101 Next, a hardware configuration of the multifunction device 101 of FIG. 1 will be described with reference to FIG. FIG. 3 is a block diagram illustrating an example of a hardware configuration of the multifunction peripheral 101 of FIG.

  In FIG. 3, reference numeral 316 denotes a controller unit that inputs and outputs image data and device information by connecting to a scanner 314 that functions as an image input device and a printer 312 that functions as an image output device. On the other hand, the controller unit 316 inputs and outputs image data and device information by connecting to a LAN (for example, the LAN 103 in FIG. 1) or a public line (WAN) (for example, PSTN or ISDN).

  In the controller unit 316, reference numeral 301 denotes a CPU, which is a processor that controls the entire system. A RAM 302 is a system work memory for the CPU 301 to operate, and is also a program memory for recording a program and an image memory for temporarily recording image data.

  A ROM 303 stores a system boot program and various control programs. A hard disk drive (HDD) 304 stores various programs for controlling the system, image data, and the like. The print data with security settings received from the client apparatus 102 is also stored in the HDD 304.

  An operation unit interface (operation unit I / F) 307 is an interface unit with the operation unit 308. Further, the operation unit I / F 307 serves to transmit the key information (for example, pressing of the start button) input from the operation unit 308 to the CPU 301.

  A network interface (network I / F) 305 is connected to a network such as the LAN 103 and inputs / outputs data. A modem 306 is connected to a public line and inputs / outputs data such as FAX transmission / reception.

  Reference numeral 318 denotes an external interface (external I / F), which is an interface unit that accepts external inputs such as USB, IEEE 1394, printer port, and RS-232C. In the present embodiment, a card reader 319 for reading a non-contact IC card (storage medium) necessary for user authentication is connected to the external I / F 318. The CPU 301 can control reading of information from the IC card by the card reader 319 via the external I / F 318, and can acquire information read from the IC card. The above devices are arranged on the system bus 309.

  An image bus interface (image bus I / F) 320 connects the system bus 309 and an image bus 315 that transfers image data at high speed, and is a bus bridge that converts a data structure. The image bus 315 is constituted by, for example, a PCI bus or IEEE1394. The following devices are arranged on the image bus 315.

  A raster image processor (RIP) 310 develops vector data such as a PDL code into a bitmap image. A printer interface (printer I / F) 311 connects the printer 312 and the controller unit 316, and performs synchronous / asynchronous conversion of image data. A scanner interface (scanner I / F) 313 connects the scanner 314 and the controller unit 316 and performs synchronous / asynchronous conversion of image data.

  An image processing unit 317 corrects, processes, and edits input image data, and performs printer correction, resolution conversion, and the like on print output image data. In addition to this, the image processing unit 317 performs image data rotation and compression / decompression processing such as JPEG for multi-valued image data and JBIG, MMR, MH for binary image data. Then, the image processing unit 317 drives the scanner 314 to perform image processing on the image data that has been read, converts the image data into a format that can be output as a file (for example, a PDF format file), and cooperates with the CPU 301 to create a network I A file of image data can be transmitted to an external device via / F305.

  The scanner 314 illuminates an image on paper as a document and scans it with a CCD line sensor, thereby converting it into an electrical signal as raster image data. The original paper is set on the tray of the original feeder, and when the apparatus user instructs the start of reading from the operation unit 308, the CPU 301 gives an instruction to the scanner 314, and the feeder feeds the original paper one by one to read the original image. Perform the action.

  The printer 312 is a part that converts raster image data into an image on paper. The method includes an electrophotographic method using a photosensitive drum or a photosensitive belt, an ink jet method in which ink is ejected from a micro nozzle array and an image is directly printed on a sheet, and any method may be used. The activation of the printing operation is started by an instruction from the CPU 301. The printer 312 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and has a paper cassette corresponding thereto.

  The operation unit 308 has an LCD display unit, and a touch panel sheet is pasted on the LCD display unit. The operation unit 308 displays a system operation screen, and when the displayed key is pressed, the position information is displayed on the operation unit I. To the CPU 301 via / F307. The operation unit 308 includes, for example, a start key, a stop key, an ID key, a reset key, and the like as various operation keys.

  Here, the start key of the operation unit 308 is used when starting a document image reading operation. At the center of the start key, there are two color LEDs, green and red, which indicate whether or not the start key can be used. Further, the stop key of the operation unit 308 functions to stop the operation in operation. The ID key of the operation unit 308 is used when inputting the user ID of the user or manually performing logout processing of the user. The reset key is used when initializing settings from the operation unit 308.

  The card reader 319 reads information stored in the non-contact IC card under the control of the CPU 301 and notifies the CPU 301 of the read information via the external I / F 318.

  With the configuration described above, the multi-function peripheral 101 can transmit the image data read from the scanner 314 to the LAN 103, and print out the print data received from the LAN 103 with the printer 312.

  Also, the image data read from the scanner 314 can be faxed to the public line by the modem 306, and the image data received by fax from the public line can be printed out by the printer 312.

[FIG. 4] Functional configuration diagram of the MFP (normal) 101-1 and the MFP (name service) 101-2 In the MFP (normal) 101-1, the data management service and the stored print execution service are executed in different processes. Has been. In addition, in the multifunction peripheral (name service) 101-2, a name service is executed in addition to them.

  Hereinafter, functional units realized by the data management service will be described.

  The data receiving unit 401 is a functional unit that receives print data and FAX data transmitted from the client apparatus 102. The data receiving unit 401 sets data received at a specific port as data to be processed.

  The data type determination unit 402 is a functional unit that determines the data type of whether the data received by the data reception unit 401 is print data or FAX data.

  The bibliographic information data generation unit 403 is a functional unit that acquires bibliographic information from the print data received by the data reception unit 401, generates bibliographic information data of the print data, and stores it in the HDD 304. The bibliographic information includes, for example, the document name, the name of the user who has instructed printing, print settings (color / monochrome, duplex / single-sided, print layout, etc.), number of copies, number of pages, and the like.

  The name information registration request unit 404 uses the name service to manage which user's and print data that can be printed by the multifunction device 101 belonging to which printer group is stored in the multifunction device (normal) 101-1. This is a functional unit that makes a request for registration of name information to be used to the multifunction peripheral (name service) 101-2.

  The bibliographic information data request receiving unit 405 is a functional unit that receives a request for bibliographic information data from the bibliographic information data requesting unit 420 of the storage printing execution service.

  The bibliographic information data transmission unit 406 is a functional unit that, when the bibliographic information data request receiving unit 405 receives a request for bibliographic information data, sends a list of corresponding bibliographic information data to the multifunction peripheral 101 that has requested bibliographic information. is there.

  The print data request reception unit 407 is a functional unit that receives a print data request from the print data request unit 421 of the stored print execution service.

  The print data transmission unit 408 is a functional unit that transmits the print data whose transmission request has been received by the print data request reception unit 407 to the MFP 101 that has made the request.

  The status update unit 409 is a functional unit that updates the status of the bibliographic information data of the print data in response to a print execution instruction or a delete instruction of the print data.

  The print data deletion unit 410 is a functional unit that deletes print data. Examples of print data to be deleted include print data instructed to be deleted by a print data deletion request unit 422 of a storage print service, which will be described later, or print data that has been received from the client apparatus 102 for a predetermined time or more.

  The bibliographic information data deletion unit 411 is a functional unit that deletes the bibliographic information data of the print data deleted by the print data deletion unit 410.

  The name information deletion request unit 412 is a functional unit that issues a name information deletion request to the multifunction peripheral (name service) 101-2.

  Hereinafter, functional units realized by the accumulated print execution service will be described.

  The name information request unit 419 manages, for the multifunction peripheral (name service) 101-2, which multifunction peripheral stores the print data of the login user that can be printed by the multifunction peripheral (normal) 101-1. It is a functional part that requests name information.

  The bibliographic information data request unit 420 is a functional unit that requests bibliographic information data of print data of a user who is logged in to the multi-function peripheral 101 from the multi-function peripheral (self-machine, other machine) that is executing the data management service. Which multifunction device stores the print data of the login user is recognized using name information.

  The print data request unit 421 is a functional unit that requests the multifunction machine 101 (self machine, other machine) to transmit designated print data.

  The print data deletion request unit 422 is a functional unit that requests the multifunction machine 101 (self machine, other machine) to delete designated print data.

  Hereinafter, functional units realized by the name service will be described. This name service is a functional unit possessed only by the multifunction peripheral (name service) 101-2.

  The name information receiving unit 413 is a functional unit that receives name information transmitted from the name information registration request unit 404.

  The name information storage unit 414 is a storage unit that stores the name information received by the name information receiving unit 413 as a name information file.

  The name information request reception unit 415 is a functional unit that receives a transmission request for name information indicating a storage location of print data that can be printed by a specific user's specific printer group, by the name information request unit 419.

  The name information transmission unit 416 is a functional unit that transmits the name information for which the transmission request is received by the name information request reception unit 415 to the multifunction peripheral that has made the request.

  The name information deletion request receiving unit 417 is a functional unit that receives a name information deletion request from the name information deletion request unit 412.

  The name information deletion unit 418 is a functional unit that deletes the name information for which the name information deletion request reception unit 417 has received the deletion request.

  Hereinafter, the platform functions common to the multifunction peripheral (normal) 101-1 and the multifunction peripheral (name service) 101-2 will be described.

  The print data receiving unit 423 is a functional unit that receives the print data transmitted from the print data transmitting unit 408 of the data management service.

  The print unit 424 is a functional unit that performs print processing of the print data received by the print data receiving unit 423. Since the print data receiving unit 423 receives the PDL data, the print data receiving unit 423 develops the data into printable data, and then performs print processing.

  The FAX transmission unit 425 is a functional unit that performs FAX transmission of FAX data received from the client apparatus 102 to a specified FAX number.

  Hereinafter, the processing flow will be described.

In the following description, in particular,
MFP A: MFP executing the data management service (that is, MFP 101-1 or 101-2)
MFP B: MFP executing name service (ie, MFP 101-2)
Multifunction machine C: A multifunction machine that is executing the accumulated printing execution service (ie, the multifunction machine 101-1 or 101-2)
The flowchart will be described as follows.

[FIG. 5] Print Data / FAX Data Generation and Transmission Processing The CPU 201 of the client apparatus 102 executes an application stored in the external memory 211, receives an editing instruction for document data using the application, and follows the editing instruction. Document data is created (step S501). The CPU 201 of the client apparatus 102 determines whether a print start request or a FAX transmission start request for the document data has been received (step S502).

  If no print start request or FAX transmission start request has been received (NO in step S502), the process waits until it is received. On the other hand, when a print start request or a FAX transmission start request is accepted (YES in step S502), the CPU 201 of the client apparatus 102 displays a driver selection screen (not shown) for accepting designation of a printer driver or a FAX driver ( Step S503).

  The CPU 201 of the client apparatus 102 accepts selection of a printer driver or a FAX driver via the driver selection screen (step S504). Thereafter, the CPU 201 of the client apparatus 102 accepts various print details settings or FAX details settings (step S505). The detailed print settings accepted here are color / monochrome settings, duplex / single-sided settings, print layout settings (Nin1), etc., and the detailed fax settings are, for example, fax numbers.

  Thereafter, the CPU 201 of the client apparatus 102 determines whether or not an execution instruction for printing or FAX transmission has been received. If an execution instruction has not been received (NO in step S506), it is determined whether a print or FAX transmission cancellation instruction has been received. If a cancel instruction has been accepted (YES in step S507), the process returns to step S501 to continue the document editing process. On the other hand, if a cancel instruction has not been received (NO in step S507), the process returns to step S504.

  When an execution instruction is accepted in step S506 (YES in step S506), the CPU 201 of the client apparatus 102 uses the driver selected in step S504 to perform data (print data) according to the various detailed settings received in step S505. (Or FAX data) is created (step S508). Then, the CPU 201 of the client apparatus 102 transmits the created data to the multifunction peripheral corresponding to the designated driver (step S509).

  The CPU 301 of the multifunction peripheral A receives the data (print data or FAX data) transmitted from the client device 102 (step S510). Then, the CPU 301 of the multifunction peripheral A performs a data reception process for the received data (step S511). Details of this data reception processing will be described with reference to FIG.

[FIG. 6] Detailed Flow of Data Reception Processing (Step S511 in FIG. 5) First, the CPU 301 of the multifunction peripheral A determines whether the data received in step S510 in FIG. 5 is print data or FAX data ( Step S601). If it is determined that the received data is FAX data, the CPU 301 of the multi-function peripheral A determines whether or not the multi-function peripheral has a FAX transmission function (step S602).

  If it is determined that there is a FAX transmission function (YES in step S602), the CPU 301 of the multi-function peripheral A transmits the FAX data to a destination (FAX number) set in the FAX data (step S603). On the other hand, if it is determined that there is no FAX transmission function (NO in step S602), the CPU 301 of the multifunction peripheral A deletes the FAX data without performing the transmission processing of the received FAX data (step S604).

  On the other hand, if it is determined in step S601 that the received data is print data, the CPU 301 of the multi-function peripheral A performs print data reception processing (step S605). Details of this processing will be described with reference to FIG. In the present invention, when the received data is FAX data, the FAX data is suitably stored in a storage device such as the HDD 304 and transmitted to a specified FAX number, thereby suitably preventing FAX transmission omission. It becomes possible.

[FIG. 7] Detailed Flow of Print Data Receiving Process (Step S605 in FIG. 6) Machine B).

  When the multifunction device A is the multifunction device (name service) 101-2, the multifunction device A and the multifunction device B may be the same multifunction device.

  The CPU 301 of the multifunction device A acquires the printer model name included in the print data (step S701). Thereafter, the CPU 301 of the multi-function peripheral A extracts bibliographic information including the user name, document name, and print setting information (color / monochrome setting, duplex / single-sided setting, print layout setting) of the user who issued the print instruction from the print data. (Step S702). Then, the CPU 301 of the multifunction peripheral A generates bibliographic information data for managing the print data based on the extracted bibliographic information (step S703). The data structure of the bibliographic information data is shown in FIG. 17 (described later).

  After generating the bibliographic information data, the CPU 301 of the multifunction peripheral A stores the print data received from the client apparatus 102 in a predetermined storage area of the storage device with a file name that conforms to a predetermined naming rule ( Step S704). Then, the CPU 301 of the MFP A sets the file name as the file name of the bibliographic information data. Thereafter, the CPU 301 of the multifunction peripheral A acquires a notification destination name service list (name information notification destination multifunction peripheral list information shown in FIG. 14) stored in the HDD 304 (step S705).

  Then, the CPU 301 of the MFP A acquires an unprocessed notification destination name service (not yet notified of name information) among the MFPs B registered in the acquired notification destination name service list ( Step S706). Then, the CPU 301 of the multi-function peripheral A transmits a name information registration request for registering name information to the acquired multi-function peripheral (name service) 101-2, which is a notification destination name service (step S707). The name information is information for notifying the name service of which user and print data that can be printed by which printer model is newly stored.

  The CPU 301 of the multifunction device B receives the name information registration request transmitted from the multifunction device A (step S708). Next, the CPU 301 of the multi-function peripheral B specifies in which printer group the printer model is included according to the printer model information included in the name information registration request (step S709). At this time, the printer group management table (described later) in FIG. 16 is used to identify which printer group the printer model information included in the name information belongs to.

  After identifying the printer group, the CPU 301 of the multifunction device B checks whether there is a name information file for managing which multifunction device stores print data that can be printed out by the multifunction device belonging to the identified printer model. (Step S710). A name information file is created for each printer group for each user. For example, the name of the file is “user name_printer group”, and the name information file stores which multifunction device that stores print data that can be printed by the multifunction device of which printer group of which user. The CPU 301 can recognize it.

  Based on the confirmation result, the CPU 301 of the multi-function peripheral B determines whether a name information file has been created (step S711). If it is determined that a name information file has not yet been created (NO in step S711), the CPU 301 of the multi-function peripheral B creates a name information file (step S712).

  On the other hand, when it is determined that the name information file has been created (YES in step S711), or after the name information file is created in step S712, the CPU 301 of the multi-function peripheral B makes a name information registration request to the name information file. It is determined whether or not the name information of the multifunction peripheral that has performed is already registered (step S713).

  If it is determined that the name information has not been registered (NO in step S713), the CPU 301 of the multifunction device B additionally registers the name information of the multifunction device that has requested the name information registration in the name information file (step S714). The name information here is information for specifying the multifunction peripheral, and for example, an IP address can be used. The data structure of the name information file will be described with reference to FIG.

  On the other hand, if it is determined that the name information has already been registered (YES in step S713), or after the name information is additionally registered in step S714, the CPU 301 of the multi-function device B makes the name information registration request. The name information registration processing result is transmitted to (step S715).

  The CPU 301 of the multifunction device A receives the name information registration processing result transmitted from the multifunction device B (step S716).

  Thereafter, the CPU 301 of the MFP A determines whether there is an unprocessed notification destination name service that has not yet transmitted a name information registration request among the notification destination name services acquired in step S705. If it is determined that there is an unprocessed notification destination name service, the processes in and after step S706 are repeatedly executed.

[FIG. 8] Overview of processing at the time of printing executed by the multifunction machine 101 This process is executed by the multifunction machine (multifunction machine C) on which the accumulated print execution service is executed.

  The CPU 301 of the multifunction machine C displays a login screen (not shown) on the LCD display unit of the operation unit 308 when there is no user logged in to the multifunction machine. At this time, the CPU 301 of the multifunction peripheral C is in a state where login information can be input.

  When the card reader 319 receives an input of card information input by inserting an IC card held by the user, the CPU 301 of the multifunction machine C performs a user authentication process (step S801). At this time, using the user information table shown in FIG. 13, the user who possesses the IC card storing the input card information is specified.

  The CPU 301 of the multifunction machine C determines whether or not the user has been specified in the user authentication process and the user authentication has been successful (step S802). If user authentication is not successful (NO in step S802), the process ends. On the other hand, if the user authentication is successful (YES in step S802), the CPU 301 of the multifunction machine C performs a print data list display process (step S803). In this process, the bibliographic information of the log-in user's print data is acquired from each MFP (including the self-machine), and the log-in user can execute print data on the MFP C using the acquired bibliographic information. The list information is created and displayed on the LCD display unit of the operation unit 308 so as to be selectable. Details of this processing will be described with reference to FIG.

  After completion of the print data list display process in step S803, the CPU 301 of the multifunction peripheral C accepts various operation instructions via the operation screen (FIG. 18) displayed on the LCD display unit (step S804).

  First, the CPU 301 of the multifunction machine C determines whether or not designation of print data is accepted as an operation instruction (step S805). This is based on whether or not a touch instruction for the print data displayed on the print data list display unit 1801 in FIG. 18 has been issued, and the CPU 301 of the multi-function peripheral C determines whether or not designation of print data has been accepted. As a result of the determination, if it is determined that the designation of print data has been received (YES in step S805), the CPU 301 of the multifunction peripheral C changes the print data selection state (step S806). Note that, when designation for print data in an unselected state is received, the print data is set to a selected state. When the designation for the selected print data is accepted, the print data is set to a non-selected state. Thereafter, the process returns to step S804.

  On the other hand, if it is determined that the designation of print data has not been accepted (NO in step S805), the CPU 301 of the multi-function peripheral C then determines whether a print instruction has been accepted as an operation instruction (step S807). This is based on whether or not a touch instruction for the print start button 1803 in FIG. 18 has been issued, and the CPU 301 of the multifunction peripheral C determines whether or not a print instruction has been accepted. As a result of the determination, if it is determined that a print instruction has been received (YES in step S807), the CPU 301 of the multifunction peripheral C performs a printing process (step S808). Details of the printing process will be described with reference to FIG. After the printing process ends, the process returns to step S804.

  On the other hand, if it is determined that a print instruction has not been received (NO in step S807), the CPU 301 of the multifunction peripheral C then determines whether a delete instruction has been received as an operation instruction (step S809). This is based on whether or not a touch instruction for the delete button 1802 in FIG. 18 has been issued, and the CPU 301 of the multifunction peripheral C determines whether or not a delete instruction has been accepted. As a result of the determination, if it is determined that a deletion instruction has been accepted (YES in step S809), the CPU 301 of the multifunction machine C performs a deletion process (step S810). Details of the deletion process will be described with reference to FIG. After the deletion process ends, the process returns to step S804.

  On the other hand, if it is determined that a delete instruction has not been received (NO in step S809), the CPU 301 of the multifunction peripheral C then determines whether a logout instruction has been received as an operation instruction (step S811). This is based on whether or not a touch instruction for the logout button 1804 in FIG. 18 has been issued, and the CPU 301 of the multifunction peripheral C determines whether or not a logout instruction has been accepted. As a result of the determination, if it is determined that a logout instruction has been accepted (YES in step S811), the CPU 301 of the multifunction peripheral C performs a logout process (step S812). Thereafter, the process ends.

  On the other hand, if it is determined that a logout instruction has not been received (NO in step S811), that is, if it is determined that the operation instruction is other than the above (NO in step S811), the CPU 301 of the multifunction machine C receives the received operation instruction. The process according to is performed (step S813). Thereafter, the process returns to step S804.

[FIG. 9] Detailed flow of print data list display process (step S803 in FIG. 8) (Multifunction machine A) is a process executed by a multifunction machine (multifunction machine B) on which the name service is executed. In some cases, two or more of the multifunction peripheral A, the multifunction peripheral B, and the multifunction peripheral C are the same multifunction peripheral.

  The CPU 301 of the multifunction device C acquires login user information that is specific information (for example, a user ID) of a logged-in user who has logged into the multifunction device C (step S901). Thereafter, the CPU 301 of the multi-function peripheral C transmits a name information acquisition request including login user information and printer model information of the multi-function peripheral to the notification destination name service (multi-function peripheral B) (step S902). At this time, if a plurality of notification destination name services are registered, a name information acquisition request is transmitted to the notification destination name service set as the primary notification destination name service. When the name information cannot be acquired from the primary notification destination name service, a name information acquisition request is further transmitted to another notification destination name service.

  The CPU 301 of the multifunction device B receives the name information acquisition request transmitted from the multifunction device C (step S903). The CPU 301 of the multifunction device B uses the printer model information included in the received name information acquisition request to identify the printer group to which the multifunction device that transmitted the user name information acquisition request belongs, and the multifunction device belonging to the printer group. A name information file for managing in which MFP the printable print data is stored is acquired (step S904). The CPU 301 of the multifunction device B transmits the name information registered in the name information file to the multifunction device C that has made the name information acquisition request (step S905).

  The CPU 301 of the multifunction device C receives name information from the multifunction device B (step S906). The CPU 301 of the multifunction device C makes a bibliographic information list acquisition request to all the multifunction devices A specified by the received name information.

  First, the CPU 301 of the multifunction device C identifies the unprocessed multifunction device A (not making a bibliographic information list acquisition request) as the processing target multifunction device A among the multifunction devices A identified by the received name information. (Step S907). The CPU 301 of the multifunction device C transmits a bibliographic information list acquisition request to the identified multifunction device A (step S908). This bibliographic information list acquisition request includes user specifying information (such as a user ID) for specifying the login user and printer model information of the multifunction peripheral C that has made the request.

  The CPU 301 of the multifunction device A receives the bibliographic information list acquisition request from the multifunction device B (step S909). The CPU 301 of the MFP A acquires the bibliographic information of the log-in user print data that can be printed by the MFP C that has requested the bibliographic information list among the print data stored in the HDD 304 (step S910). Then, the CPU 301 of the multifunction peripheral A creates bibliographic information list data using the bibliographic information acquired in step S910 (step S911). Thereafter, the CPU 301 of the multifunction device A transmits the bibliographic information list data to the multifunction device C that has transmitted the bibliographic information list acquisition request (step S912).

  The CPU 301 of the multifunction device C acquires the bibliographic information list data from the multifunction device A (step S913). The CPU 301 of the MFP C makes a bibliographic information acquisition request to all the MFPs A included in the name information, and then determines whether or not the bibliographic information of the MFP has been acquired (step S914). ). For example, when making a name service registration request, if the name information of the device could not be registered in the name service due to a communication error, etc., or the name information acquisition request communication failed and the name information could not be acquired. In such a case, since the bibliographic information of the own device cannot be acquired even if steps S907 to S913 are performed, such processing is executed.

  When it is determined that the bibliographic information has not been acquired (NO in step S914), the CPU 301 of the multifunction peripheral C acquires the bibliographic information in the login user's own device (step S915). Thereafter, the CPU 301 of the multifunction machine C displays the bibliographic information list acquired by the above-described processing (step S916).

[FIG. 10] Detailed flow of print processing (step S808 in FIG. 8) This is the process executed by A). Note that the MFP A and the MFP C may be the same MFP.

  The CPU 301 of the multifunction device C issues a print data print instruction to the multifunction device A that stores the print data for all the selected print data.

  First, the CPU 301 of the multifunction peripheral C acquires the storage destination information of the print data from the bibliographic information of the unprocessed print data (step S1001). Then, the CPU 301 of the multifunction device C transmits a print execution request for the print data to the multifunction device A indicated by the storage location information (step S1002). The print execution request includes information for specifying the requested MFP and information for specifying print data to be printed (for example, a print data file name).

  The CPU 301 of the multifunction device A receives the print execution request transmitted from the multifunction device C (step S1003). The CPU 301 of the multifunction peripheral A acquires the print data that is the target of the print execution request from the HDD 304 (step S1004). The CPU 301 of the multi-function peripheral A transmits the print data to a predetermined port (such as an LPR port) of the multi-function peripheral C (step S1005). When each MFP 101 receives print data or FAX data from the client apparatus 102 at a predetermined port (such as an LPR port), the MFP 101 discards the data, but prints transmitted from other MFPs 101. The data is not discarded and print processing is executed. With this configuration, print data from the client apparatus 102 can always be stored and printed.

  The CPU 301 of the multifunction device C receives print data from the multifunction device A (step S1006). The CPU 301 of the multifunction device C executes printing of the print data (step S1007).

  The CPU 301 of the multifunction device A acquires the bibliographic information of the print data after transmitting the print data to the multifunction device C (step S1008). The CPU 301 of the MFP A changes the status of the bibliographic information to “printed” (step S1009). Thereafter, the CPU 301 of the multifunction peripheral A transmits the print execution result to the multifunction peripheral C (step S1010).

  The CPU 301 of the multifunction device C receives the print execution result from the multifunction device A (step S1011). The CPU 301 of the multifunction machine C deletes the bibliographic information of the print data for which the print execution request has been made from the bibliographic information list (step S1012). The CPU 301 of the multifunction peripheral C then updates the print data list display using the updated bibliographic information list after completing the print execution request for all the print data for which the print instruction has been received from the user (step S1013). ).

[FIG. 11] Detailed Flow of Deletion Process (Step S810 in FIG. 8) This is the process executed by A). Note that the MFP A and the MFP C may be the same MFP.

  The CPU 301 of the multi-function peripheral C issues a print data deletion request to the multi-function peripheral A in which the print data is stored for all print data in the selected state.

  First, the CPU 301 of the multifunction peripheral C obtains storage location information of the print data from bibliographic information of unprocessed print data (step S1101). Then, the CPU 301 of the multifunction device C transmits a print data deletion request to the multifunction device A indicated by the storage location information (step S1102). The deletion request includes information for specifying the print data to be deleted (for example, the print data file name).

  The CPU 301 of the multifunction device A receives the print data deletion request transmitted from the multifunction device C (step S1103). The CPU 301 of the multifunction peripheral A acquires the bibliographic information of the print data that has received the deletion request (step S1104). The CPU 301 of the multifunction device A changes the status information to “deleted” (step S1105). Then, the CPU 301 of the multifunction peripheral A transmits the print data deletion processing result to the multifunction peripheral C that has issued the deletion request (step S1106).

  The CPU 301 of the multifunction device C receives the delete processing result transmitted from the multifunction device A (step S1107). The CPU 301 of the multifunction machine C deletes the bibliographic information of the print data that has been deleted from the bibliographic information list (step S1108). The CPU 301 of the multifunction peripheral C updates the print data list display based on the updated bibliographic information list after the deletion processing of all the print data for which deletion has been instructed (step S1109).

  Thereafter, the CPU 301 of the multi-function peripheral A determines the user name, the same user name as the printer group, and the bibliographic information data in which the printer group is registered, which are included in the bibliographic information data whose status is newly deleted in step S1105. It is determined whether or not all the statuses have been deleted (step S1110). If it is determined that it has been deleted (YES in step S1110), the CPU 301 of the multifunction device A acquires a notification destination name service (multifunction device B) (step S1111). Thereafter, the CPU 301 of the multi-function peripheral A transmits a request to delete the user name and printer group name information file to all notification destination name services (step S1112).

  The CPU 301 of the multifunction machine B receives the name information file deletion request (step S1113). The CPU 301 of the multi-function peripheral B confirms whether or not there is a name information file that has received the deletion request (step S1114). If it is determined that there is no name information file (NO in step S1115), the process advances to step S1117. On the other hand, if it is determined that there is a name information file (YES in step S1115), the CPU 301 of the multi-function peripheral B deletes the name information file (step S1116). Thereafter, the CPU 301 of the multifunction device B transmits the name information file deletion processing result to the multifunction device A (step S1117).

  The CPU 301 of the multifunction device A receives the processing result from the multifunction device B (step S1118).

  On the other hand, if it is determined in step S1110 that it has not been deleted, that is, if it is determined that there is even one piece of bibliographic information whose status has not been deleted (NO in step S1110), the CPU 301 of the multi-function peripheral A stores the name information file. The process is terminated without making a delete request.

[FIG. 12] Bibliographic Information Data and Print Data Deletion Processing This processing is performed when a predetermined timing is reached (for example, a predetermined time). This process is a process executed by a multifunction peripheral (multifunction peripheral A) in which the data management service is executed and a multifunction peripheral (multifunction peripheral B) in which the name service is being executed. Note that the MFP A and the MFP B may be the same MFP.

  The CPU 301 of the multi-function peripheral A determines whether or not the date and time registered in the time stamp of all the bibliographic information data stored in the HDD 304 is earlier than a predetermined date and time (for example, 3:00 three days ago). Is determined (step S1201). If the CPU 301 of the multifunction peripheral A determines that it is before the predetermined date and time (YES in step S1201), it sets the status of the bibliographic information data to deleted (step S1202).

  Thereafter, the CPU 301 of the multi-function peripheral A performs the following processing for all combinations of user names and printer groups included in the bibliographic information data whose status is newly changed to deleted in step S1202.

  First, with respect to the bibliographic information data in which the same user name and printer group as the bibliographic information data whose status has been changed to deleted are registered, it is determined whether or not all the statuses have been deleted (step S1204). If it is determined that all have been deleted (YES in step S1204), the CPU 301 of the MFP A deletes the user name and printer group name information file for all notification destination name services (MFP B). A request is transmitted (step S1205).

  The CPU 301 of the multifunction device B receives the name information file deletion request from the multifunction device A (step S1206). The CPU 301 of the multi-function peripheral B confirms whether or not there is a name information file that has received the deletion request (step S1207). If it is determined that there is no name information file (NO in step S1208), the process advances to step S1210. On the other hand, if it is determined that there is a name information file (YES in step S1208), the CPU 301 of the multifunction peripheral B deletes the name information file (step S1209). Thereafter, the CPU 301 of the multifunction device B transmits the name information file deletion processing result to the multifunction device A (step S1210).

  The CPU 301 of the multifunction device A receives the processing result from the multifunction device B (step S1211).

  Note that if it is determined in step S1204 that all have not been deleted, that is, if it is determined that there is at least one bibliographic information whose status has not been deleted (NO in step S1204), the CPU 301 of the multi-function peripheral A determines that the user No name information file deletion request is made for the name / printer group pair.

  After the processing from step S1203 to step S1211, the CPU 301 of the multifunction peripheral A checks the status of all bibliographic information files and determines whether the status has been deleted. If it is determined that the status has been deleted (YES in step S1212), the CPU 301 of the multi-function peripheral A deletes the bibliographic information data (step S1213). The CPU 301 of the multifunction peripheral A deletes the print data in which the bibliographic information is managed by the bibliographic information data (step S1214).

FIG. 13 shows an example of the data structure of the user information table. The user information table 1300 is a data table stored in the HDD 304 of each MFP 101. Using this information, the CPU 301 of the multifunction machine 101 identifies the user who has accepted the login request.

  The user ID 1301 is a data item in which identification information for uniquely identifying user information registered in the user information table 1300 is registered.

  The password 1302 is a data item in which a password required when the user performs login processing using a user ID is registered.

  The card ID 1303 is a data item in which a card ID for uniquely identifying an IC card possessed by a user managed by the record is registered. This card ID is used as authentication information when a user authentication process is performed in the multifunction machine.

[FIG. 14] Example of Name Information Notification Destination MFP List Information Name information notification destination MFP list information 1400, which is a notification destination name service list, is created in advance by a system administrator or the like and stored in the HDD 304 of each MFP 101. Is done.

  When the print data transmitted from the client apparatus 102 is received, the CPU 301 of the multifunction peripheral 101 transmits a name information registration request to the multifunction peripheral 101-2 registered in the name information notification destination multifunction peripheral list information 1400. To do. In the name information notification destination MFP list information 1400, information (for example, IP address) for specifying the MFP 101-2 is registered.

[FIG. 15] Example of Data Structure of Name Information File This name information file 1500 is stored in the storage device (RAM 302, HDD 304, etc.) of the multifunction peripheral (name service) 101-2.

  The name information file is: Which user This is a data file for managing information on which MFP 101 print data that can be executed by MFPs belonging to which printer group is stored. For example, if there are 10 users and 5 printer groups, up to 50 name information files are generated.

  By setting the file name of the name information file 1500 to “user name-printer group”, the multifunction device in which the name information file 1500 stores print data that can be printed by the multifunction device of which printer group of which user is stored. Whether it is managed or not can be specified.

[FIG. 16] Example of Printer Group Management Table This printer group management table 1600 manages information indicating which printer model belongs to which printer group. The printer group management table 1600 is stored in a storage device (such as the HDD 304) of the multifunction peripheral (name service) 101-2.

  A printer model 1601 is a data item in which printer model information is registered. The printer group 1602 is a data item in which information indicating which printer group the model (model) registered in the printer model 1601 belongs to is registered.

FIG. 17 is a diagram showing an example of the data structure of bibliographic information data. FIG. 17 is a diagram showing an example of the data structure of bibliographic information data for managing the bibliographic information of print data stored in each multifunction machine 101.

  When the CPU 301 of the multi-function peripheral 101 receives print data from the client device 102, it extracts bibliographic information (user name, document name, printer model name, print settings, etc.) from the print data and manages it as bibliographic information data. The print data is given a file name according to a predetermined naming rule, stored in a predetermined area of the HDD 304, and the information is included in the bibliographic information data (file name described later), the bibliographic information data, the print data, Is associated.

(Data items of bibliographic information data)
The status is a data item in which the status of the print data is registered, and a status such as unprinted, printed, or deleted is set.

  The file name is a data item in which the file name of the print data is registered.

  The user name is a data item in which the user name of the user who has instructed printing of the print data is registered.

  The document name is a data item in which the file name of the file from which the print data is created is registered.

  The time stamp is a data item in which date / time information indicating the date / time when the print data was created is registered.

  The file size is a data item in which the file size of print data is registered.

  The number of copies is a data item in which the number of copies set by the client device for the print data is registered.

  The number of pages is a data item in which the number of pages of print data is registered.

  Double side / single side is a data item in which print setting information (double side / single side) for printing print data is registered.

  The print layout is a data item in which page layout information (Nin1) of print data is registered.

  The paper size is a data item in which the paper size used when printing the print data is registered.

  Color / monochrome is a data item in which information indicating whether the print data is monochrome print data or color print data is registered. Of course, other color settings (two colors, etc.) may be added.

  The host name is a data item in which information (for example, an IP address or the like) for specifying a multifunction machine in which print data is stored is registered. Normally, information for specifying a multifunction device that has received print data is registered.

  The printer model is a data item in which information indicating which printer model print data can be printed is registered.

[FIG. 18] Example of Accumulated Print Data Operation Screen This accumulated print data operation screen is an operation screen displayed on the LCD display unit of the operation unit of the multi-function peripheral 101 during execution of the processing of FIG. Actually, it is displayed in step S916 of FIG.

  A print data list display unit 1801 is a display unit that displays a list of print data for which a logged-in user can issue a print instruction on the multifunction peripheral. Selection / non-selection of print data can be switched by a touch operation on the print data list display unit 1801. The information displayed here includes the document name, double-sided / single-sided, color / monochrome, print layout, paper size, number of pages, number of copies, time stamp, etc. in the bibliographic information.

  A delete button 1802 is a button used to input an instruction to delete the print data being selected in the print data list display unit 1801 to the CPU 301 of the multifunction peripheral 101.

  A print start button 1803 is a button used to input a print execution instruction for print data currently selected in the print data list display unit 1801 to the CPU 301 of the multifunction peripheral 101.

  A logout button 1804 is a button used to input a logout instruction to the CPU 301 of the multifunction machine 101.

  An update button 1805 is a button used for requesting bibliographic information to the multifunction device A again.

  The printed acquisition button 1806 is a button used to request bibliographic information data whose status is already printed. This is used when reprinting print data.

  A detailed information button 1807 is a button used when changing print settings or the number of copies. When a detailed information button 1807 is pressed, a print setting change screen (not shown) is displayed, and print settings and the number of copies can be changed.

  As described above, according to the present embodiment, it is possible to switch whether or not to immediately execute the process according to the data according to the type of data received from the client device. In particular, the print data is stored in the storage device and then printed after a user's print instruction is received. The FAX data is immediately stored in the storage device without being stored in the storage device. It becomes possible to switch processing.

  The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (18)

An image forming system capable of storing print data, wherein a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus are connected via a network,
The first image forming apparatus includes:
First receiving means for receiving data from the client device;
First determination means for determining whether the data received by the first reception means is print data or FAX data;
A FAX transmission unit configured to perform FAX transmission of the FAX data to a designated destination when the first determination unit determines that the data received by the first reception unit is FAX data;
Storage means for storing the print data in a storage device when the first determination means determines that the data received by the first reception means is print data;
Generating means for generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Means for sending
First request means for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
Second receiving means for receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information by the first requesting means; ,
Second request means for requesting print data to the image forming apparatus specified by the name information received by the second receiving means;
Printing means for printing the print data received from the image forming apparatus in response to the second request means,
The second image forming apparatus includes:
Third receiving means for receiving the name information transmitted from the first image forming apparatus;
Managing means for managing name information received by the third receiving means in a name information file for managing information on which image forming apparatus the print data is stored in;
Second transmission means for transmitting name information managed in the name information file in response to a request for name information from the first image forming apparatus;
An image forming system comprising: The first image forming apparatus includes:
2. The apparatus according to claim 1, further comprising: a first deleting unit that deletes the FAX data received by the first receiving unit when the first image forming apparatus does not have a FAX transmission function. The image forming system described. The first transmission unit further transmits user information of the print data to the second image forming apparatus,
The management unit manages information indicating in which image forming apparatus the print data is stored for each user specified by the user information in a name information file. The image forming system described. The first transmission unit further transmits model information of the first image forming apparatus to the second image forming apparatus,
The image forming system according to claim 3, wherein the management unit manages information indicating in which image forming apparatus the print data is stored for each model information using a name information file. The first image forming apparatus includes:
And a third transmission unit configured to transmit the print data stored in the storage unit to the other image forming apparatus when a print data transmission request is received from the other image forming apparatus. The image forming system according to claim 1. The first image forming apparatus includes:
First accepting means for accepting a deletion instruction for print data stored in the storing means;
The image forming system according to claim 1, further comprising: a second deletion unit that deletes the print data for which the deletion instruction is received by the first reception unit. The first image forming apparatus includes:
A third requesting unit for requesting the second image forming apparatus to delete the name information;
The second image forming apparatus includes:
7. The apparatus according to claim 1, further comprising a third deletion unit that deletes the name information file managed by the management unit in response to receiving the name information deletion request. The image forming system described. Functions as the first image forming apparatus in an image forming system capable of storing print data and including a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus connected via a network. An image forming apparatus,
First receiving means for receiving data from the client device;
First determination means for determining whether the data received by the first reception means is print data or FAX data;
A FAX transmission unit configured to perform FAX transmission of the FAX data to a designated destination when the first determination unit determines that the data received by the first reception unit is FAX data;
Storage means for storing the print data in a storage device when the first determination means determines that the data received by the first reception means is print data;
Generating means for generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Means for sending
First request means for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
Second receiving means for receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information by the first requesting means; ,
Second request means for requesting print data to the image forming apparatus specified by the name information received by the second receiving means;
An image forming apparatus comprising: a printing unit that prints print data received from the image forming apparatus in response to the second request unit. 9. The image according to claim 8, further comprising a first deletion unit that deletes the FAX data received by the first reception unit when the image forming apparatus does not have a FAX transmission function. Forming equipment. The image forming apparatus according to claim 8, wherein the first transmitting unit further transmits user information of the print data to the second image forming apparatus. The image forming apparatus according to claim 10, wherein the first transmission unit further transmits model information of the image forming apparatus to the second image forming apparatus. And a third transmission unit configured to transmit the print data stored in the storage unit to the other image forming apparatus when a print data transmission request is received from the other image forming apparatus. The image forming apparatus according to claim 8. First accepting means for accepting a deletion instruction for print data stored in the storing means;
The image forming apparatus according to claim 8, further comprising: a second deletion unit that deletes print data for which a deletion instruction has been received by the first reception unit. 14. The image forming apparatus according to claim 8, further comprising a third request unit configured to request the name information to be deleted from the second image forming apparatus. A control method of an image forming system capable of storing print data, wherein a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus are connected via a network,
In the first image forming apparatus,
A first receiving step of receiving data from the client device;
A first determination step of determining whether the data received in the first reception step is print data or FAX data;
A FAX transmission step of FAX transmitting the FAX data to a designated destination when it is determined in the first determination step that the data received in the first reception step is FAX data;
A storage step of storing the print data in a storage device when it is determined in the first determination step that the data received in the first reception step is print data;
A generation step of generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Sending process of
A first requesting step for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
A second receiving step of receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information in the first requesting process; ,
A second requesting step for requesting print data to the image forming apparatus specified by the name information received in the second receiving step;
A printing process for printing the print data received from the image forming apparatus in response to the second request process,
In the second image forming apparatus,
A third receiving step for receiving the name information transmitted from the first image forming apparatus;
A management step of managing the name information received in the third reception step with a name information file that manages information on which image forming apparatus the print data is stored;
A second transmission step of transmitting name information managed in the name information file in response to a request for name information from the first image forming apparatus;
An image forming system control method comprising: Functions as the first image forming apparatus in an image forming system capable of storing print data and including a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus connected via a network. An image forming apparatus control method comprising:
A first receiving step of receiving data from the client device;
A first determination step of determining whether the data received in the first reception step is print data or FAX data;
A FAX transmission step of FAX transmitting the FAX data to a designated destination when it is determined in the first determination step that the data received in the first reception step is FAX data;
A storage step of storing the print data in a storage device when it is determined in the first determination step that the data received in the first reception step is print data;
A generation step of generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Sending process of
A first requesting step for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
A second receiving step of receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information in the first requesting process; ,
A second requesting step for requesting print data to the image forming apparatus specified by the name information received in the second receiving step;
And a printing process for printing the print data received from the image forming apparatus in response to the second requesting process. A program for causing a computer to control an image forming system in which a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus that can store print data are connected via a network. And
In the first image forming apparatus, the computer is
First receiving means for receiving data from the client device;
First determination means for determining whether the data received by the first reception means is print data or FAX data;
A FAX transmission unit configured to perform FAX transmission of the FAX data to a designated destination when the first determination unit determines that the data received by the first reception unit is FAX data;
Storage means for storing the print data in a storage device when the first determination means determines that the data received by the first reception means is print data;
Generating means for generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Means for sending
First request means for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
Second receiving means for receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information by the first requesting means; ,
Second request means for requesting print data to the image forming apparatus specified by the name information received by the second receiving means;
In response to the second request means, function as a printing means for printing the print data received from the image forming apparatus,
In the second image forming apparatus, the computer is
Third receiving means for receiving the name information transmitted from the first image forming apparatus;
Managing means for managing name information received by the third receiving means in a name information file for managing information on which image forming apparatus the print data is stored in;
Second transmission means for transmitting name information managed in the name information file in response to a request for name information from the first image forming apparatus;
A program characterized by making it function. Functions as the first image forming apparatus in an image forming system capable of storing print data and including a plurality of image forming apparatuses including a first image forming apparatus and a second image forming apparatus connected via a network. A program for causing a computer to control the image forming apparatus,
The computer,
First receiving means for receiving data from the client device;
First determination means for determining whether the data received by the first reception means is print data or FAX data;
A FAX transmission unit configured to perform FAX transmission of the FAX data to a designated destination when the first determination unit determines that the data received by the first reception unit is FAX data;
Storage means for storing the print data in a storage device when the first determination means determines that the data received by the first reception means is print data;
Generating means for generating bibliographic information data for managing the print data;
First name information indicating the first image forming apparatus is transmitted to the second image forming apparatus in order to notify the second image forming apparatus that the print data is stored in the storage device. Means for sending
First request means for requesting the second image forming apparatus for name information indicating an image forming apparatus that is a storage location of print data;
Second receiving means for receiving name information indicating an image forming apparatus that is a storage location of print data transmitted from the second image forming apparatus in response to a request for name information by the first requesting means; ,
Second request means for requesting print data to the image forming apparatus specified by the name information received by the second receiving means;
A program that functions as a printing unit that prints print data received from the image forming apparatus in response to the second request unit.

Images