Information processing apparatus, information processing system, control method and program

Abstract

To provide an information processing apparatus, an information processing system or the like, in cloud printing, which monitor each job log and correctly store each job history.SOLUTION: Disclosed is an information processing apparatus which manages each job log of a printing device to which each print job is submitted from a client terminal installed with an extended monitoring application via a network and which executes printing via the network. The information processing apparatus comprises: a storage unit for storing jot history information having plural job logs per job including each job identifier which can identify each job; a first receiving unit for receiving each job log transmitted by the printing device; a second receiving unit for receiving a job list per job including each job identifier transmitted by the extended monitoring application; an addition unit for adding each job log received by the first receiving unit to the job history information; and an update unit for updating the job history information based on the job list received by the second receiving unit and the job history information.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing system, a control method, and a program.

Background Art

[0002] In recent years, general-purpose printer drivers using industry-standard protocols such as IPP (Internet Printing Protocol) have been proposed. As general-purpose printer drivers, there are local printer drivers that connect directly to printers and cloud printer drivers that transmit print data to cloud print services. General-purpose printer drivers can communicate with printers of multiple printer vendors. Therefore, by using a general-purpose printer driver, a user can transmit print data to an image forming apparatus or a cloud print service without installing a vendor-specific printer driver.

[0003] In recent years, unlike cloud print services aimed at providing a function of transmitting print jobs to printers, cloud print services aimed at providing a print management function have also been proposed. The print management function is used, for example, to collect job logs generated by a printing apparatus and use the collection results for analyzing a user's printing tendency, collecting fees required for printing, and the like. In a printing system using a general-purpose printer, there is a problem that it is not possible to detect in a timely manner even if there is a loss of important printed matter (partial loss of a print result), a possibility of double printing, or deletion of a print job before printing. Therefore, Patent Document 1 discloses a technique for notifying that a printing abnormality has occurred when print end information generated by a printing apparatus does not change even after a predetermined time has elapsed by updating print-in-progress information generated by an information processing apparatus and stored in a storage device with the print end information.

[0004] In a cloud printing service that transmits print data to a cloud printing service, the printing device is identified immediately before printing is performed, and the print data is transmitted to the printing device. That is, the print management function of the cloud printing service can transmit print data to a printing device that is not a target for collecting job logs. In recent years, due to the spread of remote work, the number of cases where printing is performed using a printing device that cannot be managed by a print management service installed in a company has been increasing.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, in cloud printing services and other print management services, if printing by a printing device that is not a target for collecting job logs increases, the analysis of printing trends by the print management function and the collection of fees required for printing will become inaccurate. In the printing system disclosed in Patent Document 1, when the print management service executes printing by a printing device that is not a target for collecting job logs, it notifies that it is abnormal printing. However, since the printing is successful, it can be said that the notification of abnormal printing is inaccurate. Furthermore, the analysis of printing trends and the collection of fees required for printing become inaccurate.

[0007] An object of the present invention is to provide an information processing apparatus, an information processing system, a control method, and a program that can monitor job logs in cloud printing and accurately store job histories.

Means for Solving the Problems

[0008] In order to achieve the above object, one aspect of the information processing apparatus of the present invention is an information processing apparatus that manages, via a network, a job log of a printing device that executes printing when a print job is input via the network from a client terminal on which an extended monitoring application is installed, the information processing apparatus including: a storage unit that stores job history information having a plurality of job logs in units of jobs including a job identifier capable of identifying a job; a first receiving unit that receives a job log transmitted by the printing device; a second receiving unit that receives a job list in units of jobs including a job identifier transmitted by the extended monitoring application; an adding unit that adds the job log received by the first receiving unit to the job history information; and an updating unit that updates the job history information based on the job list received by the second receiving unit and the job history information.

Advantages of the Invention

[0009] According to the present invention, there is an effect that an information processing apparatus, an information processing system, a control method, and a program capable of monitoring a job log in cloud printing and accurately storing a job history can be provided.

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 13

Embodiments for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. However, the configurations described in the following embodiments are merely examples, and the scope of the present invention is not limited by the configurations described in the embodiments.

[0012] <First Embodiment> FIG. 1 is a configuration diagram of a print system 1 capable of cloud printing according to the first embodiment. The print system 1 according to the present embodiment includes a client terminal 101, a cloud print server 102, an application management server 103, a cloud print-compatible printer 104, an online support server 105, and a print management server 106. These are communicably connected via a network 107 to communicate required information. In FIG. 1, one client terminal 101 and one cloud print-compatible printer 104 are shown respectively, but there may be a plurality of client terminals 101 and cloud print-compatible printers 104. Further, each of the cloud print server 102, the application management server 103, and the online support server 105 may be a server system configured by a plurality of information processing devices.

[0013] By configuring each server as a server system composed of a plurality of information processing devices, load distribution can be performed by the plurality of information processing devices. Also, the cloud print server 102, the application management server 103, and the online support server 105 may be virtually configured inside a single physical information processing device. Further, although the network 107 assumes a WAN such as the Internet, all of them may be in a closed communication environment such as an in-house LAN.

[0014] (Client terminal 101) The client terminal 101 is realized by an information processing device such as a PC, a tablet, or a smartphone and is a terminal that can be directly operated by the user. The client terminal 101 can execute arbitrary application software (app). The client terminal 101 has installed therein a cloud printer driver 311, an extended monitoring app 312, an OS (operating system) 313, a local printer driver 314, a print app 315, and a print spooler 316. When a print instruction using the print app 315 is given by the user, the client terminal 101 generates print data using the cloud printer driver 311 or the local printer driver 314 and passes it to the print spooler 316. The print spooler 316 queues the passed print data as a print job in the print queue and sends the print job to the cloud print server 102 or the designated cloud print-compatible printer 104.

[0015] (Cloud print-compatible printer 104) The cloud print-compatible printer 104 is a printing device that actually performs printing on a recording medium such as paper, and converts the print data received via the network 107 into image data for printing. The cloud print-compatible printer 104 stores the print result for each print data and stores it in the storage unit 244 described later as a "job log". The cloud print-compatible printer 104 receives the print data generated by the cloud printer driver 311 via the cloud print server 102. In addition, the cloud print-compatible printer 104 also receives the print data generated by the local printer driver 314 of the client terminal 101 without going through the cloud print server 102.

[0016] (Cloud Print Server 102) The cloud print server 102 is a server equipped with a cloud print service unit 321. The cloud print service unit 321 receives an external print instruction and print data. The cloud print service unit 321 transmits the received print data to the cloud print-compatible printer 104.

[0017] (Application Management Server 103) The application management server 103 is a server equipped with an application management service unit 331. The application management service unit 331 stores and manages various applications. The application management server 103 receives the identification information and download request of the application from the client terminal 101, and transmits the application specified based on the received identification information to the client terminal 101.

[0018] (Online Support Server 105) The online support server 105 is a server equipped with an online support service unit 351 that provides an online support service. The online support service unit 351 provides the client terminal 101 with an "extended setup information file" in which information for expanding the functions of the client terminal 101 is described.

[0019] (Print Management Server 106) The print management server 106 is a server having a print management service unit 361 that provides a print management service. The print management service unit 361 acquires a job log from a cloud print-compatible printer 104 which is a preset management target and stores it in a memory.

[0020] (Fig. 2(a): Hardware Configuration of Client Terminal 101) Next, with reference to FIG. 2, the hardware configuration of each device constituting the printing system 1 will be described. FIG. 2(a) is a hardware configuration diagram of the client terminal 101. The client terminal 101 has a display unit 216, an operation unit 217, a storage unit 214, a control unit 211, and a network communication unit 215, and the control unit 211 includes a CPU 212 and a memory 213.

