Information processing apparatus, management apparatus, control method thereof, and program

Abstract

To prevent operating information of one MFP from being displayed as operating information of two separate MFPs when an MFP and a DFE connected to the MFP are connected to the same network.SOLUTION: An information collection PC 104 searches a network 106 and, if an MFP 101 and a DFE 102 connected to the MFP 101 and configured to send print data to the MFP 101 are found in the search, collects and stores operating information from either of the MFP 101 and the DFE 102.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to the operation management of a system in which an image processing apparatus and a control apparatus connected to the image processing apparatus and transmitting print data to the image processing apparatus are connected to the same network.

Background Art

[0002] In recent years, many image processing apparatuses such as printers, scanners, FAX machines, or Multi Function Printers (hereinafter referred to as "MFPs") that comprehensively have these functions have come to have a network communication function. An MFP equipped with a communication function communicates with a server or a PC on a network and realizes functions such as transmitting scan data from the MFP to the PC.

[0003] On the other hand, in professional-use products for printing companies and design offices, there is a desire to perform more advanced print control than office-use products, such as image processing and scheduling of print jobs. Such advanced print control can be achieved by connecting a control apparatus called a Digital Front End controller (hereinafter referred to as "DFE") to the MFP. In printing companies, design offices, etc., the DFE is often connected to the MFP.

[0004] Although the DFE and the MFP each have device information in their respective control units, there is a desire to centrally manage the device information that is distributedly managed in the respective control units of the DFE and the MFP. In Patent Document 1, in a configuration in which a DFE connected to an MFP is connected to a network, a technique has been proposed in which the DFE acquires device information from the MFP in response to a request from a device management apparatus, merges it with its own device information, and responds. Thereby, the device information that is distributedly managed by each of the DFE and the MFP can be centrally managed.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, it is conceivable that a DFE is connected to an MFP and both the MFP and the DFE are connected to the same network. In this case, operation information is collected from both the MFP and the DFE and transmitted to the management device. For this reason, in the management device, the MFP and the DFE are managed as two separate devices. There was a problem that although the device for which the operation status is to be managed is one MFP, it appears to the user that there are two identical devices.

[0007] The present invention has been made to solve the above problems. An object of the present invention is to provide a mechanism that enables a management device to manage the operation of an image processing device without duplication in a system in which an image processing device and a control device connected to the image processing device for transmitting print data are connected to the same network.

Means for Solving the Problems

[0008] The present invention is an information processing device that collects operation information from devices on a network, and includes a search means for searching for devices on the network, and when an image processing device and a control device connected to the image processing device for transmitting print data to the image processing device are found by the search by the search means, a collection means for collecting operation information from either one of the image processing device and the control device, and a storage means for storing the collected operation information.

Effects of the Invention

[0009] According to the present invention, in a system in which an image processing apparatus and a control apparatus connected to the image processing apparatus and transmitting print data to the image processing apparatus are connected to the same network, a management apparatus can manage the operation of the image processing apparatus without duplication. As a result, it is possible to prevent the operation information of one MFP from being actually displayed as if it were the operation information of separate MFPs.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13A

Figure 13B

Figure 14A

Figure 14B

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. Note that the configurations shown in the following embodiments are examples, and the present invention is not limited to the illustrated configurations.

[0012] 〔First Embodiment〕 <Configuration of Device Operation Management System> FIG. 1 is a diagram showing an example of the connection environment of a device operation management system showing an embodiment of the present invention. As shown in FIG. 1, the device operation management system of the present embodiment (hereinafter also referred to as "this system") includes an MFP (Multi Function Printer) 101 and a DFE (Digital Front End controller) 102. Further, this system includes a client PC 103, an information collection PC 104, and a device operation management apparatus 105.

[0013] The MFP 101, DFE 102, client PC 103, and information collection PC 104 are communicably connected via a network 106. Further, the DFE 102 and the MFP 101 are connected by an internal interface 107 for transferring images at high speed.

[0014] In this system, a print job is sent from the client PC 103 to the DFE 102 through the network 106. The DFE 102 sequentially performs rasterization processing on the print job received from the client PC 103 via the network 106, and transfers the rasterized image data (also referred to as print data) to the MFP 101 via the internal interface 107. The MFP 101 performs necessary processing on the rasterized image data received from the DFE 102 via the internal interface 107, and prints and outputs it onto actual paper.

[0015] Note that it is also possible to send an office-oriented print job or the like from the client PC 103 to the MFP 101 via the network 106. The MFP 101 sequentially processes the print job received from the client PC 103, and prints and outputs it onto actual paper using the marking engine 220 (Fig. 2). Also, the MFP 101 can perform copying (copy job) using the connected scanner, or send the scanned result to the client PC 103 (transmission job). Further, the MFP 101 can also print (fax job) the facsimile (hereinafter referred to as "fax") received data received via a telephone line (not shown).

