System, method, and program

Abstract

To solve the problem of the conventional print system in which a user may not appropriately grasp an error in the notification of errors detected by a cloud services in a subsequent stage when a print system is constructed by linking a plurality of cloud services.SOLUTION: The present invention pertains to a second system cooperating with a first system capable of communicating with a client device, including: management means for linking user information registered in the second system to user information registered in the first system and managing them; receiving means for receiving a print job; and requesting means for requesting the first system to send an error notification for the user information registered in the first system corresponding to the user information of a user who is the owner of the print job when an error is detected in the received print job and the print job is received from the first system.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a system, method, and program for managing an image forming apparatus having a printing function and print data. [Background technology]

[0002] As diverse working styles become more common, there is a growing need for organizations to manage employee printing. As a result, the adoption of cloud printing, which allows printing via a print server operated by the organization, is on the rise in office environments.

[0003] In the prior art, when using cloud printing, if an error occurs on a printing device, the error is notified to the print server, and the print server manages the status of the printing device stored internally as "error occurring" (for example, Patent Document 1). The status of this printing device could be checked by accessing the management screen provided by the print server. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-192730 Summary of the Invention [Problem to be solved by the invention]

[0005] It is expected that in the future, print systems will be built by linking multiple cloud services with different purposes and service contents. One service will provide print services such as managing data submitted to be printed and managing device information of the image forming device to be printed, as well as document management services such as document editing. The other service will provide print services such as managing data submitted to be printed and managing device information of the image forming device to be printed, as well as services managing the status and print history received from the image forming device.

[0006] When multiple cloud services are linked in this way, if an error occurs in print data to be printed by an image forming device, it is desirable to notify the user, the owner of the data, who input the print data into the print system. However, in a print system configured as described above, there is a possibility that an error will be detected in a cloud service other than the one used by the user to input the print data. In this case, if the user receives an error notification from a service that the user did not directly use when inputting the data, the user may mistakenly recognize the error as unrelated to the print data they input, or may not realize that the error notification is for their own use.

[0007] Therefore, an object of the present invention is to provide a mechanism for reducing the occurrence of such problems in error notification even when a print system is constructed by linking multiple cloud services. [Means for solving the problem]

[0008] Therefore, the present invention provides a second system that cooperates with a first system capable of communicating with a client device, the second system including a management unit that links and manages user information registered in the first system with user information registered in the second system; a receiving unit that receives a print job; and a processing unit that, when an error is detected in the received print job and the print job was received from the first system, returns a print job to the user who is the owner of the print job. The The system is characterized by having a request means for requesting the first system to notify an error regarding the user information registered in the corresponding first system. [Effects of the Invention]

[0009] According to the present invention, even when a print system is constructed by linking a plurality of cloud services, it is possible to provide a mechanism for notifying an appropriate error. [Brief explanation of the drawings]

[0010] [Figure 1] Block diagram showing an example of a network system configuration [Figure 2] FIG. 1 is a diagram illustrating an example of the hardware configuration of an information processing apparatus and an image forming apparatus. [Figure 3] A diagram showing an example of the software module configuration of a print server [Figure 4] A diagram showing an example of the software module configuration of a collaboration server [Figure 5] FIG. 10 is a diagram illustrating an example of a configuration of software modules in a client device. [Figure 6] FIG. 1 is a diagram illustrating an example of a configuration of software modules in an image forming apparatus. [Figure 7] Flowchart of error detection process in print server [Figure 8] Flowchart of error notification processing in the print server of the first embodiment [Figure 9] Flowchart of error notification processing in the linkage server of the first embodiment [Figure 10] Flowchart of error notification processing in the client device according to the first embodiment [Figure 11] Example of an error notification email [Figure 12] Example of an error notification screen [Figure 13] Example of error notification destination setting screen DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of the present invention will be described below with reference to the drawings. In this embodiment, it is assumed that a print system is constructed using two cloud services that can provide print services. The print system is connected to a client device used by a user to input print data via a network such as the Internet, and an image forming device that can print print data received from the print system via the network. A print server shown in FIG. 1 operates in one of the cloud services, and a linking server that can link with the print server operates in the other cloud service. A print server (not shown) also operates in the cloud service in which the linking server operates, and a print service can be provided in which input print data is sent to an image forming device managed by the print server for printing.