[0021] The display unit 216 is a display device for displaying visual information to the user, and is realized by a liquid crystal display or the like. The operation unit 217 is an input device for receiving an input from the user, and is realized by a keyboard, a mouse, or the like. Also, a touch panel or the like having the functions of both the display unit 216 and the operation unit 217 may be used. The storage unit 214 is a storage device that stores digital data in a non-volatile manner and allows its rewriting, and is realized by a hard disk drive, an SSD, or the like.

[0022] The control unit 211 includes a CPU 212 and a memory 213, and controls the overall operation of the client terminal 101. The CPU 212 expands and executes a program stored in the storage unit 214 in the memory 213. The memory 213 is the main memory of the CPU 212, and a work area and a temporary storage area for expanding various programs are formed. The network communication unit 215 communicates with an external network 107, and performs transmission and reception of required digital data between an external server, a printer, and the client terminal 101 via the network 107.

[0023] (Fig. 2(b): Hardware Configuration of Cloud Print Server 102) Fig. 2(b) is a hardware configuration diagram of cloud print server 102. Cloud print server 102 includes a storage unit 224, a control unit 221, and a network communication unit 225. The control unit 221 includes a CPU 222 and a memory 223. Since the storage unit 224, the control unit 221, and the network communication unit 225 are equivalent to those of the client terminal 101, the description thereof is omitted. Note that cloud print server 102 is described as being configured by one information processing apparatus having the hardware configuration shown in Fig. 2(b), but cloud print server 102 may be configured by a plurality of information processing apparatuses having the configuration shown in Fig. 2(b).

[0024] (Fig. 2(c): Hardware Configuration of Application Management Server 103) Fig. 2(c) is a hardware configuration diagram of application management server 103. Application management server 103 includes a display unit 236, an operation unit 237, a storage unit 234, a control unit 231, and a network communication unit 235. The control unit 231 includes a CPU 232 and a memory 233. Since the display unit 236, the operation unit 237, the storage unit 234, the control unit 231, and the network communication unit 235 are equivalent to those of the client terminal 101, the description thereof is omitted. Note that application management server 103 is described as being configured by one information processing apparatus having the hardware configuration shown in Fig. 2(c), but application management server 103 may be configured by a plurality of information processing apparatuses having the configuration shown in Fig. 2(c).

[0025] (Fig. 2(d): Hardware Configuration of Cloud Print-Compatible Printer 104) Fig. 2(d) is a hardware configuration diagram of cloud print-compatible printer 104. Cloud print-compatible printer 104 includes a display unit 246, an operation unit 247, a storage unit 244, a control unit 241, a network communication unit 245, and a printing unit 248. The control unit 241 includes a CPU 242 and a memory 243.

[0026] The display unit 246 is a touch panel, LED, etc. installed in the cloud print-compatible printer 104, and visually displays information to the user. The operation unit 247 is for receiving inputs from the user, and may include hard keys such as a numeric keypad in addition to the touch panel. Since the storage unit 244 and the control unit 241 are equivalent to those of the client terminal 101, the description thereof is omitted. The network communication unit 245 is for communicating required information with an external network 107, mainly receiving print data and transmitting the status of the cloud print-compatible printer 104 such as an error to an external server.

[0027] The printing unit 248 executes printing processing by performing a series of operations of paper feeding, printing, and paper discharging on the paper (printing medium) prepared in a cassette, tray, etc. The printing method is not limited to an electrophotographic method, an inkjet method, etc. Finishing devices such as a duplex unit, stapler, and punching process used at the time of paper discharging are also included in the printing unit 248. In the present embodiment, as an example of the cloud print-compatible printer 104, a "single function printer" that performs only a printing function will be described. However, a "multi-function printer (MFP)" having a scanner function, a FAX function, etc. may also be used.

[0028] (Fig. 2(e): Hardware configuration of the online support server 105) Fig. 2(e) is a hardware configuration diagram of the online support server 105. In the present embodiment, the online support server 105 is described as being configured by one information processing device, but it may be configured by a plurality of information processing devices. The online support server has a display unit 256, an operation unit 257, a storage unit 254, a control unit 251, and a network communication unit 255, and the control unit 251 includes a CPU 252 and a memory 253. Since the display unit 256 and the operation unit 257 are the same as the display unit 216 and the operation unit 217 of the client terminal 101, the description thereof is omitted.

[0029] The storage unit 254 is a memory device that stores information non-volatilely, such as an HDD or an SSD. The storage unit 254 stores an "extended setup information file", which is a file containing information for expanding the functions provided by the client terminal 101. The CPU 252 controls the online support server 105. The memory 253 is used for the processes executed by the CPU 252. The network communication unit 255 enables the online support server 105 to communicate required information with the client terminal 101. The online support server 105 receives a request to acquire a file stored in the storage unit 254 via the network communication unit 255 and transmits the corresponding file to the client terminal 101. This file includes the "extended setup information file".

[0030] (Fig. 2(f): Hardware configuration of the print management server 106 (information processing device)) Fig. 2(f) is a hardware configuration diagram of the print management server 106. In the present embodiment, the print management server 106 is described as being composed of one information processing device, but it may be composed of multiple information processing devices. The print management server 106 includes a display unit 266, an operation unit 267, a storage unit 264, a control unit 261, a network communication unit 265, and a printing unit 268, and the control unit 261 includes a CPU 262 and a memory 263. Since the display unit 266 and the operation unit 267 are the same as the display unit 216 and the operation unit 217 of the client terminal 101, the description thereof is omitted. The storage unit 264 is a memory device that stores information non-volatilely, such as an HDD or an SSD.

[0031] The CPU 262 controls the print management server 106. The memory 263 is used when the CPU 262 executes various processes. The network communication unit 255 communicates required information with the client terminal 101 and the cloud print-compatible printer 104. The print management server 106 acquires a job log from the cloud print-compatible printer 104 via the network communication unit 265. The storage unit 264 stores the information of the cloud print-compatible printer 104 that the print management service 363 manages and the aggregation result obtained by aggregating the job logs collected from the cloud print-compatible printer 104 for each user or each job type. The printing unit 268 prints the aggregation result of the job log and the like.

[0032] (FIG. 3: Explanatory diagram of a sequence showing a process including installation of an extended monitoring application) Next, with reference to FIG. 3, the user procedure of the present embodiment and the sequence of processes among each software and the print service will be described. First, the cloud print-compatible printer 104 receives a printer registration operation from the user to register the cloud print-compatible printer 104 with the cloud print service unit 321. In S3001, the cloud print-compatible printer 104 transmits the "device identification information" of the cloud print-compatible printer 104 and a printer registration request to the cloud print service unit 321. Here, the "device identification information" transmitted to the cloud print service unit 321 is, for example, the "HWID (Hardware ID)" assigned for each printer model. Note that the device identification information may be any information as long as it can identify the printer model.

[0033] The cloud print service unit 321 transmits the URL of the cloud print service unit 321 for printer registration to the cloud print-compatible printer 104 in response to receiving a registration request. When the user accesses the URL from the cloud print-compatible printer 104 or an information processing device (such as the client terminal 101), an input screen for entering the user ID and password is displayed on the display unit of the terminal that accessed the URL. The user enters the user ID and password for using the cloud print service unit 321 and logs in to the cloud print service unit 321. When the user's login is successful, the cloud print service unit 321 sends a request to obtain information necessary for printer registration to the cloud print-compatible printer 104. The cloud print-compatible printer 104 transmits printer information to the cloud print service unit 321 in response to the acquisition request.