[0016] The DFE 102 communicates with the MFP 101, acquires and manages the serial number and product name information of the MFP 101, etc. Also, the DFE 102 manages the job execution information it has executed itself.

[0017] The information collection PC 104 is an information processing device that searches for devices connected on the network 106 and registers them in a device list described later. The information collection PC 104 collects and stores the information of the devices registered in the device list via the network 106. Also, the information collection PC 104 sends the collected and stored information to the device operation management device 105.

[0018] The device operation management apparatus 105 displays information that printing administrators view daily for the purpose of managing the productivity and operation rate of a plurality of MFPs. The device operation management apparatus 105 has means for receiving information from the information collection PC 104, storing it, and preparing to display the device operation status. The device operation management apparatus 105 may be realized by one computer or may be realized by a plurality of computers. The device operation management apparatus 105 may be configured to be realized by using, for example, a cloud service or the like.

[0019] The client PC 103 accesses the device operation management apparatus 105 and displays the information prepared for display by the device operation management apparatus 105. Thereby, the printing administrator can view the operation status of a desired device. The client PC 103 is, for example, various information processing apparatuses such as a personal computer, a tablet terminal, and a smartphone.

[0020] <Device configurations of MFP 101 and DFE 102> FIG. 2 is a block diagram showing an example of the hardware configuration of MFP 101 and DFE 102. MFP 101 has a controller unit including a CPU 211, a RAM 212, and an HDD 213. Further, MFP 101 includes a marking engine 220, a scanner 221, an image processing unit 216, an image processing I / F unit 217, a device I / F unit 218, and a network I / F unit 214. Various programs are stored in the HDD 213 or the like and are read into the RAM 212 and executed by the CPU 211 as necessary.

[0021] DFE 102 has a controller unit including a CPU 201, a RAM 202, and an HDD 203. Further, DFE 102 includes an image processing unit 205, an image processing I / F unit 206, and a network I / F unit 204. Various programs are stored in the HDD 203 or the like and are read into the RAM 202 and executed by the CPU 201 as necessary. DFE 102 functions as a control device that provides functions to MFP 101. As described above, the system in which the MFP 101 and the DFE 102 are connected can be said to be a system in which a plurality of control units are connected to the operating device. Note that both the MFP 101 and the DFE 102 may be provided with a display / operation device (not shown) or the like as necessary.

[0022] <Device Configuration of Information Collection PC 104 and Device Operation Management Device 105> FIG. 3 is a block diagram showing an example of the hardware configuration of the information collection PC. The information collection PC 104 includes a CPU 301, a RAM 302, an HDD 303, and a network I / F unit 304. Hardware such as the CPU 301, the RAM 302, and the HDD 303 constitutes a so-called computer. Various programs are stored in the HDD 303 or the like, and are read into the RAM 302 by the CPU 301 as necessary and control is executed.

[0023] FIG. 4 is a block diagram showing an example of the hardware configuration of the device operation management device 105. The device operation management device 105 includes a CPU 401, a RAM 402, an HDD 403, and a network I / F unit 404. Hardware such as the CPU 401, the RAM 402, and the HDD 403 constitutes a so-called computer. Various programs are stored in the HDD 403 or the like, and are called into the RAM 402 by the CPU 401 as necessary and control is executed.

[0024] <Processing Function Configuration of Information Collection PC 104> FIG. 5 is a block diagram showing an example of the configuration of the processing functions of the information collection PC 104. Each software module of the information collection PC 104 shown in FIG. 5 is stored in the HDD 303 of the information collection PC 104, and is read into the RAM 302 as needed and controlled and executed by the CPU 301 to function. Note that, although it is assumed that one CPU 302 executes each process shown in the flowchart described later in the information collection PC 104, other modes may be used. For example, it is also possible to execute each process shown in the flowchart described later by causing a plurality of processors and memories to cooperate. In addition, some processes such as data transmission and reception are realized in cooperation with a hardware circuit such as a communication interface.

[0025] The network management unit 501 communicates with devices connected on the network 106 such as the DFE 102, MFP 101, and client PC 103, and the device operation management device 105 on the cloud via the network 106 using the network I / F unit 304.

[0026] The device search processing unit 502 is a software module that searches for devices connected on the network 106. For example, it is executed periodically, at the time of new settings, or when a new device is added, and registers the operation management target devices on the network in a device list described later.