[0012] If a user has registered their user account (user ID) with each cloud service, they can submit print data to either service. Because each cloud service manages account information corresponding to a user independently, this invention provides a new mechanism for associating account information for two cloud services, as described below.

[0013] This invention also assumes a case in which error information is notified when an error occurs at an image forming device that is the printing target of print data sent to a print server directly from a client device or via a link server. Hereinafter, data including data for identifying the print data to be printed, print settings, and other information related to print control will be referred to as a print job. In the following embodiments, data sent to a print server via a link server will be referred to as a print job. However, it is also possible to send print data from a link server to a print server in a format other than a print job. In such a case, in the following embodiments, the print server to which the print data is sent will manage the data in the format of a print job, including information related to specific settings and print control.

[0014] Example 1 Fig. 1 is a block diagram showing an example of the configuration of a network system according to this embodiment. As described above, in Fig. 1, a print system is constructed using two cloud services that can provide print services. One cloud service includes a print server 101. The other cloud service includes a link server 102.

[0015] The print system is also connected to a client device 103 that a user uses to input print data via a network such as the Internet, and an image forming device 104 that can print print data received from the print system via the network.

[0016] The print server 101 can manage print data submitted via the network 100 from the client device 103 or the link server 102 as a print job. The print job may be sent to the image forming device 104 for execution. Alternatively, the print server 101 may receive a print job request command from the image forming device 104 and send the print job. One or more image forming devices that are targets for printing from the print server 101 are registered in advance, along with their device information, user information, and the like, by accessing the registration service of the print server 101 using a web browser or the like on any device. The print server 101 also collects and manages operation information, such as the device status and print history, from the registered image forming devices when an event occurs or periodically. A management screen provided by the print server 101 to the web browser allows users to check a list of registered image forming devices and the status of each device.

[0017] The print server 101 is constructed by executing a program for providing the print server functions on one or more virtual machines realized by using the hardware resources of multiple information processing devices that constitute the cloud service. Note that it is also possible to realize the print server by executing the program on a dedicated information processing device.

[0018] The linkage server 102 can receive and manage print data uploaded and submitted using a web browser on the client device 103 via the network 100. It can also manage the print data as a print job that includes definitions such as print settings supported by the linkage server 102. The linkage server 102 may also be capable of providing users with a storage service or a document editing web application. Data managed and edited by these services can also be used as print data.

[0019] By accessing the registration service of the linkage server 102 using a web browser or the like of any device, a user can register information such as device information of the image forming device and user information in advance in the linkage server 102. The print server 101 can also be registered as a virtual printer as the output destination of print data. This allows a print job managed by the linkage server 102 to be submitted (transferred) to the print server 101 via the network 100. When submitting print data from the linkage server 102 to the print server 101, the user can specify the image forming device 104 as the print target. In this case, the device information of the image forming device 104 is registered in both the linkage server 102 and the print server 101. Furthermore, when submitting print data from the linkage server 102 to the print server 101, the user can execute printing by accessing the print server 101 from the image forming device he or she wants to use for printing and issuing a print request without specifying the print target. In this case, printing can also be performed from an image forming device not registered in the linkage server 102.

[0020] Linked server 102 is constructed by executing a program for providing the functions of the linked server on one or more virtual machines realized by using the hardware resources of multiple information processing devices that construct the cloud service. Note that linked server 102 can also be realized by executing the program on a dedicated information processing device.

[0021] The client device 103 executes a client application corresponding to each of the print server 101 and the linkage server 102. The client application may be a dedicated application for creating print jobs or a general-purpose web browser. The client device 103 also has an installed email application for checking emails sent to email addresses associated with user accounts registered on the print server 101 and the linkage server 102. This allows the client device 103 to receive error notifications and the like via email.