[0034] Next, the cloud print service unit 321 that has received the printer registration request registers the information of the cloud print-compatible printer 104 and generates a print queue for the cloud print-compatible printer 104. At this time, the cloud print service unit 321 acquires the "capability information" of the cloud print-compatible printer 104 and associates it with the generated print queue. The "capability information" is information indicating various functions installed in the printer, such as duplex capable information, color capable information, staple capable information, etc., which are information set by the user at the time of printing.

[0035] (Installation of the extended monitoring app 312) Next, the installation of the "extended monitoring app 312" that is executed when the user performs a setup operation for printing with the cloud print-compatible printer 104 on the client terminal 101 will be described. When registering the cloud print-compatible printer 104 on the client terminal 101, the standard printing function, which is one of the functions of the OS (operating system) 313 of the client terminal 101, is utilized. In S3002, the OS 313 accepts an additional operation of the printer, which is a setup operation of the cloud print-compatible printer 104 by the user. The setup operation of the cloud print-compatible printer 104 is, for example, an operation as follows.

[0036] (Fig. 4: Explanatory diagram of the screen related to the printer displayed on the client terminal) Fig. 4 is a screen related to the printers registered on the client terminal 101 displayed by the OS 313. When the user selects and operates the object 401, the OS 313 is given an instruction to search for printers. The OS 313 that has been given the printer search instruction determines whether it stores a token for the cloud print service unit 321. If the OS 313 does not store the token, the OS 313 displays a screen (not shown) for inputting user information (login name, password). Next, in S3003, the OS 313 transmits the user information input via the screen to the cloud print service unit 321 to request user authentication and an access token.

[0037] In S3004, the cloud print service unit 321 executes an authentication process using the user information received from the client terminal 101. When the cloud print service unit 321 completes the authentication process, it notifies the client terminal 101 of the result of the authentication process. In S3005, if user authentication is successful (authentication succeeded), the OS 313 acquires an access token from the cloud print service unit 321.

[0038] If user authentication fails (authentication failure) in S3004, in S3006, the cloud print service unit 321 notifies the OS 313 of the client terminal 101 of the authentication error. Then, in S3007, the OS 313 aborts the process based on the received authentication error information. If the access token cannot be obtained, the OS 313 ends the process described in FIG. 3.

[0039] If the OS 313 stores the access token or obtains the token in S3005, the OS 313 proceeds to S3008. The OS 313 searches for printers registered in the cloud print service unit 321 and printers connected to the network 107. In S3008, the OS 313 sends a request to obtain printer information registered in the cloud print service unit 321 to perform printer search. In S3008, the OS 313 sends a request to obtain printer information with the access token attached to the cloud print service unit 321.

[0040] Next, in S3009, the cloud print service unit 321 sends the "printer information" that the user identified by the access token attached to the acquisition request is permitted to use to the client terminal 101. The "printer information" sent to the client terminal 101 is the "printer name" assigned to the printer registered in the cloud print service unit 321 and the "HWID" of the printer. The OS 313 obtains the list of printers sent by the cloud print service unit 321 and the "device identification information" of each printer. Note that in parallel with the processes of S3008 and S3009, the OS 313 searches for printers connected to the same network as the client terminal 101. This is the search for devices by mDNS, Bonjour, etc.

[0041] OS313 displays a list of printers on the client terminal 101 based on the printer information obtained from the cloud print service unit 321 and the printer information detected by searching on the network 107. In the area 402 of FIG. 4, the printer information received from the cloud print service unit 321 is listed. Among the information displayed in the area 402, "Cloud Printer 001 / 002 / 003" is the information of the printers registered in the cloud print service unit 321. On the other hand, "Printer XX" is the printer detected by the client terminal 101 searching the network 107. In this way, the printer information obtained from the cloud print service unit 321 and the printer information detected by the client terminal 101 searching the network 107 are displayed in a list. The printer information received from the cloud print service unit 321 is displayed with an icon 403 added. The symbol below the icon 403 represents "cloud", and the user can visually recognize that the printer with the icon 403 added is available on the cloud service.

[0042] On the other hand, the printer information detected by the client terminal 101 searching the network 107 is displayed with an icon 404 added. The icon 403 and the icon 404 are different symbols at first glance. In this way, the printer information received from the cloud print service unit 321 and the printer information detected by searching the network 107 are displayed in a way that allows the user to easily distinguish them. Note that the client terminal 101 may display only the information of the printers registered in the cloud print service unit 321.

[0043] Next, the user performs a selection operation on the printer information corresponding to the printer that the user wishes to register with the client terminal 101 from among the printer information displayed in the area 402. In S3010, the OS 313 inquires of the cloud print service unit 321 about the "capability information" of the printer corresponding to the selected printer information. What setting items the OS 313 inquires about for the capability information is predetermined according to the specification of the OS 313 and is set in the OS 313. The OS 313 makes an inquiry about the "capability information" by designating the preset setting items. The items preset in the OS 313 are the setting items defined as standard specifications by IPP, and are items such as "paper size", "paper type", "color mode", etc.

[0044] In S3011, the cloud print service unit 321 returns the "capability information" of the cloud print-compatible printer 104 to the OS 313. In this embodiment, it will be described that the information registered in the cloud print service unit 321 during the registration process of S3001 is transmitted to the client terminal 101 in S3011. However, the capability information registered in the cloud print service unit 321 may be transmitted to the client terminal 101 at a timing other than the above. For example, the capability information registered in the cloud print service unit 321 may be transmitted to the client terminal 101 in accordance with a change in the capability information of the cloud print-compatible printer 104. Also, the user may instruct an update of the capability information on the user interface (UI) provided by the cloud print service unit 321, and the updated capability information may be transmitted to the client terminal 101 in response to the instruction. Also, at the timing of the capability information request in S3010, the cloud print service unit 321 can acquire the capability information from the cloud print-compatible printer 104 and notify the acquired capability information to the client terminal 101.

[0045] In S3011, the cloud print service unit 321 answers, for the setting items specified from the client terminal 101, the ability information composed of the "attribute value" and the "default value" corresponding to the setting items. Here, the "attribute value" to be answered is all the attribute values registered in the cloud print service unit 321 regardless of whether it is a standard definition. The "default value" is the value (initial value) initially set when the client terminal 101 displays the print setting screen. Note that if the cloud print service unit 321 does not store the response to the attribute value queried by the OS 313, it does not respond to the OS 313.

[0046] Next, the OS 313 starts installing the cloud printer driver 311 based on the device identification information and printer name of the printer selected by the user. Then, in S3012, the OS 313 generates a print queue of the cloud printer driver 311 having the basic device ability information included in the OS 313. The "device ability information" is definition information necessary for generating the print setting ability information of the printer driver, for example, described in XML such as "PrintDeviceCapabilities". Through the above, the installation of the cloud printer driver 311 is completed. By executing the processing up to this point, it becomes possible to transmit print data to the print queue for the cloud print-compatible printer 104 generated from the client terminal 101 to the cloud print service unit 321.

[0047] (Installation process of the extended monitoring app 312) Next, the OS 313 starts the installation process of the extended monitoring application 312 associated with the printer. First, the OS 313 executes an assignment process of assigning "identification additional information" to the device identification information. This assignment process is a process necessary for obtaining the extended setup information file 700 from the online support server 105, and the "identification additional information" may be any string different from the normal device identification information. In this embodiment, in order to distinguish from applications of other devices, the OS 313 assigns identification additional information ""PrinterApp_"", which indicates that it is an application corresponding to the printer, to the device identification information. Note that ""PrinterApp_"" is an example of the identification additional information, and other strings, numbers, symbols, etc. may also be used. As a result of executing the above assignment process, for example, if the device identification information of the cloud print-compatible printer 104 is ""device001"", the device identification information after the identification additional information assignment process becomes ""PrinterApp_device001"".