[0027] The device operation information collection processing unit 503 is a software module that collects operation information from the operation management target devices registered in the device list. The collected operation information is stored in the data storage unit 505. Note that the data storage unit 505 stores information on the HDD 303 of the information collection PC 104, but may store the information in a predetermined storage area such as the RAM 302 or an external storage area. The device operation information transmission processing unit 504 is a software module that periodically transmits the device operation information collected by the device operation information collection processing unit 503 and stored in the data storage unit 505 to the device operation management device 105.

[0028] <Functional Configuration of Device Operation Management Device 105> FIG. 6 is a block diagram showing an example of the configuration of the processing functions of the device operation management apparatus 105. Each software module of the device operation management apparatus 105 shown in FIG. 6 is stored in the HDD 403 of the device operation management apparatus 105, read into the RAM 402 as needed, and controlled and executed by the CPU 401 to function. Note that, although it is assumed that one CPU 401 executes each process shown in the flowchart described later in the device operation management apparatus 105, other embodiments may be used. For example, a plurality of processors and memories may be made to cooperate to execute each process shown in the flowchart described later. Also, some processes such as data transmission and reception are realized in cooperation with a hardware circuit such as a communication interface.

[0029] The network management unit 601 communicates with the information collection PC 104, the client PC 103, and devices on the Internet using the network I / F unit 404. The operation information reception processing unit 602 is a software module that receives the operation information transmitted from the information collection PC 104. The device operation information management unit 603 is a software module that appropriately manages the device operation information received by the operation information reception processing unit 602 and stores it in the data storage unit 605. Note that the data storage unit 605 stores information on the HDD 403 of the device operation management apparatus 105, but may store it in a predetermined storage area such as the RAM 402 or an external storage area.

[0030] The device operation information display processing unit 604 is a software module for displaying the device operation information managed by the device operation information management unit 603 on the client PC 103 or a device on the Internet. The device operation information display processing unit 604 generates information indicating the operation status of the device based on the operation information of the device managed by the device operation information management unit 603 (prepares a display screen showing the operation status of the device).

[0031] FIG. 7(a) is a diagram showing an example of the data structure of the device list managed by the device operation information management unit 603 of the first embodiment. The device list is composed of information on a plurality of devices to be managed (hereinafter referred to as "device 702"). Each device 702 is composed of device information 703 and MFP information 705. The device information 703 stores information 704 such as the product name and serial number of the corresponding device. The MFP information 705 stores information 706 such as the IP address and MAC address of the corresponding MFP.

[0032] Figure 7(b) is a diagram showing an example of the data structure of the transmission operation information 711 transmitted from the MFP 101 to the information collection PC 104. The transmission operation information 711 includes information 712 such as serial number, date and time, product name, counter information, job type, job type details, job number information since the previous transmission, and print sheet number information for each job.

[0033] Figure 7(c) is a diagram showing an example of the data structure of the operation information managed by the device operation information management unit 603 of the first embodiment. The operation information 721 is managed for each serial number 722 of the device, and is composed of the total number of jobs 724 and the total number of pages 725 for each job type 723. The job types 723 include print jobs, copy jobs, fax jobs, scan jobs, and the like.

[0034] Figure 8 is a flowchart showing an example of the process of searching for devices on the network and registering them in the device list by the device search processing unit 502 in the information collection PC 104 in the first embodiment. That is, the process of this flowchart is realized by the CPU 301 of the information collection PC 104 loading and executing a program stored in the HDD 303 or the like into the RAM 302 as needed.

[0035] In S801, the device search processing unit 502 searches for devices via the network 106 connected to the network I / F unit 304. For example, the device search processing unit 502 broadcasts a search packet. Note that multicast may be used instead of broadcast. Next, in S802, the device search processing unit 502 acquires the device information of the device that responded in the search of S801, and stores it in the memory 302 or the HDD 303 via the data storage unit 505.

[0036] Next, in S803, the device search processing unit 502 determines whether the corresponding device information has been registered in the device list. If it has been registered (Yes in S803), the device search processing unit 502 ends the processing of this flowchart.

[0037] On the other hand, if it has not been registered yet (No in S803), the device search processing unit 502 proceeds to S804. In S804, the device search processing unit 502 determines whether the device information obtained in S802 is the device information of the MFP. If it is not the device information of the MFP (No in S804), the device search processing unit 502 ends the processing of this flowchart without adding the device information obtained in S802 to the device list.

[0038] On the other hand, if it is determined that it is the device information of the MFP (Yes in S804), the device search processing unit 502 proceeds to S805. In S805, the device search processing unit 502 adds the device information obtained in S802 to the device list. Specifically, the device search processing unit 502 adds the information of 702 to 706 to the device list 701 with the configuration as shown in FIG. 7(a) based on the device information obtained in S802. After the processing of S805, the device search processing unit 502 ends the processing of this flowchart.