[0022] The client device 103 is located in a network environment in the user's office, or in a network environment for remote work, such as at home or in a satellite office. The user may have one client device 103 in each environment. The client device 103 can communicate with the image forming device 104 via a wired or wireless network connection, a USB connection, or the like, but does not necessarily have to be connected to the image forming device 104 in a local environment. The number of client devices connected may be different from the number shown in FIG. 1.

[0023] The image forming apparatus 104 executes client applications corresponding to the print server 101 and the link server 102. Using these client applications, the image forming apparatus 104 can communicate with the print server 101 to exchange print requests, its own device information (identification information), operation information (status, counter, log information, etc.), job information (print jobs, scan jobs, etc.), and the like. The image forming apparatus 104 may be provided by the same vendor (group) as the print server 101. The image forming apparatus 104 may be installed in an office environment or a network environment for remote work. The following description will mainly focus on an embodiment in which the image forming apparatus 104 is installed in a network environment for remote work, such as at home. The image forming apparatus 104 may be connected to the print server 101 or the link server 102 via a mobile network. The number of image forming apparatuses connected may be different from that shown in FIG. 1 .

[0024] FIG. 2A shows the hardware configuration of an information processing device. Reference numeral 201 denotes a RAM (temporary memory area). Reference numeral 202 denotes storage in which pre-installed programs and data are stored. Reference numeral 203 denotes a network interface, which connects to a network and communicates with other computers and network devices. The communication method may be either wired or wireless. A mobile network interface may also be included. Reference numeral 205 denotes an input / output interface, which inputs and outputs information and signals using a display, keyboard, mouse, touch panel, buttons, etc. Computers that do not have this hardware can be connected and operated from other computers using remote desktop or remote shell. Reference numeral 206 denotes a secondary storage device, such as a hard disk drive (HDD) or flash memory. Reference numeral 200 denotes a CPU, which executes programs loaded from the RAM 201, storage 202, secondary storage device 206, etc. In the case of an information processing device for constructing the print server 101, the CPU executes programs for implementing the functions and processing described in the flowcharts and other sections described below. In the case of an information processing device for constructing the link server 102, the CPU executes programs for implementing the functions and processing described in the flowcharts and other sections described below. In the case of an information processing device for constructing the client device 103, a client application for a web browser or a dedicated client (described later), or a program corresponding to an email application, is executed by the CPU. Each unit is connected via a system bus 204. In this embodiment, unless otherwise specified, the system bus 204 propagates control commands from the CPU 200 to each piece of hardware connected to the system bus 204.

[0025] FIG. 2B shows the hardware configuration of the image forming apparatus 104. Reference numeral 208 denotes a RAM (random access memory) for temporary memory storage. Reference numeral 209 denotes storage in which embedded programs and data are stored. Reference numeral 210 denotes a network interface, which connects to a network and communicates with other computers and network devices. Communication may be via either wired or wireless means. A mobile network interface may also be included. Reference numeral 214 denotes an input / output interface, which inputs and outputs information and signals using a touch panel, buttons, or the like. Devices that do not have this hardware can also be connected and operated from other computers via a remote interface or the like. Reference numeral 215 denotes a secondary storage device, such as a hard disk drive (HDD) or flash memory. Reference numeral 207 denotes a CPU, which executes programs loaded from the RAM 208, storage 209, secondary storage device 215, or the like. Reference numeral 213 denotes a printer, which executes jobs such as printing. Reference numeral 212 denotes a device controller, which receives control commands from the CPU 207 and controls the printer 213. Each component is connected via a system bus 211. In this embodiment, unless otherwise specified, the system bus 211 transmits control commands from the CPU 207 to each piece of hardware connected to the system bus 211 .

[0026] 3 is a block diagram showing an example of the functional configuration of the software modules of the print server 101. The programs of the print server 101 are read from the RAM 201, storage 202, secondary storage device 206, etc., and executed by the CPU 200. Connection to external devices such as the link server 102 is made via the network interface 203.