[0048] Next, in S3013, the OS 313 sends a search request for the extended setup information file 700 including the target device identification information with additional information to the online support service unit 351. That is, ""PrinterApp_device001"" with the identification additional information assigned is sent to the online support service unit 351.

[0049] (Fig. 7: Extended Setup Information File) The online support service unit 351 stores the extended setup information file 700 shown in Fig. 7. What is shown in Fig. 7 is an example of the extended setup information file 700. The extended setup information file 700 is a file created by the vendor of the cloud print-compatible printer 104 and registered in the online support service unit 351. Information for specifying an application to be associated with the print queue is described in the extended setup information file 700. In the example shown in Fig. 7, the name for specifying the extended monitoring application 312 is described in 701 ""PackageFamilyName"".

[0050] The AUMID 702 in FIG. 7 describes an ID that identifies the extended monitoring application 312. On the other hand, the "PrinterHardwareID 703" describes a character string obtained by adding identification additional information to the identification information of the cloud print-compatible printer 104. The "ServerURL 704" describes the access destination to the print management service unit 361 operating in the print management server 106. The online support service unit 351 stores an extended setup information file in which the identification information of the printer driver is described, in addition to the extended setup information file in which the identification information of the application is described. In the extended setup information file 700 in which the identifier of the printer driver is described, the identifier of the printer driver is described in the "PackageFamilyName 701". Further, the "PrinterHardwareID 703" in the extended setup information file 700 describes device identification information without the description of the identification additional information.

[0051] As described above, the online support service unit 351 stores both the extended setup information file in which the identifier of the printer driver is described and the extended setup information file in which the identifier of the extended monitoring application is described. For this reason, the OS 313 executes a process of adding the identification additional information to the device identification information in order to appropriately obtain the necessary extended setup information file. The online support service unit 351 that has received the search request identifies the extended setup information file in which the device identification information with the identification additional information specified in the request matches the "PackageFamilyName" in the file. In S3014, as a result of the search, when the online support service unit 351 stores the extended setup information file 700 including the target device identification information, the extended setup information file 700 is returned to the OS 313. At this time, the content of the extended setup information file 700 is written into the registry of the OS 313.

[0052] Next, in S3015, the OS 313 associates and installs the extension setup information described in the extension setup information file 700 obtained from the online support service unit 351 with the print queue generated in S3012. Next, in S3016, the OS 313 extracts the "application ID" from the installed extension setup information. The "application ID" is an identifier defined by "PackageFamilyName" in the extension setup information file. In the example shown in FIG. 7, it is "PrinterApp_abcd12345678a" (see 702) indicating the extension monitoring application 312. The above is the process when the online support service unit 351 stores the extension setup file corresponding to the cloud print-compatible printer 104.

[0053] On the other hand, as a result of the search, there may be a case where the online support service unit 351 cannot detect the extension setup information file 700 containing the target device identification information. In this case, in S3017, the OS 313 completes the installation of the cloud printer driver 311 and aborts the installation process of the application (extension monitoring application 312). The OS 313 executes the installation abort process in S3017 when it cannot receive the extension setup file within a predetermined time from the search request in S3013 or when it receives an error notification from the online support service unit 351.

[0054] From S3018 onwards, the process when the extended setup file can be obtained and the application ID can be extracted in S3016 will be described. In S3018, the OS 313 requests the application management service unit 331 to search for an application whose extracted application ID matches. The application management service unit 331 stores, in association with each other, an application operating on the client terminal 101 and an application ID which is an identifier of the application. The application and the application ID are registered in the application management service unit 331 by a vendor providing the cloud print-compatible printer 104.

[0055] In S3019, when the application management service unit 331 stores an application that matches the requested application ID, it returns the application to the client terminal 101. In the extended setup information file 700 shown in FIG. 7, the extended monitoring application 312 is returned. In S3020, the OS 313 installs the obtained extended monitoring application 312 in association with the print queue on the client terminal 101 side. The OS 313 stores the application ID in the registry as information on the print queue. Further, the extended monitoring application 312 sets the OS 313 so that the extended monitoring application 312 is started when the OS is started, with respect to the OS 313. The installed extended monitoring application 312 is started after the power of the client terminal 101 is turned on and the OS 313 is started, and operates as a background task after startup.

[0056] On the other hand, in S3021, when the application management service unit 331 does not store an extended monitoring application that matches the requested application ID, the OS 313 aborts the installation process of the application (extended monitoring application 312). In this case, the generated print queue and the cloud printer driver 311 are installed in association with each other, and the extended monitoring application 312 ends the process without being associated with the print queue.

[0057] In the above description, a predetermined string was added to the device identification information of the cloud print-compatible printer 104 to search for the extended setup file. If it is possible to distinguish the files for installing the printer driver, the search may be performed without adding the predetermined string. Also, although an example in which the extended monitoring app 312 is associated with the print queue was described, it may be associated with the client terminal 101, that is, only one app may be installed on the client terminal 101.

[0058] (FIG. 8: Explanatory diagram of a sequence showing job history complementation by the print management service unit 361 from a print execution instruction by the client terminal 101) Next, with reference to FIG. 8, a sequence of job history complementation by the print management service unit 361 from a print execution instruction by the client terminal 101 in the first embodiment will be described. Note that the "job log" refers to what is obtained by storing the print result generated by the cloud print-compatible printer 104 in its storage unit 244. Also, the "job history" is what is obtained by storing the "job log" collected by the print management server 106 from each printer in the storage unit 264. The cloud printer driver 311, the extended monitoring app 312, and the print spooler 316 of the client terminal 101 become able to communicate the required information with each other by a predetermined method when started. The extended monitoring app 312 accesses the connection destination indicated by the ServerURL 704 of the extended setup information file 700 at the time of first startup, performs authentication from an authentication screen (not shown), and sets the authentication information as registered. Also, it is assumed that sufficient time has elapsed from when the print instruction is given until the processes of printing, job log generation, and job log acquisition are executed.

[0059] (Contents of the process in FIG. 8) First, in S801, the cloud printer driver 311 notifies the extended monitoring app 312 of the start of a job. For example, it notifies the "job information" using a pre-determined method. The "job information" is, for example, the job ID, job name, owner name (user name), paper size, paper type, number of printed sheets, etc. The "Job ID (JobId)" is an identifier of the print job set for each job issuing device. In this embodiment, it is set as a serial number starting from "1". For example, it is set as "Computer name: AAA0000001". The "computer name" is uniquely determined on the network, and "AAA0000001" is uniquely determined on the same computer. The "job ID" is stored as information for identifying the job in the print log generated by the printer. By verifying the numerical value of the serial number, it is possible to detect missing jobs, duplicate jobs, etc. Also, the file name (document name) of the file to be printed as the name of the print job, the user ID of the user who gives the print instruction, the date and time information when the print instruction is given, etc. may be used.

[0060] Next, in S802, the extended monitoring app 312 starts the monitoring process of the print spooler 316. Here, the "monitoring process" is the job detailed information acquisition process of S809 to S811 described later. Next, in S803, the cloud printer driver 311 registers the job. For example, it uses the public function (API) of the print spooler 316 to send the print data to the cloud print-compatible printer 104 specified later. Next, in S804, the print spooler 316 changes the status of the job to "Spooling". The content of the status is appropriately changed according to the change in the status of the job. "Spooling" indicates the state before the print spooler 316 stores the job and then sends it.