[0039] The device list registered as described above is stored in the data storage unit 505, transmitted to the device operation management device 105, and managed by the device operation information management unit 603 of the device operation management device 105. Also, the device operation information collection processing unit 503 of the information collection PC 104 collects operation information as shown in FIG. 7(b) from the devices registered in the above-described device list, and stores the collected operation information in the data storage unit 505. Further, the device operation information transmission processing unit 504 transmits the operation information stored in the data storage unit 505 to the device operation management device 105. The device operation information management unit 603 of the device operation management device 105 manages the operation information (including the serial number of the MFP) of the MFP 101 as shown in FIG. 7(b) received from the information collection PC 104 in a data structure as shown in FIG. 7(c) based on the serial number.

[0040] As described above, according to the first embodiment, in a printing system in which the MFP and the DFE are connected to the same network, the device operation management device can manage the operation status of the same MFP without duplication. Thereby, it is possible to prevent the operation information of actually one MFP from being displayed as if it were the operation information of separate MFPs.

[0041] 〔Second Embodiment〕 In the first embodiment described above, the configuration for enabling the management of operation information without duplication by registering the searched MFP in the device list and controlling not to register the DFE connected to the MFP in the device list has been described. Note that some users may desire to manage the operation information of the DFE in detail, and an embodiment that satisfies this desire will be described below.

[0042] FIG. 9 is a diagram showing an example of a setting screen for the information collection PC 104 in the second embodiment. This screen is actually displayed on the display unit of the client PC 103 and instructed by a user such as a print administrator by accessing the information collection PC 104 from the client PC 103.

[0043] The setting screen 901 is a screen that enables a user to select and set in advance the source for acquiring device operation information. The user selects the source for acquiring device operation information using the radio buttons 902 and 903. When acquiring device operation information from the MFP 101, the radio button 902 is selected. On the other hand, when acquiring device operation information from the DFE 102, the radio button 903 is selected. By selecting either of the radio buttons 902 and 903 and pressing the "Yes" button 904, the settings on the setting screen 901 can be enabled and the setting screen 901 can be closed. Note that this setting is stored in the HDD 303 of the information collection PC 104. Also, by pressing the "Cancel" button 905, the settings on the setting screen 901 can be disabled and the setting screen 901 can be closed.

[0044] Note that in the second embodiment, the "MFP information" indicated by 705 in Fig. 7(a) shall be read as "device information acquisition source information". Also, when the DFE 102 is set as the device operation information acquisition source on the setting screen 901, the transmission operation information transmitted from the DFE 102 to the information collection PC 104 shall include the serial number of the MFP 101 that the DFE 102 has acquired and managed from the MFP 101.

[0045] Fig. 10 is a flowchart showing an example of the process of searching for devices on the network and registering them in the device list in the device search processing unit 502 in the information collection PC 104 in the second embodiment. That is, the process of this flowchart is realized by the CPU 301 of the information collection PC 104 loading a program stored in the HDD 303 or the like into the RAM 302 and executing it as necessary.

[0046] First, since S1001 to S1003 are the same as the processes of S801 to S803 in Fig. 8, the description thereof is omitted. In S1004, the device search processing unit 502 determines, from the device information acquired in S1002, whether the device information is the device information of the MFP or the DFE, and determines whether the device corresponding to the device information matches the device operation information acquisition source set on the screen 901 of FIG. 9. If they do not match (No in S1004), the device search processing unit 502 ends the processing of this flowchart without adding the device information acquired in S1002 to the device list.

[0047] On the other hand, if it is determined that the device corresponding to the device information acquired in S1002 matches the device information acquisition source (Yes in S1004), the device search processing unit 502 proceeds to S1005 for processing. In S1005, the device search processing unit 502 adds the device information acquired in S1002 to the device list. Specifically, the device search processing unit 502 adds the information of 702 to 706 to the device list 701 having the above-described configuration based on the device information acquired in S1002. After the processing of S1005, the device search processing unit 502 ends the processing of this flowchart.

[0048] The device list registered as described above is stored in the data storage unit 505, transmitted to the device operation management device 105, and managed by the device operation information management unit 603 of the device operation management device 105. In addition, the device operation information collection processing unit 503 of the information collection PC 104 collects operation information from the devices registered in the above-described device list, and the device operation information transmission processing unit 504 transmits the collected operation information to the device operation management device 105. The device operation information management unit 603 of the device operation management device 105 manages the operation information (including the serial number of the MFP) of the MFP 101 or DFE 102 received from the information collection PC 104 in a data structure as shown in FIG. 7(c) based on the serial number.