[0027] The print server 101 receives print jobs submitted from the collaboration server 102 or the client device 103 via a communication unit 300 and stores them in a job storage unit 301. A job determination unit 302 determines whether there are any errors involved in the processing based on the print job. The errors that are determined include errors caused by print settings included in the print job and errors detected when the print job violates the security policy of the organization to which the user who owns the print job belongs. If no such errors are found, the print job may be sent to an image forming device and the image forming device may be instructed to execute printing. Alternatively, the print job may be stored as is, and upon receiving a print request from the image forming device, the print job may be returned and printed.

[0028] If the job determination unit 302 determines that an error has occurred, the notification management unit 303 creates an error notification. At this time, the following is confirmed from the contents of the print job. · Presence or absence of system collaboration (with collaboration server 102) -User information of the user who owns the print job If there is no system cooperation, the user management unit 304 is referenced and a print job error is notified to the user who is the owner of the print job. This error can be notified by email using the email address registered in association with the user account registered on the print server 101, identified based on the user identification information (ID) described as the owner in the print job. In addition, the user can check the error in their job by logging in to a website provided by the print server 101 using the user account.

[0029] If there is system collaboration, the system references the user management unit 304, collaboration destination user linking unit 305, and collaboration destination error linking unit 306. The system creates an error notification request using user information registered in the collaboration server 102 that is managed in association with the user ID described as the owner of the print job. The notification management unit 303 sends the error notification request to the collaboration server 102 via the communication unit 300.

[0030] An example of part of the job information of a print job, including information on whether or not service cooperation is performed, is shown below. In the example below, information indicating cooperation with the cooperation server 102 is written in the last line. - Print jobs that include information on whether or not service integration is enabled { “JobId”:“JOB00001”, “UserId”:“USR00001”, “DocumentName”:“DOC0001”, “DocumentPath”:“ / path / to / document”, “DocumentType”:“text”, “Date”:“2021 / 4 / 1”, “Time”:12:34.56, “Link”:True, “LinkedSystem”: “Linked service 102”, } A specific example of an error that can occur in a print job is a policy violation. Below is an example of an error notification when a policy is violated. It is also possible to include the job identifier of the print job ("JobId":"JOB00001"). Example of a print policy violation error notification { “ErrorId”:“ERR04011334”, “ErrorCode”:“ERR0001”, “ErrorTitle”:“Print Policy Error”, “ErrorDetail”:“Print Policy Error is happened.Please check your policy.”, “UserId”:“USR00001”, “Date”:“2020 / 4 / 1”, “Time”:13:34.56,}

[0031] An example of a correspondence table between user information registered in the print server 101 and user information registered in the linked server 102, which is held by the linked user association unit 305, is shown below. In this table, the information is listed using identification information (ID). Note that there is also user information that does not have a correspondence. [Table 1]

[0032] Below, an example of the correspondence between the error code detected by the print server 101 and the error code in the collaboration server 102, which is held by the collaboration destination error linking unit 306, is shown. [Table 2]

[0033] Below is an example of an error notification request created by referencing the link error code correspondence table. In this example, the notification is sent when a policy violation error indicated by the error code "ERR0001" is detected in a job of a user indicated by "USR00001" registered on the print server 101. It is also possible to include the job identifier ("JobId") of the print job. Example of a print policy violation error notification request { “Id”:“NTF0001”, “Type”:“Notification”, “LinkedErrorCode”:“LinkedErr001”, “LinkedUserId”:“LinkedUser001”, “Date”:“2020 / 4 / 1”, “Time”:14:34.56, } 4 is a block diagram showing an example of the functional configuration of the software modules of the linkage server 102. The programs of the linkage server 102 are read from the RAM 201, storage 202, secondary storage device 206, etc., and executed by the CPU 200. Access to external devices such as the print server 101 is performed via the network interface 203.

[0034] The linkage server 102 receives print data from the client device 103 via the communication unit 400 and stores it in the job storage unit 401. The stored print data can be submitted to the print server 101 via the communication unit 400. The linkage server 102 can also send a print job containing print data and predetermined settings to the image forming device and instruct it to print. Alternatively, the linkage server 102 can receive a print request from the image forming device and return a print job.