[0061] Next, in S805, the print spooler 316 sends the job to the cloud print-compatible printer 104. Next, in S806, the print spooler 316 changes the status of the job to "Sending". "Sending" indicates the state from the start of the job transmission to the completion of the job transmission.

[0062] When the job transmission is completed, in S807, the print spooler 316 detects the reception completion of the cloud print-compatible printer 104. For example, when all the print data has been transmitted, it is determined that the reception is complete. Next, in S808, the print spooler 316 changes the status of the job to "Sent". "Sent" indicates the state where the job transmission is completed.

[0063] (Job monitoring process of the extended monitoring app 312) Next, the job monitoring process of the extended monitoring app 312 will be described. In S809, the extended monitoring app 312 requests the print spooler 316 to obtain the status. For example, it uses the public function of the print spooler 316 to request to obtain the job list and further requests to obtain the detailed information of the job. Next, in S810, the print spooler 316 responds to the status acquisition request. That is, it appropriately responds to the call of the public function in S809. Next, in S811, the extended monitoring app 312 updates the job list. That is, if there is an addition to the job information previously stored in the storage unit 214, it is added to the list, and if the status of an existing job is updated, the status of the corresponding job in the list is updated. Then, the extended monitoring app 312 repeats the processes of S809 to S811. The series of job detailed information acquisition processes starting from S809 starts with the start of monitoring of the print spooler 316 in S802 and is executed asynchronously with the processes of the print spooler 316 after S803. Note that the job list in this embodiment is generated in units of print jobs.

[0064] Then, in S812, the extended monitoring app 312 transmits the updated job list to the print management service unit 361. The transmission of the job list may be executed periodically using a timer provided in the extended monitoring app 312, or may be executed at the timing when the job is updated. Also, the job list may be transmitted according to the instruction of the print management service unit 361.

[0065] Take the job list example as "ID=Comp99-AAA0000001,owner=User99,department=2399, document="Readme.doc", Page=5, Size=A5, Type=normal, name=“plain paper”,device=DeviceZ, finishing=none, status=sent". In S801, the cloud printer driver 311 notifies the extended monitoring app 312 of the start of a job. At the same time, job information (job ID, job name, owner name, etc.) is notified. Also, in S809, the extended monitoring app 312 grasps the information (Status) obtained from the print spooler 316. "ID" is an ID that uniquely determines a job. "Owner" is the job executor. "Department" is a 4-digit numerical value indicating the user group to which the job executor belongs. "Document" is the document name. "Page" is the number of printed pages. "Size" is the paper size. "Type" is the paper type. "Name" is the display name of the paper type. "Device" is the destination device information. "Finishing" is the processing method for the printed matter, such as a function to fold the printed matter in half or a function to perform binding processing. "Status" is the status of the job.

[0066] Next, in S813, the cloud print-compatible printer 104 executes printing. Next, in S814, the CPU 243 of the cloud print-compatible printer 104 generates a print log (job log) including the job information of the executed printing job and stores it in the storage unit 244. The "job log" is generated for each job and has information such as a log ID uniquely determined by the log, a job ID generated by the cloud printer driver 311, the number of printed sheets, the print paper size, the print paper type, and finishing. Next, in S815, the cloud print-compatible printer 104 transmits the job log to the print management service unit 361. For example, when a predetermined time arrives, the cloud print-compatible printer 104 transmits the job log stored in the storage unit 244 to the print management service unit 361. Next, in S816, the print management service unit 361 adds a job history. That is, the CPU 262 of the print management server 106 adds the job log acquired in S815 to the job history stored in the storage unit 264.

[0067] (FIG. 6(a): Explanation diagram of job history display: FIG. 13(a): Explanation diagram of job history) FIG. 13(a) shows an example of a job history consisting of five job logs. Each job log is associated with information such as a job ID (JobID), user name, department ID, device name, document name, end time, and number of pages. FIG. 6(a) is an explanation diagram of job history display. The job history display is a display by the CPU 262 of the print management server 106 of the job history stored in the storage unit 264 on the display unit 266. It may also be displayed on the display unit 216 of the client terminal 101 via the network 107. In the job history display of FIG. 6(a), the jobs are arranged and displayed from top to bottom in the order of the print completion time (the earliest end time).

[0068] Returning to FIG. 8, in S817, the Print Management Service Unit 361 corrects the job history. Although an example in which the job history correction process in S817 is executed after obtaining the job log has been described, it may be performed after obtaining the job list (i.e., immediately after S812), or may be executed periodically using a timer.

[0069] (FIG. 9: Flowchart showing job history correction processing) Next, with reference to FIG. 9, the "job history correction process" in S817 will be described. For ease of explanation, it is assumed that one job list has been received. The authentication information used by the Print Management Service Unit 361 for inter-device communication, timer settings, and various other settings required for operations are appropriately set in advance.

[0070] First, in S901, the Print Management Service Unit 361 determines whether it has received a "job list" from the Extended Monitoring Application 312. If the Print Management Service Unit 361 determines that it has received a "job list" from the Extended Monitoring Application 312 via the network 107 (Yes), the process proceeds to S902. On the other hand, if the Print Management Service Unit 361 determines that it has not received a job list from the Extended Monitoring Application 312 via the network 107 (No), the process proceeds to S903. In S902, the Print Management Service Unit 361 executes a job history update process described later. On the other hand, in S903, the Print Management Service Unit 361 determines whether the job log acquisition time has reached a preset time. For example, a timer can be used to make the preset time arrive periodically.

[0071] When the Print Management Service Unit 361 determines that the job log acquisition time has reached the preset time (Yes), the process proceeds to S904. On the other hand, when it determines that the job log acquisition time has not reached the preset time (No), the process proceeds to S905. In S904, the Print Management Service Unit 361 executes a job log acquisition process to acquire the job log. On the other hand, in S905, the Print Management Service Unit 361 determines whether the aggregation time has arrived. When the Print Management Service Unit 361 determines that the aggregation time has arrived (Yes), the process proceeds to S906. On the other hand, when it determines that the aggregation time has not arrived (No), the process returns to S901. In S906, the Print Management Service Unit 361 executes an aggregation process. For example, the Print Management Service Unit 361 extracts the job history stored in the storage unit 264 and executes an aggregation process for each user, each department, each printer, etc.

[0072] (Fig. 5: Explanation diagram of the aggregation screen) Fig. 5 is an explanatory diagram of an aggregation screen that displays the aggregation result. In Fig. 5, the aggregation period is associated with and displayed along with "Print", "Copy", "Box", and "Receive". That is, for each aggregation period, the number of each of "Print", "Copy", "Box", and "Receive" is aggregated, and the aggregation result is displayed. For example, in the aggregation period of "January 15, 2021 to February 14, 2021", each of "Print", "Copy", "Box", and "Receive" has "539 pieces", "625 pieces", "10 pieces", and "110 pieces", respectively, indicating that a total of "1284 pieces" of jobs have been executed. At the lower side of the aggregation screen, the aggregation period and its total are displayed in a bar graph format, making it easy for the user to visually recognize and understand.

[0073] The aggregation result may be output in a file format, or the CPU 262 may display the aggregation result stored in the storage unit 264 on the display unit 266 and further display it on the display unit 216 of the client terminal 101 via the network 107. In the example shown in Fig. 5, the aggregation result for each aggregation period is displayed in a table and a graph. The user can refer to the aggregation result to grasp the printing frequency, etc., and use it for allocating printing costs, etc.