[0049] As described above, according to the second embodiment, it becomes possible to manage the operation information for the same MFP without duplication using the operation information acquired from the device selected and set as the device information acquisition source. In addition, by the print administrator or the like selecting and setting the DFE as the device information acquisition source, it becomes possible to manage the operation information of the DFE in detail.

[0050] 〔Third Embodiment〕 In the first and second embodiments described above, when searching on the network and finding the MFP and the DFE connected to the MFP, the operation information is collected from either one of these MFPs and DFE. Then, using the information collected in this way, the device operation management device 105 manages the operation information of the device. That is, a configuration for managing the operation information for the same MFP without duplication using the operation information collected from either the MFP or the DFE has been described. Since the jobs executed by the DFE and the MFP are different, users who want to perform a detailed analysis of the number of printed sheets and the number of jobs have a desire to integrally manage the operation information of each of the MFP and the DFE. In this embodiment, a configuration for integrally managing the operation information of each of the MFP and the DFE will be described. In this embodiment, it is assumed that the information collection PC 104 collects the operation information from both the MFP 101 and the DFE 102.

[0051] FIG. 11 is a diagram showing an example of an operation status screen for displaying the display content prepared in the device operation information display processing unit 604 of the third embodiment on the client PC 103. On the operation status screen 1101, a device list is displayed in the device list 1102 on the left side of the screen. Although the MFP 101 and the DFE 102 are recognized as separate devices on the network, in this device list, the information is displayed as one device. In the example of FIG. 11, “AB-Cx00” displayed at the top of the device list 1102 is a device composed of the MFP 101 and the DFE 102, but is displayed as one device. The MFP 101 and the DFE 102 are connected by the internal interface 107, and transmit the operation information including the same serial number to the information collection PC 104. The consumable information display 1103 displays the remaining amount of consumables.

[0052] When any device is selected and instructed (for example, double-clicked) from the device list displayed in the device list 1102, the detailed information of the device is displayed as, for example, 1204 in FIG. 12.

[0053] FIG. 12 is a diagram showing an example of the display of the detailed information of the device in the third embodiment. In the detailed information 1204, the total number of print jobs and the number of pages are displayed by synthesizing (integrating) the information executed by both the MFP 101 and the DFE 102 that constitute the device selected in the device list 1102.

[0054] FIGS. 13A and 13B are diagrams showing an example of the data structure of the device list, transmission operation information, and operation information according to the third embodiment. Hereinafter, FIGS. 13A and 13B are collectively referred to simply as "FIG. 13".

[0055] FIG. 13(a) shows an example of the data structure of the device list managed by the device operation information management unit 603. The device list 1301 is composed of information of a plurality of devices (hereinafter "device 1302"). Each device 1302 is composed of device information 1303, MFP information 1305, and DFE information 1307.

[0056] The device information 1303 stores device information 1304 common to the MFP and the DFE, such as the serial number and engine name obtained from the MFP or the DFE. Regarding the counter information, information obtained from the more accurate MFP 101 may be used. The MFP information 1305 stores MFP-specific information 1306 such as the IP address and MAC address of the corresponding MFP. Similarly, the DFE information 1307 stores DFE-specific information 1308 such as the DFE product name, IP address, and MAC address of the corresponding DFE.

[0057] Note that the device search processing unit 502 of the third embodiment searches for devices on the network 106 (similar to S801 in FIG. 8), acquires the device information of the devices that responded (similar to S802), and stores it in the memory 302 or the HDD 303 via the data storage unit 505. Further, if the corresponding device information is not already registered in the device list (similar to S803), the device search processing unit 502 adds the information from 1302 onward to the device list 1301 configured as shown in FIG. 13(a) based on the acquired device information. At this time, if the acquired device information is the device information of the MFP, MFP information 1305 to 1306 is added, and if the acquired device information is the device information of the DFE, DFE information 1307 to 1308 is added.

[0058] The device list registered as described above is stored in the data storage unit 505, transmitted to the device operation management device 105, and managed by the device operation information management unit 603 of the device operation management device 105. Also, the device operation information collection processing unit 503 of the information collection PC 104 collects operation information from the devices registered in the above-described device list, and the device operation information transmission processing unit 504 transmits the collected operation information to the device operation management device 105.