[0035] The linkage server 102 receives an error notification request from the print server 101 via the communication unit 400. The notification management unit 402 creates an error notification from the contents of the error notification request. At this time, the following is confirmed from the contents of the error notification request. The job identifier for the print job - The print job for which the error notification is to be sent and the user who owns it Error Codes The notification management unit 402 then creates an error notification that includes the above confirmed information. This error can be notified by email using the email address registered in the linkage server 102, which is associated with the user account identified based on the user ID described in the error notification request. In addition, the user can check for errors in their own jobs by logging in to a website provided by the linkage server 102 using the user account.

[0036] 5A is a block diagram showing an example of the functional configuration of the software modules of the client device 103. The programs of the client device 103 are read from the RAM 201, storage 202, secondary storage device 206, etc., and executed by the CPU 200. Access to external devices such as the print server 101 is performed via the network interface 203.

[0037] A print service client 501 is installed on the client device 103. This module is implemented by a dedicated client application of the print server 101. Alternatively, a web browser can be used to access a web service site provided by the print server 101 and submit print data. In this case, a login operation using a user account registered with the service is required.

[0038] A job management unit 503 of the print service client 501 manages information about print jobs. The print jobs are submitted to the print server 101 via the communication unit 500. The job management unit 503 can also receive an error notification for the submitted print job from the print server 101 via the communication unit 500. The received error notification is displayed in a notification display unit 502. FIG. 12A is a sample screen display when a print job error notification is received from the print server 101 and displayed in the notification display unit 502.

[0039] Reference numeral 510 denotes a web browser, which can be used to specify a URL or the like to access web pages provided by the web servers of the print server 101, the linkage server 102, and the image forming apparatus 104. By accessing a cloud service including the linkage server 102 and logging in with a registered user account, storage services, document editing services, and the like can be used. Reference numeral 511 denotes an email application for receiving emails.

[0040] Fig. 5(B) is a block diagram showing another example of the functional configuration of the software modules of the client device 103. The configuration that differs from Fig. 5(A) will be described.

[0041] In the example of FIG. 5(B), a linked service client 504 is installed on the client device 103. This module is implemented by a dedicated client application for the linked server 102. Alternatively, a web browser can be used to access a web service site provided by the linked server 102 and submit print data. In this case, a login operation using a user account registered with each service is required.

[0042] When printing from the print server 101, the client device 103 shown in the example of Figure 5 (B) does not need to install the print service client 501, and can submit print data to the print server 101 via the collaboration server 102.

[0043] A job management unit 506 of the collaboration service client 504 manages print job information. The print job is submitted to the collaboration server 102 via the communication unit 500. Furthermore, a job error detected in a print job submitted to the print server 101 via the collaboration server 102 is notified based on the error notification request described above. Error notifications from the collaboration server 102 can be received by the email application 511. If a notification is received directly from the collaboration service 102, it can also be displayed in the notification display unit 505. Figure 12(B) is a sample screen display when a print job error notification is received from the collaboration server 102 and displayed in the notification display unit 505. Alternatively, a web browser can be used to access a web service site provided by the collaboration server 102 and submit print data. In this case, a login operation using a user account registered with each service is required.

[0044] It is also possible to install both the print service client 501 and the cooperative service client 504 in the client device 103 .

[0045] 6 is a block diagram showing an example of the functional configuration of software modules of the image forming apparatus 104. The programs of the image forming apparatus 104 are read from the RAM 208, storage 209, secondary storage device 215, etc., and executed by the CPU 207. Execution of print jobs, etc. is performed by the CPU 207 controlling and executing the printer 213 via the device controller 212. Access to external devices such as the print server 101 is performed via the network interface 210.

[0046] The image forming apparatus 104 has a built-in print service client 602. The image forming apparatus 104 receives print jobs from the print server 101 via a communication unit 600 and manages them in a job management unit 604. The received print jobs are executed by a job execution unit 601. The image forming apparatus 104 can manage device identification information and device operation information (status, counter, log information, etc.) in a device information management unit 603. The image forming apparatus 104 can manage job information (print jobs, scan jobs, etc.) in the job management unit 604. The image forming apparatus 104 can communicate information from the device information management unit 603 and the job management unit 604 with the print server 101 via the communication unit 600.