[0074] (FIG. 10: Flowchart showing job history update processing according to the first embodiment) Next, the job history update processing in S902 will be described with reference to FIG. 10. Assume that the printers to be monitored by the print management service unit 361 are "DeviceA" and "DeviceB", and the print management service unit 361 can check the status of the devices to be monitored. First, in S1001, the print management service unit 361 determines whether there is a transmitted job. That is, the print management service unit 361 determines that there is a transmitted job if there is a job in the transmitted job list already transmitted from the extended monitoring application 312 with the "Status: status" being "Sent". If it is determined in S1001 that there is a transmitted job (Yes), the process proceeds to S1002. On the other hand, if it is determined that there is no transmitted job (No), the job history update processing ends.

[0075] Next, in S1002, the print management service unit 361 determines whether the same job ID exists in the job history. That is, the CPU 262 of the print management server 106 searches the job history stored in the storage unit 264 and searches for a record having the same "JobID" as the transmitted job determined to exist in S1001. If, as a result of the search, there is a record having the same "JobID", it is determined that the same job ID exists in the job history. If the print management service unit 361 determines that the same job ID exists in the job history (Yes), the process proceeds to S1003. On the other hand, if it is determined that the same job ID does not exist in the job history (No), the process proceeds to S1004.

[0076] In S1003, the Print Management Service Unit 361 corrects the job history. Originally, the job log generated by the printer and the job information generated from the information of the driver and the print spooler should match. When the printer rounds off the attributes of the job log, a more accurate job history is generated by correcting with the information of the job information. For example, when the printing paper specified by the driver is magnetic paper and the printer does not correspond to "magnetic paper" as the paper type in the job log, it may be rounded off to "others". In this case, it is possible to correct the job history with the paper type information in the job list as "magnetic paper". When the correction of the job history is completed in S1003, the process shown in FIG. 10 is terminated.

[0077] On the other hand, in S1004, the Print Management Service Unit 361 determines whether the destination device is a monitoring target. That is, when the content of "Device" in the job list received from the Extended Monitoring Application 312 in S809 is a device to be monitored, it is determined that it is a device to be monitored. When the Print Management Service Unit 361 determines that the destination device is a monitoring target (Yes), it proceeds to S1005. On the other hand, when it determines that the destination device is not a monitoring target (No), it proceeds to S1006. In S1005, the Print Management Service Unit 361 generates an "unknown log" and adds it to the job history.

[0078] For example, assume that the following is stored in the job list. "ID=Comp11-AAA0000001, owner=User1, department=2321, document="Request.doc", Page=3, Size=Letter, Type=normal, name="Plain Paper", device=DeviceB, finishing=none, status=sent". In this case, the content of "Device" being monitored is "DeviceB". When the job list is obtained in the state shown in Fig. 13(a), the job with "ID=Comp11-AAA0000001" shown in the job list is generated as an "unknown log" and the subsequent job history is shown in Fig. 13(c). It can be seen from Fig. 13(c) that the job with "ID=Comp11-AAA0000001" is added third from the top. The "unknown log" added to the job history has "JobID" as "Comp11-AAA0000001", the user name "User1", the department ID "2321", and the device name "DeviceB", and it is in the same history as the job list. Also, it is recorded as "unknown log" in the remarks column of Fig. 13(c). Fig. 6(c) shows an example of the display of the job history with the "unknown log" added. Since Fig. 6(c) is an unknown log, the "end time" is blank.

[0079] On the other hand, in S1006, the print management service section 361 generates an "alternative log" and adds it to the job history.

[0080] When the job list is "ID=Comp99-AAA0000001, owner=User99, department=2399, document="Readme.doc", Page=5, Size=A5, Type=normal, name="Plain Paper", device=DeviceZ, finishing=none, status=sent", the following occurs. In this case, the content of "Device" is "DeviceZ" which is not the object of monitoring.

[0081] When the job list is obtained with the job history in the state of Fig. 13(a), the job with "ID=Comp99-AAA0000001" indicated in the job list is generated as an "alternative log" and added, and the subsequent job history is shown in Fig. 13(b). The job history of the "alternative log" is added third from the top in Fig. 13(b). In the alternative log added to the job history, "JobID" is "Comp99-AAA0000001", the user name is "User99", the department ID is "2399", the device name is "DeviceZ", etc., and it is in the history as per the job list. Fig. 6(b) shows an example of the display of the job history with the "alternative log" added.

[0082] As described above, even if printing is done on a printer not monitored by the print management service unit 361, the "alternative log" generated by the extended monitoring app 312 can be added, making the aggregation result more accurate. Also, when the print management service unit 361 cannot obtain the print result of the job sent by the client terminal 101 as a job log from the monitored printer, an "unknown log" can be added, making the job history accurate.

[0083] <Second Embodiment> Next, the second embodiment of the present invention will be described. In the first embodiment, when a job log cannot be generated on the cloud print-compatible printer 104, an unknown log or the like can be generated and added to the job history. However, since it is unknown whether the printing was successful, improvement is needed to check the print result. Hereinafter, only the differences from the first embodiment will be described for ease of explanation.

[0084] (Fig. 11: Sequence showing complement of job history by print management service unit from print execution instruction by client terminal) Referring to FIG. 11, the sequence of job history completion by the print management service unit 361 from the print execution instruction by the client terminal 101 in the second embodiment will be described. S1101 to S1108, S1110 to S1112, S1113, and S1117 to S1120 are the same as S801 to 808, S809 to S811, S813, and S814 to S817 in FIG. 8, respectively.

[0085] In S1019, the extended monitoring app 312 starts monitoring the job of the cloud print-compatible printer 104. For example, the extended monitoring app 312 notifies the cloud print-compatible printer 114 at the print destination to subscribe to the event of the job status change by a preset method. Here, the "event of status change" is what the printer detects the status change and notifies externally. Also, "subscription" refers to registering with the printer as the notification destination of the event. When registering the registered event type and one's own destination (for example, IP address), the "subscription" is executed in which the printer notifies the registered destination of the event when the event occurs. It is assumed that the print spooler 316 can obtain the information (such as the IP address) of the print destination. Next, in S1114, the cloud print-compatible printer 104 notifies the extended monitoring app 312 of the job status change. That is, when the status of the print job changes, based on the preset method, the extended monitoring app 312 is notified of the job information identifying the print job and its status.

[0086] Examples of the status are shown below. "PreProcessing": Waiting for job analysis by the printer. "Processing ": Job analysis in progress by the printer. "Wait-Excuting": Waiting for printing by the printer. "Excuting": Printing in progress by the printer. "Complete ": Printing completed by the printer. "Deleated": Deleted from the printer.

[0087] In S1115, the extended monitoring app 312 updates the job list. The extended monitoring app 312 updates the job list based on the job information obtained in S1114. That is, if there is a job already stored in the storage unit 214 of the client terminal 101, it is added, and if the status has been updated, the status of the corresponding job is updated. Next, in S1116, the extended monitoring app 312 transmits the job list to the print management service unit 361. The transmission of the job list may be executed periodically by a timer provided in the extended monitoring app 312, may be transmitted at the timing when the job list is updated, or may be transmitted upon receiving an instruction from the print management service unit 361.

[0088] (Fig. 12: Flowchart showing job history update processing of the second embodiment) Next, the job history update processing will be described with reference to Fig. 12. S1201 to S1203 are the same as S1001 to S1003 in Fig. 10. In S1204, the print management service unit 361 determines whether the status of the transmitted job found from the job list in S1201 is "Complete". In S1204, if the print management service unit 361 determines that the status of the transmitted job found from the job list is "Complete" (Yes), it proceeds to S1205, while if it determines that the status is not "Complete" (No), it proceeds to S1206.