[0059] FIG. 13(b) shows an example of the data structure of the transmission operation information 1311 transmitted from the MFP 101 or the DFE 102 to the information collection PC 104. The transmission operation information 1311 includes information 1312 such as serial number, date and time, product name, counter information, job type, job type details, and print count information for each job. Note that the serial number included in the transmission operation information transmitted from the DFE 102 to the information collection PC 104 corresponds to the serial number of the MFP 101 that the DFE 102 has acquired and manages from the MFP 101.

[0060] FIG. 13(c) shows an example of the data structure of the operation information managed by the device operation information management unit 603. The operation information 1321 is managed for each device information (hereinafter referred to as "device 1322"). Each device 1322 is composed of device information 1323, MFP operation information 1325, and DFE operation information 1336.

[0061] In the device information 1323, information 1324 such as serial number, counter information, and consumable information is managed.

[0062] The MFP operation information 1325 is based on the operation information collected from the MFP. The MFP operation information 1325 is composed of the total number of jobs and the total number of pages for each job type such as print job 1326, copy job 1333, scan job 1334, and FAX job 1335.

[0063] Note that the print job 1326 is classified into a DFE job 1327 and an MFP job 1328 as detailed classifications. The DFE job 1327 is the print job information input from the DFE 102 to the MFP 101. The DFE job 1327 is composed of the total number of jobs 1329 and the total number of pages 1330. Similarly, the MFP job 1328 is composed of the total number of jobs 1331 and the total number of pages 1332.

[0064] The DFE operation information 1336 is based on the operation information collected from the DFE. The DFE operation information 1336 is composed of a print job 1337 and a scan job 1340. The print job 1337 is composed of a print detailed type PDF (Portable Document Format) job 1338 and a PostScript job 1339, and the total number of jobs and the total number of pages are managed for each job.

[0065] The scan job 1334 is managed with the total number of jobs and the total number of pages for each job as the combined information of the scan job performed by the MFP and the scan job instructed by the DFE. Note that at least the DFE job 1327 and the print job 1337 include information on the update date and time (not shown).

[0066] The device operation information management unit 603 of the device operation management device 105 associates the operation information of the MFP 101 and the DFE 102 (including the serial number of the MFP) received from the information collection PC 104 with the serial number and manages it in the data structure as shown in FIG. 13(c). At this time, it is assumed that the serial numbers included in the operation information collected from the MFP 101 and the operation information collected from the DFE 102 are the same. That is, the operation information of the MFP 101 and the operation information of the DFE 102 are managed in association with each other using the serial number as a key.

[0067] FIGS. 14A and 14B are flowcharts showing an example of a process for creating operation information to be displayed on the client PC 103 in the device operation information display processing unit 604 in the device operation management device 105 according to the third embodiment. The process shown in FIGS. 14A and 14B is realized by the CPU 401 of the device operation management device 105 loading a program stored in the HDD 403 or the like into the RAM 402 and executing it as necessary.

[0068] First, in S1401, the device operation information display processing unit 604 requests the device operation information management unit 603 to acquire the operation information (MFP operation information 1325 and DFE operation information 1336) of any device in the device list. Hereinafter, the device for which the operation information is acquired here is referred to as the "target device".

[0069] In S1402, the device operation information display processing unit 604 checks whether the operation information has been acquired up to the end of the device list. If the operation information has not been acquired up to the end of the device list yet, that is, if there is still a device in the device list for which the operation information has not been acquired (No in S1402), the device operation information display processing unit 604 proceeds to S1403. In this case, the operation information of the device requested in S1401 can be acquired.

[0070] In S1403 to S1405, the device operation information display processing unit 604 synthesizes the MFP operation information 1325 and the DFE operation information 1336 acquired in S1401 to create display information. Hereinafter, each step will be described.

[0071] In S1403, the device operation information display processing unit 604 creates print job operation display information for the corresponding device using the operation information acquired in the above S1401. The details of this processing will be described with reference to FIG. 14B. Next, in S1404, the device operation information display processing unit 604 creates scan job operation display information for the corresponding device using the operation information acquired in the above S1401. Next, in S1405, the device operation information display processing unit 604 creates operation display information for other jobs such as the FAX job 1335 of the corresponding device using the operation information acquired in the above S1401.

[0072] Next, in S1406, the device operation information display processing unit 604 requests the device operation information management unit 603 to acquire the operation information of the next device from the device operation information management unit 603, and transfers the processing to S1402. Here, if the operation information has already been acquired up to the end of the device list, that is, if there is no information on the device for which the operation information is to be acquired in the device list (Yes in S1402), the device operation information display processing unit 604 ends the processing of this flowchart.

[0073] As described above, the operation display information generated (prepared for display) by the device operation management device 105 is transmitted to the client PC 103 in response to a request from the client PC 103 and is displayed on the client PC 103.