[0047] The print job error determination process in the print server 101 will be described with reference to the flowchart shown in FIG.

[0048] In S700, the print server 101 receives a print job via the communication unit 300. In S701, the job determination unit 302 determines whether there is an error in the print job. If there is an error, in S702 the notification management unit 303 executes job error linked notification processing (FIG. 8). Errors detected from the job here include errors related to the policy violations mentioned above. On the other hand, if there is no error, in S703 the job storage unit 301 stores the print job as an executable print job.

[0049] The job error collaborative notification process in the notification management unit 303 of the print server 101 will be described with reference to the flowchart shown in FIG.

[0050] In S800, the notification management unit 303 acquires attribute information of the print job. In S801, the notification management unit 303 checks the following information from the attribute information of the print job. ·System integration - The user who owns the print job If, as a result of checking whether or not there is system integration, it is determined that there is no system integration, in S805, the notification management unit 303 refers to the information managed by the user management unit 304 and notifies an error based on the user account that is the owner of the print job.

[0051] On the other hand, if it is determined that there is system collaboration, in S802, the information managed by the user management unit 304 and the collaboration destination user linking unit 305 is referenced, and user information registered in the collaboration destination collaboration server 102 that is linked to the user information of the owner of the print job is acquired. In S803, the collaboration destination error linking unit 306 acquires the error code in the collaboration server 102 that is linked to the detected error.

[0052] In S804, the notification management unit 303 creates and sends an error notification request to the collaboration server 102, adding the user information of the collaboration destination and the collaboration destination error code acquired in S802 and S803, and the job identifier of the print job ("JobId").

[0053] The job error notification process in the linkage server 102 will be described with reference to the flowchart shown in FIG. In S900, the communication unit 400 receives a print job error notification request from the print server 101. Here, the notification management unit 402 checks the following information from the received error notification request. The job identifier for the print job - Information about the user who owns the print job Error Codes The notification management unit 402 then creates an error notification that includes this information. The notification management unit 402 references the information managed by the user management unit 403 and notifies the user account that is the owner of the print job of the error (S901). The notification is sent to a dedicated client application of the client device 103.

[0054] The error notification process in the client device 103 will be described using the flowchart shown in Fig. 10. This process is executed by the print service client 501 that receives the notification shown in S805 of Fig. 8, or by the cooperation destination service client 504 that receives the notification shown in S901 of Fig. 9. This process is a common operation when an error notification is received by the print service client 501 and the cooperation destination service client 504, and in the following description, they will be collectively referred to as the client. This process starts when a user logs in by operating the client.

[0055] In S1001, the client determines whether an error notification associated with the logged-in user exists. If an error notification including user information corresponding to the identification information of the logged-in user of the client is received, it is determined that an error notification exists. If an error notification associated with the logged-in user does not exist, this process ends.

[0056] On the other hand, if an error associated with the logged-in user exists, the client displays error notification information in the notification display unit 502 in S1002.

[0057] Example 2 In the second embodiment, when an error occurs in a print job, the attribute information of the print job is checked. If the print job does not have system integration, an error notification email is sent to the email address linked to the user account that owns the job. If the print job has system integration, the account of the linked service that is linked to the user account that owns the job is obtained. An error notification email is sent to the email address linked to the account of the linked service.

[0058] The user can receive and check the error notification sent to the email address corresponding to the account registered with any of the cloud services using the email application 511 of the client device 103.

[0059] In this embodiment, differences from the first embodiment will be described below.

[0060] 8 and S901 in Fig. 9, the print server 101 and the collaboration server 102 identify a registered email address linked to the account of the user who is the job owner to be notified, and then execute an error notification by email to that email address.

[0061] In step S804, the print server 101 sends the following error notification request to the collaboration server 102. The error notification request specifies email ("e-mail") as the notification type. As described above, the request may include a job identifier.