[0089] In S1205, the print management service unit 361 generates an "alternative log". The fact that there is no job log corresponding to the job history but the status of the job is "Complete" means that printing has been completed on the cloud print-compatible printer 104 but the generation of the job log has failed. For example, this corresponds to a case where the printer power was turned off immediately after printing was completed, preventing the log from being generated. On the other hand, in S1206, the print management service unit 361 generates a "failure log".

[0090] Speculate the cause of failure according to the status in the job list. An example of the status is shown below. "PreProcessing": The process has ended while waiting for job analysis by the printer. "Processing": The process has ended while the printer is analyzing the job. "Wait-Excuting": The process has ended while waiting for printing by the printer. "Excuting": The process has ended while the printer is printing. "Deleated": The job is deleted from the printer.

[0091] For example, assume that there is one piece of job information stored in the job list as follows: "ID=Comp11-AAA0000001,owner=User1,department=2321, document="Claim.doc", Page=3, Size=Letter, Type=normal, name=“Plain Paper”,device=DeviceB, finishing=none, status=excuting".

[0092] When the job history is in the state of Fig. 13(a) and the above job list is obtained, since the status is "Excuting", it is determined that the process has ended while the printer is printing, and a "failure log" is added. The job history with the job "ID=Comp11-AAA0000001" shown in the above job list generated and added as the "failure log" is shown in Fig. 13(d). The "failure log" is stored in the third row from the top in Fig. 13(d), and "failure" is associated and stored in the "result column", and "power off" is associated and stored in the "remarks column". That is, it is stored as a "failure log" due to the printer power off during printer printing. Fig. 6(d) shows an example of the display of the job history with the "failure log" added. The job list is displayed in the third row from the top, and it is displayed as "failure" in the "result column" and "job deletion" in the "cause column", indicating that it is a "failure log".

[0093] As described above, even if printing is performed on a printer that is not a monitoring target by the print management service unit 361, the extended monitoring application 312 can detect the completion of a job and can reliably reflect the print result of the "alternative log" in the job history information. As a result, it is possible to accurately execute the aggregation process regarding the job history. Further, when the print management service unit 361 cannot obtain the job log of the job transmitted by the client terminal 101 from the printer that is the monitoring target, it is possible to add an unknown log and present the cause of failure, so that the job history becomes more accurate as job tracking information.

[0094] <Supplementary Note> The disclosure of this embodiment includes the following configurations, methods, and programs. (Configuration 1) An information processing apparatus that manages, via a network, the job log of a printing device that executes printing by inputting a print job via the network from a client terminal on which an extended monitoring application is installed, a storage unit that stores job history information having a plurality of job logs in units of jobs including a job identifier capable of identifying a job; a first receiving unit that receives a job log transmitted by the printing device; a second receiving unit that receives a job list in units of jobs including a job identifier transmitted by the extended monitoring application; an adding unit that adds the job log received by the first receiving unit to the job history information; an updating unit that updates the job history information based on the job list received by the second receiving unit and the job history information, the information processing apparatus being characterized by including these components. (Configuration 2) The updating unit when the job identifier of the job list received by the second receiving unit does not exist in the job history information and the transmission source is a printing device that is a monitoring target, further includes an unknown log adding unit that adds the job log of the job list as an unknown log to the job history information, the information processing apparatus according to Configuration 1 being characterized by including this component. (Configuration 3) When the update unit When the job identifier in the job list received by the second receiving unit does not exist in the job history information and the transmission source is a printing device not subject to monitoring, the information processing apparatus according to Configuration 1, further comprising an alternative log adding unit that adds the job log of the job list as an alternative log to the job history information. (Configuration 4) When the update unit When the job identifier in the job list received by the second receiving unit exists in the job history information, the information processing apparatus according to Configuration 1, further comprising a correction unit that corrects the job log of the job list. (Configuration 5) When the correction unit When there is an item that is different between the contents of both the job log in the job history information corresponding to the job list received by the second receiving unit and the job list, the information processing apparatus according to Configuration 4, wherein the item is corrected with the item of the job list. (Configuration 6) When the unknown log adding unit further The information processing apparatus according to Configuration 2, wherein when generating an unknown log and adding it to the job history information, information indicating that it is an unknown log is associated and stored. (Configuration 7) The information processing apparatus according to any one of Configurations 1 to 5, further comprising a job log acquisition unit that acquires a job log for a printing device to be monitored when a job list is not received by the second receiving unit and a predetermined time has arrived. (Configuration 8) The information processing apparatus according to any one of Configurations 1 to 5, further comprising an aggregation processing unit that performs aggregation processing in a predetermined manner on the job history information when the job list transmitted by the extended monitoring application is not received by the second receiving unit and a predetermined time has not arrived. (Configuration 9) The information processing apparatus according to claim 8, further comprising an output unit that outputs the result of the aggregation process by the aggregation processing unit in different modes on one screen. (Configuration 10) The aggregation process in the predetermined mode is an aggregation for at least one item among a plurality of items including each user, each department, and each printer. The information processing apparatus according to Configuration 8. (Configuration 11) The information processing apparatus according to any one of Configurations 1 to 5, further comprising a third receiving unit that receives a job list updated based on the state of a print job transmitted by the extended monitoring application. (Configuration 12) When the job identifier of the job list received by the third receiving unit does not exist in the job history information and the state of the print job of the job list is print completion, a second alternative log adding unit that adds the job log of the job list to the job history information as an alternative log. The information processing apparatus according to Configuration 11. (Configuration 13) When the job identifier of the job list received by the third receiving unit does not exist in the job history information and the state of the print job of the job list is not print completion, a failed log adding unit that adds the job log of the job list to the job history information as a failed log. The information processing apparatus according to Configuration 11. (Configuration 14) The failed log adding unit further When generating a failed log and adding it to the job history information stored in the storage unit, result information indicating that it is a failed log and cause information indicating the cause are associated and stored. The information processing apparatus according to Configuration 13. (System Configuration 1) An information processing system in which a client terminal installed with an extended monitoring application, a printing device, and an information processing apparatus that manages job logs can communicate required information with each other via a network. The client terminal The extended monitoring application includes a first transmission unit that transmits, to the information processing apparatus, a job list for each print job input to the printing device. The printing device includes a second transmission unit that transmits, to the information processing apparatus, a job log of the input print job. The information processing apparatus includes a storage unit that stores job history information having a plurality of job logs for each job including a job identifier capable of identifying the job, a first reception unit that receives the job log transmitted by the printing device, a second reception unit that receives a job list for each job including a job identifier transmitted by the extended monitoring application, a job history information addition unit that adds the job log received by the first reception unit to the job history information, and a job history update unit that updates the job history information based on the job list received by the second reception unit and the job history information. An information processing system characterized by comprising these components. (System configuration 2) The client terminal includes an extraction unit that extracts an application identifier for identifying an application described in the setup file when the setup file acquired from the first server is incorporated into the own terminal, The information processing system according to configuration 15, characterized in that the extended monitoring application returned from the second server becomes installable when the application identifier extracted by the extraction unit is transmitted to the second server. (Method) A control method for an information processing apparatus that manages, via a network, a job log of a printing device that executes printing by inputting a print job via the network from a client terminal on which an extended monitoring application is installed, a storage step of storing job history information having a plurality of job logs for each job including a job identifier capable of identifying the job, a first reception step of receiving the job log transmitted by the printing device, A second receiving step of receiving a job list in units of jobs including a job identifier, which is transmitted by the extended monitoring application; An adding step of adding the job log received in the first receiving step to the job history information; An updating step of updating the job history information based on the job list received in the second receiving step and the job history information, wherein the control method of the information processing apparatus is characterized by comprising: (Program) A program for causing a computer to execute a control method of an information processing apparatus that manages, via a network, a job log of a printing device that executes printing by inputting a printing job via a network from a client terminal on which an extended monitoring application is installed, The control method includes: A storage step of storing job history information having a plurality of job logs in units of jobs including a job identifier capable of identifying a job; A first receiving step of receiving a job log transmitted by the printing device; A second receiving step of receiving a job list in units of jobs including a job identifier, which is transmitted by the extended monitoring application; An adding step of adding the job log received in the first receiving step to the job history information; An updating step of updating the job history information based on the job list received in the second receiving step and the job history information, wherein the program is characterized by comprising:

[0095] As described above, the preferred embodiments of the present invention have been described. However, the present invention is not limited to the above-described embodiments, and various modifications and changes are possible within the scope of the gist thereof. For example, the present invention can also be realized by a process in which a program that realizes one or more functions of the above-described embodiments is supplied to a system or apparatus via a network or a recording medium, and a processor of a computer of the system or apparatus reads and executes the program. Further, the present invention can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

Description of Reference Numerals

[0096] 1 Printing System 101 Client Terminal 102 Cloud Print Server 103 Application Management Server 104 Cloud Print-Compatible Printer 105 Online Support Server 106 Print Management Server 105 Online Support Server 311 Cloud Printer Driver 312 Extended Monitoring App 313 OS 314 Local Printer Driver 315 Print App 316 Print Spooler 321 Cloud Print Service Section 331 Application Management Service Section 351 Online Support Service Section 361 Print Management Service Section

Claims

1. An information processing apparatus for managing, via a network, a job log of a printing device that executes printing by inputting a printing job via the network from a client terminal on which an extended monitoring application is installed, comprising: a storage unit that stores job history information having a plurality of job logs in units of jobs including job identifiers that can identify the jobs; a first receiving unit that receives a job log transmitted by the printing device; a second receiving unit that receives a job list in units of jobs including a job identifier transmitted by the extended monitoring application; an adding unit that adds the job log received by the first receiving unit to the job history information; an updating unit that updates the job history information based on the job list received by the second receiving unit and the job history information. The information processing apparatus is characterized by comprising the above.

2. The updating unit: When the job identifier of the job list received by the second receiving unit does not exist in the job history information and the transmission source is a printing device to be monitored, the updating unit further comprises an unknown log adding unit that generates the job log of the job list as an unknown log and adds it to the job history information. The information processing apparatus according to claim 1 is characterized by this.

3. The updating unit: When the job identifier of the job list received by the second receiving unit does not exist in the job history information and the transmission source is a printing device not to be monitored, the updating unit further comprises an alternative log adding unit that generates the job log of the job list as an alternative log and adds it to the job history information. The information processing apparatus according to claim 1 is characterized by this.

4. The updating unit: When the job identifier of the job list received by the second receiving unit exists in the job history information, the updating unit further comprises a correcting unit that corrects the job log of the job list. The information processing apparatus according to claim 1 is characterized by this.

5. The correcting unit: When there are items that differ in the contents of both the job list received by the second receiving unit and the job log in the corresponding job history information, the correcting unit corrects the item with the item of the job list. The information processing apparatus according to claim 4 is characterized by this.

6. The unknown log adding unit further: The information processing apparatus according to claim 2, wherein when generating an unknown log and adding it to the job history information, information indicating that it is an unknown log is associated and stored in the storage unit.

7. The information processing apparatus according to any one of claims 1 to 5, further comprising a job log acquisition unit that acquires a job log for a printing device to be monitored when a job list is not received by the second receiving unit and a predetermined time has arrived.

8. The information processing apparatus according to any one of claims 1 to 5, further comprising a aggregation processing unit that performs aggregation processing on the job history information in a predetermined manner when a job list transmitted by the extended monitoring application is not received by the second receiving unit and a predetermined time has not arrived.

9. The information processing apparatus according to claim 8, further comprising an output unit that outputs the result of the aggregation processing by the aggregation processing unit in different manners on one screen.

10. The information processing apparatus according to claim 8, wherein the aggregation processing in the predetermined manner is aggregation for at least one item among a plurality of items including for each user, for each department, and for each printer.

11. The information processing apparatus according to any one of claims 1 to 5, further comprising a third receiving unit that receives a job list updated based on the state of a printing job transmitted by the extended monitoring application.

12. The information processing apparatus according to claim 11, further comprising a second alternative log addition unit that generates a job log of the job list as an alternative log and adds it to the job history information when the job identifier of the job list received by the third receiving unit does not exist in the job history information and the state of the printing job of the job list is printing completed.

13. The information processing apparatus according to claim 11, further comprising a failure log addition unit that generates a job log of the job list as a failure log and adds it to the job history information when the job identifier of the job list received by the third receiving unit does not exist in the job history information and the state of the printing job of the job list is not printing completed.

14. The failure log addition unit further When generating a failure log and adding it to the job history information, the information processing apparatus according to claim 13, characterized in that result information indicating that it is a failure log and cause information indicating the cause thereof are associated and stored in the storage unit.

15. An information processing system in which a client terminal installed with an extended monitoring application, a printing device, and an information processing apparatus for managing job logs can communicate required information with each other via a network, wherein the client terminal is provided with a first transmission unit that transmits a job list in units of print jobs input to the printing device to the information processing apparatus by the extended monitoring application, wherein the printing device is provided with a second transmission unit that executes the input print job and transmits the job log to the information processing apparatus, wherein the information processing apparatus includes a storage unit that stores job history information having a plurality of job logs in units of jobs including job identifiers that can identify jobs, a first reception unit that receives the job log transmitted by the printing device, a second reception unit that receives a job list in units of jobs including a job identifier transmitted by the extended monitoring application, a job history information addition unit that adds the job log received by the first reception unit to the job history information, and an update unit that updates the job history information based on the job list received by the second reception unit and the job history information.

16. wherein the client terminal is provided with an extraction unit that extracts an application identifier for identifying an application described in the setup file when the setup file acquired from the first server is incorporated into the own terminal, and the information processing system according to claim 15, characterized in that the extended monitoring application returned from the second server becomes installable by transmitting the application identifier extracted by the extraction unit to the second server.

17. A control method for an information processing apparatus that manages, via a network, a job log of a printing device that executes printing when a print job is input via a network from a client terminal installed with an extended monitoring application, including a storage step of storing job history information having a plurality of job logs in units of jobs including job identifiers that can identify jobs, a first reception step of receiving the job log transmitted by the printing device, A second receiving step of receiving a job list in job units including a job identifier, which is transmitted by the extended monitoring application; An adding step of adding the job log received in the first receiving step to the job history information; An updating step of updating the job history information based on the job list received in the second receiving step and the job history information, wherein the control method of the information processing apparatus is characterized by including these steps.

18. A program for causing a computer to execute a control method of an information processing apparatus that manages, via a network, a job log of a printing device that executes printing by inputting a printing job via a network from a client terminal on which an extended monitoring application is installed, The control method includes: A storage step of storing job history information having a plurality of job logs in job units including a job identifier capable of identifying a job; A first receiving step of receiving a job log transmitted by the printing device; A second receiving step of receiving a job list in job units including a job identifier, which is transmitted by the extended monitoring application; An adding step of adding the job log received in the first receiving step to the job history information; An updating step of updating the job history information based on the job list received in the second receiving step and the job history information, wherein the program is characterized by including these steps.

Images