[0074] FIG. 14B is a flowchart showing the details of the print job operation expression information creation process of S1403 in FIG. 14A. First, in S1411, the device operation information display processing unit 604 compares the DFE job 1327 in the MFP operation information 1325 with the print job 1337 in the DFE operation information 1336 to check whether they match. Here, in the DFE job 1327 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336, if the total number of jobs and the total number of pages are equal respectively, it is determined that they match. If they match (Yes in S1411), the device operation information display processing unit 604 proceeds to S1414.

[0075] In S1414, it is assumed that the device operation information display processing unit 604 uses the information of the print job 1337 in the DFE operation information 1336. In this case, in the next S1415, the device operation information display processing unit 604 adds up the MFP job 1328 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336 to obtain the total print job operation information of the entire device. By performing this process, the results of print jobs executed by the MFP alone without going through the DFE can be integrated with the print results managed by the DFE. For example, it becomes possible to correctly count the results of status prints that print the status information of the MFP, and the results of print jobs directly received and printed by the MFP from a mobile terminal or the like.

[0076] On the other hand, if the DFE job 1327 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336 do not match (No in S1411), the device operation information display processing unit 604 proceeds to S1412.

[0077] In S1412, the device operation information display processing unit 604 compares the time when the operation information was received from the device for the DFE job 1327 in the MFP operation information 1325 and the print job 1337 in the DFE operation information 1336, and determines which information is the latest. If the print job 1337 in the DFE operation information 1336 is newer (DFE case in S1412), the device operation information display processing unit 604 proceeds to S1414.

[0078] On the other hand, if the DFE job 1327 in the MFP operation information 1325 is newer (MFP case in S1412), the device operation information display processing unit 604 proceeds to S1413. In S1413, the device operation information display processing unit 604 shall use the information of the DFE job 1327 in the MFP operation information 1325. In this case, in the next S1415, the device operation information display processing unit 604 shall add up the MFP job 1328 in the MFP operation information 1325 and the DFE job 1327 in the MFP operation information 1325 to obtain the total print job operation information of the entire device.

[0079] Next, in S1416, the device operation information display processing unit 604 shall obtain the detailed job information (information of the PDF job 1338 and the PostScript job 1339) in the print job 1337 in the DFE operation information 1336.

[0080] Next, in S1417, the device operation information display processing unit 604 shall calculate the ratio of each job from the total print job operation obtained in S1415 above and the detailed job information obtained in S1416 above, and create the information necessary for display. At this time, the display screen shall be generated so as to display the ratio of each job in descending order of the number of jobs. In the detailed display screen, the display screen shall also be generated so as to display the ratios of the PDF job 1338 and the PostScript job 1339. Also, the display screen shall be generated so that the ratio of the jobs passing through the DFE within the same job type and the ratio of the jobs processed by the MFP without passing through the DFE can be known.

[0081] After the processing of S1417 above, the device operation information display processing unit 604 shall end the processing of this flowchart. In this way, for the overlapping parts between the operation information of the MFP 101 and the operation information of the DFE 102, the operation information shall be synthesized (integrated) using either of the operation information.

[0082] As described above, in this embodiment, when displaying the printed job types and the like, the operation information of both the MFP and the DFE is synthesized and displayed. At this time, the number of copy jobs, the number of FAX jobs, etc. executed by the MFP are obtained from the MFP operation information. On the other hand, the print jobs executed by the DFE are obtained from the DFE operation information.

[0083] According to the above-described third embodiment, in a printing system where an MFP and a DFE are connected to the same network, the device operation management apparatus can manage operation information for the same MFP without duplication and appropriately integrate and manage distributed job information. As a result, it is possible to prevent the operation information of actually one MFP from being displayed as if it were the operation information of separate MFPs.

[0084] Note that since the jobs executed by the DFE and the MFP are different, in order to perform a detailed analysis of the number of printed sheets and the number of jobs, information on both the MFP operation information and the DFE operation information is required. In this embodiment, display information is created by synthesizing both pieces of operation information. As a result, it becomes possible to perform a detailed analysis of the number of printed sheets and the number of jobs.

[0085] In the above example, in the case where information of the same job type, such as a print job, is present in both the MFP operation information and the DFE operation information, a configuration in which they are totaled to obtain the total of the job type has been described. However, it may be possible to switch whether to total the information of the same job type in the MFP operation information and the DFE operation information according to user settings.