[0062] Example of a print policy violation error notification email request { “Id”:“MAIL0001”, “Type”:“e-mail”, “LinkedErrorCode”:“LinkedErr001”, “LinkedUserId”:“LinkedUser001”, “Date”:“2020 / 4 / 1”, “Time”:14:34.56, } 11 is a sample email for notifying a job error in the second embodiment. The email body contains information such as the error code and the date and time of the error. The email can also contain information that is easy for the sender system to understand (print server 101, collaboration server 102) and a job identifier.

[0063] (Application example) As mentioned in the first and second embodiments, the error notification may be either on the screen or by e-mail. The user may also be able to select and set the notification destination on the screen. In this case, the notification destination may be selected, such as on-screen notification, error notification, or multiple e-mail addresses.

[0064] FIG. 13 shows a sample setting screen for setting the notification destination for job errors.

[0065] In the first and second embodiments, notification is made to the client device 103 or the user's e-mail address, but at the same time, an error may be notified on the screen of the image forming device 104 registered in the service.

[0066] The error notification on the screen and by e-mail mentioned in the first and second embodiments do not necessarily have to be initiated by a print job error. For example, when a device error occurs in the image forming device 104 registered in the service, the device information management unit 603 may send an error notification to the print server 101 via the communication unit 600. The print server 101 may receive the error notification and send the error notification mentioned in the first and second embodiments to the user who uses the registered image forming device.

[0067] (Other Examples) The present invention also includes an apparatus or system configured by appropriately combining the above-described embodiments, and a method thereof.

[0068] Here, the present invention is a device or system that executes one or more pieces of software (programs) that realize the functions of the above-described embodiments. Also, a method for implementing the above-described embodiments executed by the device or system is also one aspect of the present invention. The program is supplied to the system or device via a network or various storage media, and is read into one or more memories and executed by one or more computers (CPUs, MPUs, etc.) of the system or device. In other words, the present invention also includes the program itself, or various storage media that store the program and are readable by a computer. The present invention can also be realized by a circuit (e.g., ASIC) that realizes the functions of the above-described embodiments. [Explanation of symbols]

[0069] 101 Print Server 102 Collaboration Server 103 Client Device 104 Image forming device

Claims

1. a second system cooperating with the first system capable of communicating with a client device, a management means for linking and managing user information registered in the first system corresponding to user information registered in the second system; a receiving means for receiving a print job; a requesting means for requesting the first system to notify an error to user information registered in the first system corresponding to a user who is an owner of the print job, when an error is detected in the received print job and the print job has been received from the first system; A second system comprising:

2. The second system according to claim 1, further comprising a notification means for executing an error notification based on user information of a user who is the owner of the print job when an error is detected in the received print job and the print job was received from a client device without going through the first system.

3. 3. The second system according to claim 2, wherein the error notification by the notification means is made by email.

4. 4. The second system according to claim 2, further comprising a providing unit that provides a setting screen for selecting a method of error notification by said notifying unit.

5. 1. A method in a second system interfacing with a first system capable of communicating with a client device, comprising: a management step of linking and managing user information registered in the first system corresponding to user information registered in the second system; a receiving step of receiving a print job; a request step of requesting the first system to notify an error to user information registered in the first system corresponding to a user who is an owner of the print job, when an error is detected in the received print job and the print job has been received from the first system; A method comprising:

6. 6. The method of claim 5, further comprising a notification step of executing an error notification based on user information of a user who is the owner of the print job if an error is detected in the received print job and the print job was received from a client device without going through the first system.

7. 7. The method according to claim 6, wherein the error notification in the notification step is made by email.

8. 8. The method according to claim 6, further comprising the step of providing a setting screen for selecting a method of error notification in the notification step.

9. A program for causing a computer to execute a method in a second system that cooperates with a first system that can communicate with a client device, the program comprising: a management step of linking and managing user information registered in the first system corresponding to user information registered in the second system; a receiving step of receiving a print job; a request step of requesting the first system to notify an error to user information registered in the first system corresponding to a user who is an owner of the print job, when an error is detected in the received print job and the print job has been received from the first system; A program comprising:

Images