[0086] Also, in the case where information of the same PDL (Page Description Language) type is present in both the MFP operation information and the DFE operation information, they may be totaled to obtain the total. Then, a display screen is generated so as to arrange and display in descending order for each PDL job type. Further, when a detailed display instruction is given, the ratio of the jobs of each PDL type may be displayed. Also, it may be displayed so that the ratio of the jobs passing through the DFE within the PDL type and the ratio of the jobs processed by the MFP without passing through the DFE can be understood. Note that it may be possible to switch whether to total the information of the same PDL type in the MFP operation information and the DFE operation information according to user settings.

[0087] In addition, a plurality of applications are prepared as the device operation information display processing unit 604, and the determination of aggregation and the operation information used for display may be different for each application. For example, in the first application, the operation status is display-controlled based on the sum of the MFP operation information and the DFE operation information. Also, in the second application, in order to manage the jobs executed by the MFP without going through the DFE, the operation status is display-controlled based on the MFP operation information. Furthermore, in the third application, since management in units of print jobs is required, the operation status is display-controlled based on the information on the DFE side. Note that on the client PC 103, by accessing the URL of the application for which the operation status is to be displayed, the desired operation status can be displayed.

[0088] In the above-described embodiments, the information collection PC 104 generates the device list and collects and transmits the operation information. However, a configuration in which the MFP 101 or the DFE 102 performs equivalent control may also be used. That is, the MFP 101 or the DFE 102 may have the functions of the above-described information collection PC 104. Also, the collection control of the operation information provided by the PC 104, the integrated management control of the operation information provided by the management device 105, the generation of the screen related to the operation information, and the provision to the client PC may be realized as one server or one cloud service.

[0089] As described above, in a printing system in which the MFP 101 and the DFE 102 are connected to the same network, the device operation management device 105 can manage the operation of the same MFP without duplication and integrally manage the distributed job information. That is, there is no need to display duplicate printing devices, and the job statuses separately executed by the MFP and the DFE can also be combined and displayed, reducing the network communication cost. That is, it becomes possible to appropriately manage the operation status of the operating devices in a system in which a plurality of control units are connected to the operating devices.

[0090] Note that the configurations and contents of the various types of data described above are not limited to this, and it goes without saying that they can be configured with various other configurations and contents according to the use and purpose. Although one embodiment has been described above, the present invention can be implemented, for example, as an embodiment of a system, device, method, program, or storage medium. Specifically, it may be applied to a system composed of a plurality of devices, or may be applied to a device composed of a single device. Also, all configurations combining the above-described embodiments are included in the present invention.

[0091] (Other Embodiments) The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions. Also, the present invention may be applied to a system composed of a plurality of devices or to a device composed of a single device. The present invention is not limited to the above-described embodiments, and various modifications (including organic combinations of the respective embodiments) are possible based on the gist of the present invention, and they are not excluded from the scope of the present invention. That is, all configurations combining the above-described embodiments and their modified examples are included in the present invention.

Description of Reference Numerals

[0092] 101 MFP 102 DFE 103 Client PC 104 Information Collection PC 105 Equipment Operation Management Device

Claims

1. An information processing apparatus for collecting operation information from devices on a network, comprising: search means for searching for devices on the network; collecting means for collecting operation information from either one of the image processing apparatus and the control apparatus when the image processing apparatus and the control apparatus connected to the image processing apparatus and transmitting print data to the image processing apparatus are found by the search by the search means; storage means for storing the collected operation information; An information processing apparatus characterized by comprising the above.

2. The information processing apparatus according to claim 1, wherein when the image processing apparatus and the control apparatus connected to the image processing apparatus and transmitting print data to the image processing apparatus are found by the search by the search means, the collecting means collects operation information from the image processing apparatus and does not collect operation information from the control apparatus that transmits print data to the image processing apparatus.

3. The information processing apparatus according to claim 1 or 2, further comprising transmission means for transmitting the operation information stored in the storage means to a management apparatus for managing operation information.

4. having setting means for setting which of the image processing apparatus and the control apparatus to collect operation information from; The information processing apparatus according to claim 1, wherein when the image processing apparatus and the control apparatus connected to the image processing apparatus and transmitting print data to the image processing apparatus are found by the search by the search means, the collecting means collects operation information from the apparatus set by the setting means among the searched image processing apparatus and the control apparatus.

5. A control method for an information processing apparatus that collects operation information from devices on a network, comprising: a search step of searching for devices on the network; a collection step of collecting operation information from either one of the image processing apparatus and the control apparatus when the image processing apparatus and the control apparatus connected to the image processing apparatus and transmitting print data to the image processing apparatus are found by the search in the search step; a storage step of storing the operation information collected in the collection step in a storage area; A control method for an information processing apparatus, characterized by comprising the above.

6. A program for causing a computer to execute the control method of the information processing apparatus according to claim 5.

Images