Server device, server device control method, and program

Abstract

To provide a server device which can notify a user of an execution situation of a print job put into an image formation device from an external device even when the user is away from the image formation device.SOLUTION: In an image formation system, a chat server notifies a chat application which operates on a mobile terminal of information on a print job executed by an MFP via a network. The chat server, when a retention print job of a user B is put into the MFP and the MFP is executing a retention print job of a user A, displays a message showing that the print job of the user B cannot be executed because the retention print job of the user A is being executed on an operation panel of the mobile terminal used by the user B.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a server device, a control method for a server device, and a program. [Background technology]

[0002] Image forming apparatuses that execute print jobs are known. A user can check the execution status of a print job, such as whether it is waiting or in progress, via an operation panel or the like provided on the image forming apparatus. Furthermore, image forming apparatuses have a function called reservation printing, which starts printing of a print job submitted from an external device in accordance with a print instruction from the user who submitted the print job, rather than immediately executing the print job.

[0003] Also, a system has been proposed in which a server device interactively notifies a communication terminal equipped with a chat application of fax information received by an image forming device in real time (see, for example, Patent Document 1). This allows a user to check the fax information received by the image forming device using the communication terminal even if the user is away from the image forming device. [Prior art documents] [Patent documents]

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

[0005] However, in the technology of Patent Document 1, the execution status of a print job submitted to an image forming apparatus from an external device is not notified to the communication terminal. Therefore, a user submits a print job and moves to the image forming apparatus, only to realize that the print job he or she submitted is not being executed because another print job submitted by another user is currently being executed, which is very inconvenient.

[0006] The present invention aims to provide a server device, a control method for the server device, and a program that can inform a user of the execution status of a print job submitted to an image forming device from an external device even when the user is away from the image forming device. [Means for solving the problem]

[0007] In order to achieve the above object, a server device of the present invention is a server device that notifies an application of a communication terminal of information regarding a print job executed by an image forming device, and includes: an acquisition means that acquires status information of the print job input to the image forming device from an external device; and a control means that displays a predetermined message on a display unit of the communication terminal based on the status information; The control means When a print job is input from an external device to the image forming device and the image forming device is executing another print job different from the first print job, ,before a message indicating that the one print job cannot be executed because the other print job is being executed is displayed on the display unit of the communication terminal; When a user operating the communication terminal is logged in to the image forming apparatus, the predetermined message is not displayed on the display unit of the communication terminal. It is characterized by: [Effects of the Invention]

[0008] According to the present invention, even if the user is away from the image forming apparatus, the user can be informed of the execution status of a print job input to the image forming apparatus from an external device. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram schematically illustrating a configuration of an image forming system including a server device according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram schematically illustrating the hardware configuration of the MFP in FIG. [Figure 3] 2 is a block diagram illustrating a hardware configuration of the chat server of FIG. 1. FIG. [Figure 4]2 is a block diagram illustrating a hardware configuration of the mobile terminal of FIG. 1. [Figure 5] FIG. 2 is a block diagram illustrating a software configuration of the MFP in FIG. [Figure 6] FIG. 2 is a block diagram illustrating a schematic configuration of a chatbot program that runs on the chat server of FIG. 1. [Figure 7] 2 is a block diagram illustrating a schematic configuration of a chat application that operates on the mobile terminal of FIG. 1. [Figure 8] 4 is a flowchart showing the procedure of a print job control process executed by the MFP of FIG. [Figure 9] 10 is a flowchart showing the procedure of a notification control process performed by the chat server of FIG. [Figure 10] 2 is a diagram showing an example of a management table managed by the chat server of FIG. 1. FIG. [Figure 11] 2 is a diagram showing an example of a chat information management table managed by the chat server of FIG. 1. FIG. [Figure 12] FIG. 10 is a diagram showing an example of a message template used to generate chat message data in step S915 of FIG. 9. [Figure 13] 10 is a flowchart showing the procedure of a button event control process executed by the chat server of FIG. [Figure 14] 10 is a flowchart showing the procedure of a message display control process executed by the mobile terminal of FIG. [Figure 15] 1. FIG. 4 is a sequence diagram showing an example of a chat notification performed by the image forming system of FIG. [Figure 16] FIG. 5 is a diagram showing an example of a chat screen displayed on the operation panel of FIG. 4. [Figure 17] 1. FIG. 4 is a sequence diagram showing another example of a chat notification performed by the image forming system of FIG. [Figure 18] FIG. 5 is a diagram showing an example of a chat screen displayed on the operation panel 401 of FIG. 4. [Figure 19] 10 is a flowchart showing another procedure of the message notification determination process in step S913 of FIG. 9. [Figure 20] FIG. 20 is a diagram showing an example of a setting screen for setting whether or not to perform the determinations in steps S1904 to S1908 in FIG. DETAILED DESCRIPTION OF THE INVENTION

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

[0011] Fig. 1 is a block diagram showing a schematic configuration of an image forming system 1 including a server device according to the present embodiment. In Fig. 1, the image forming system 1 is made up of MFPs 10 and 11, a chat server 20 as a server device, information processing devices 30 and 31, mobile terminals 40 and 41, and a wireless access point 50. These are connected to each other via a network 60 and are capable of communicating with each other. MFP is an abbreviation for Multi Function Peripheral.

[0012] MFP10 and MFP11 are image forming devices that have a function of printing print jobs received from information processing device 30, information processing device 31, mobile terminal 40, and mobile terminal 41. Note that in the present embodiment, as an example, a configuration in which two MFPs are connected to network 60 will be described, but the present invention is not limited to this configuration, and for example, a configuration in which one MFP or three or more MFPs are connected to network 60 may also be used.

[0013] Chat server 20 is a server that provides a chat service between mobile terminals and MFPs as a chatbot. For example, chat server 20 receives print job information from MFP10 or the like via network 60, and notifies a chat application 701 (described later in FIG. 7) running on mobile terminal 40 or mobile terminal 41 of the execution status of the print job. Chat server 20 also receives chat information (described later) from chat application 701 (described later), and sends instructions regarding the print job to MFP10 or MFP11 based on this chat information.

[0014] The information processing device 30 and the information processing device 31 are devices such as personal computers. A user can use the information processing device 30 or the information processing device 31 to send document data to be printed to the MFP 10 or the MFP 11 as a print job. Note that in the present embodiment, as an example, a configuration in which two information processing devices are connected to the network 60 will be described, but the present invention is not limited to this configuration, and for example, a configuration in which one or three or more information processing devices are connected to the network 60 may also be used.

[0015] The mobile terminals 40 and 41 are communication terminals such as smartphones and tablet terminals. In the present embodiment, the mobile terminals 40 and 41 are described as devices such as smartphones and tablet PCs, but the mobile terminals 40 and 41 are not limited to such devices. The mobile terminals 40 and 41 may be devices other than smartphones and tablet PCs as long as they are devices that can be connected to a network.

[0016] Mobile terminal 40 and mobile terminal 41 can connect to network 60 via wireless access point 50 and communicate with chat server 20. While the present embodiment describes, as an example, a configuration in which two mobile terminals are connected to wireless access point 50, the present invention is not limited to this configuration, and one or three or more mobile terminals may be connected to wireless access point 50. A user can check the execution status of a print job on MFP 10 or MFP 11 and issue instructions for the print job using a chat application 701 (described later) shown in FIG. 7 that runs on mobile terminal 40 or mobile terminal 41. Wireless access point 50 is a wireless device that wirelessly communicates with mobile terminal 40 or mobile terminal 41, enabling connection of mobile terminal 40 or mobile terminal 41 to network 60.

[0017] Next, a description will be given of the hardware configuration of the MFP 10 and the MFP 11. In this embodiment, the MFP 10 and the MFP 11 have the same hardware configuration, and the hardware configuration will be described below using the MFP 10 as an example.

[0018] Fig. 2 is a block diagram showing a schematic hardware configuration of the MFP 10 shown in Fig. 1. In Fig. 2, the MFP 10 includes a controller unit 100, an operation unit 111, a scanner 112, and a printer 113. The controller unit 100 is connected to the operation unit 111, the scanner 112, and the printer 113.

[0019] The controller unit 100 includes a CPU 101, a RAM 102, a ROM 103, a HDD 104, an operation unit I / F 105, a network I / F 106, a scanner I / F 107, and a printer I / F 108. These are connected to one another via a system bus 110.

[0020] The CPU 101 starts up the MFP 10 based on a boot program stored in the ROM 103. The CPU 101 also reads a control program stored in the HDD 104 and executes predetermined processing using the RAM 102 as a work area. The HDD 104 stores control programs for implementing functions of the MFP 10, such as a copy function and a print function. The operation unit I / F 105 controls data input / output communication with the operation unit 111. The network I / F 106 is connected to the network 60 and controls input / output of information via the network 60. The scanner I / F 107 acquires image data from the scanner 112 and inputs / outputs scanner control data. The printer I / F 108 outputs output image data to the printer 113 and inputs / outputs printer control data.

[0021] The operation unit 111 is an interface that accepts instructions from a user and displays various information. The operation unit 111 includes an input device such as a touch panel or hard keys, and a display device such as an LCD or LED. The scanner 112 includes an optical reading device such as a CCD, and has the function of optically scanning a paper medium and reading it as electronic image data. The printer 113 has the function of forming the electronic image data as an image on a recording medium such as paper.

[0022] The MFP 10 has a print function of printing, on a printer 113, a print job received from the information processing device 30 or the information processing device 31 via the network I / F 106. The MFP 10 also has a reservation print function of temporarily storing the received print job in the HDD 104 and printing the print job on the printer 113 in response to a print instruction from the user via the operation unit 111 or an external device. Furthermore, when the MFP 10 executes processing related to a print job, it stores status information of the print job in the HDD 104. The status information of the print job stored in the HDD 104 is transmitted via the network I / F 106 to external devices such as the information processing device 30, the information processing device 31, the mobile terminal 40, and the mobile terminal 41.

[0023] Fig. 3 is a block diagram showing a schematic hardware configuration of chat server 20 in Fig. 1. Chat server 20 includes control unit 120, operation display unit 128, and operation input unit 129. Control unit 120 is connected to operation display unit 128 and operation input unit 129. Control unit 120 includes CPU 121, RAM 122, ROM 123, HDD 124, operation unit I / F 125, and network I / F 126. These are connected to one another via system bus 127.

[0024] The CPU 121 executes various control programs and controls the overall operation of the chat server 20. The ROM 123 stores various control programs. For example, the ROM 123 stores the mobile terminal 40 and a chatbot program 601 (described later in FIG. 6) for providing a chat service to the mobile terminal 40. The CPU 121 reads out the control programs stored in the ROM 123 or the HDD 124, and executes predetermined processing using the RAM 122 as a work area. The network I / F 126 controls input and output of information via the network 60. The operation unit I / F 125 controls data output communication to the operation display unit 128 and data input and output communication with the operation input unit 129. The operation display unit 128 is a display interface for the user and includes a display device such as an LCD or LED. The operation input unit 129 is an interface for inputting instructions from the user and includes input devices such as a keyboard and a mouse.

[0025] Next, a description will be given of the hardware configuration of mobile terminal 40 and mobile terminal 41. In this embodiment, mobile terminal 40 and mobile terminal 41 have the same hardware configuration, and the hardware configuration will be described below using mobile terminal 40 as an example.

[0026] Fig. 4 is a block diagram showing a schematic hardware configuration of mobile terminal 40 of Fig. 1. In Fig. 4, mobile terminal 40 includes an operation panel 401, a CPU 402, a ROM 403, a RAM 404, an HDD 405, an NFC communication unit 407, a Bluetooth communication unit 408, and a wireless LAN communication unit 409. These are connected to each other.

[0027] The CPU 402 reads out the control program stored in the ROM 403 and various information saved in the HDD 405 into the RAM 404, and executes various processes for controlling the operation of the mobile terminal 40. The ROM 403 stores the control program. For example, the ROM 403 stores a control program that runs a chat application 701 shown in FIG. 7, which will be described later. The RAM 404 is used as the main memory of the CPU 402 and as a temporary storage area such as a work area for the CPU 402. The HDD 405 stores various data such as photographs and electronic documents.

[0028] The operation panel 401 has a touch panel function that can detect a user's touch operation, and displays various screens provided by the OS and chat application. The user can input desired operation instructions to the mobile terminal 40 by touching the operation panel 401. The mobile terminal 40 exchanges data with various peripheral devices via an NFC communication unit 407, a Bluetooth communication unit 408, and a wireless LAN communication unit 409. Communication with the wireless access point 50 is also performed via the wireless LAN communication unit 409.

[0029] Next, a description will be given of the software configuration of the MFP 10 and the MFP 11. In this embodiment, the MFP 10 and the MFP 11 have the same software configuration, and the software configuration will be described below using the MFP 10 as an example.

[0030] Fig. 5 is a block diagram showing a schematic software configuration of MFP 10 in Fig. 1. In Fig. 5, MFP 10 includes, as software modules, a network communication control module 501, a job control module 502, and a printer control module 503. MFP 10 further includes a UI control module 504, a user management module 505, a print job storage module 510, and a print execution queue 511. Processing by the above-mentioned modules is realized by CPU 101 of MFP 10 executing programs stored in ROM 103 or the like.

[0031] The network communication control module 501 controls the network I / F 106 to control input and output of data to and from external devices. For example, communication of print jobs and information related to print jobs is controlled by the network communication control module 501. The job control module 502 performs job control of print jobs and manages the status of print jobs. The printer control module 503 controls the printer I / F 108 to cause the printer 113 to execute print processing. The UI control module 504 controls the screen display of the operation unit 111 and processes user operations accepted by the operation unit 111. The user management module 505 manages information about users who use the MFP 10. The print job storage module 510 performs processing to store print jobs received by the MFP 10. The print execution queue 511 records print jobs to be processed by the printer control module 503. In the MFP 10, print processing is executed sequentially starting from the print job recorded first in the print execution queue.

[0032] Fig. 6 is a block diagram showing a schematic configuration of a chatbot program 601 that runs on the chat server 20 of Fig. 1. In Fig. 6, the chatbot program 601 includes a print job status management module 602, a chat application user management module 603, and a chat management module 604. The chatbot program 601 further includes a chat application communication module 605, an MFP data communication module 606, and an MFP user management module 607.

[0033] A print job status management module 602 manages print job statuses (status information) described later received from the MFP10 or MFP11. A chat application user management module 603 manages information (hereinafter referred to as "user information") related to users who use a chat application 701 in FIG. 7 described later. A chat management module 604 controls interactions with the chat application 701 described later based on the print job status and user information described later. A chat application communication module 605 controls communications with the chat application 701 described later, and exchanges messages with the chat application 701 described later. An MFP data communication module 606 controls communications with the MFP10 or MFP11. An MFP user management module 607 manages user information for users who are permitted to log in to the MFP10 or MFP11.

[0034] Next, we will explain the software configuration of mobile terminal 40 and mobile terminal 41. In this embodiment, mobile terminal 40 and mobile terminal 41 have the same software configuration, and the software configuration will be explained below using mobile terminal 40 as an example.

[0035] Fig. 7 is a block diagram showing a schematic configuration of a chat application 701 that runs on the mobile terminal 40 of Fig. 1. In Fig. 7, the chat application 701 is made up of a chat display module 702, a UI operation module 703, and a chat server communication module 704. The processing by these modules is realized by the CPU 402 of the mobile terminal 40 executing a program stored in the ROM 403 or the like.

[0036] A chat display module 702 controls the display of a chat screen on the operation panel 401. A UI operation module 703 processes instructions for the chat application 701 that are input by the user to the operation panel 401. A chat server communication module 704 communicates with the chat server 20 via the wireless LAN communication unit 409.

[0037] Next, a description will be given of the execution of a print job by the MFP 10 and the MFP 11. In this embodiment, the MFP 10 and the MFP 11 execute a print job in the same procedure, so the following description will be given of the case where the MFP 10 executes a print job as an example.

[0038] Fig. 8 is a flowchart showing the procedure of print job control processing executed by MFP 10 of Fig. 1. The print job control processing of Fig. 8 is realized by CPU 101 of MFP 10 executing a program stored in ROM 103 or the like.

[0039] 8, CPU 101 determines whether a print job has been received by job control module 502 (step S801). In this embodiment, MFP 10 receives print jobs via network 60 from information processing device 30, information processing device 31, mobile terminal 40, mobile terminal 41, etc. by network communication control module 501. MFP 10 receives either a reserved print job or a normal print job as the print job. A reserved print job is a print job in which the received print job is temporarily stored in HDD 104 and printing processing by printer 113 is started in accordance with a user's print instruction from operation unit 111 or an external device. A normal print job is a print job in which printing processing by printer 113 is started immediately without storing the received print job in HDD 104.

[0040] If it is determined in step S801 that a print job has not been received, the process proceeds to step S805, which will be described later. If it is determined in step S801 that a print job has been received, CPU 101 stores the received print job in print job storage module 510 (step S802). Next, CPU 101 determines whether the received print job is a reserved print job (step S803).

[0041] If it is determined in step S803 that the received print job is a reserved print job, the process proceeds to step S805, which will be described later. If it is determined in step S803 that the received print job is not a reserved print job, the received print job is a normal print job. In this case, CPU 101 moves the received print job to print execution queue 511 (step S804). The print job moved to print execution queue 511 is processed sequentially by printer control module 503 and printed by printer 113. Next, CPU 101 determines whether a print instruction for the reserved print job stored in print job storage module 510 has been accepted (step S805).

[0042] If it is determined in step S805 that a print instruction for the reserved print job has not been accepted, the process proceeds to step S807, which will be described later. If it is determined in step S805 that a print instruction for the reserved print job has been accepted, CPU 101 moves the print job saved in print job save module 510 to print execution queue 511 (step S806). As a result, the reserved print jobs saved in print job save module 510 are processed sequentially by printer control module 503 and printed by printer 113. Next, CPU 101 determines whether a cancel instruction for the print job being executed has been accepted (step S807). In this embodiment, the user can issue a cancel instruction from operation unit 111 or an external device connected via network 60, just like issuing a print instruction.

[0043] If it is determined in step S807 that a cancel instruction for the print job being executed has not been accepted, the process proceeds to step S809, which will be described later. If it is determined in step S807 that a cancel instruction for the print job being executed has been accepted, CPU 101 causes job control module 502 to perform processing to cancel the print job being executed (step S808). Next, CPU 101 transmits a print job status indicating the status of the print job being processed by MFP 10 to chat server 20 (step S809). The print job status includes various information that is set in management table 1000 in FIG. 10, which will be described later. Thereafter, the process returns to step S801. In this way, MFP 10 and MFP 11 repeatedly execute the processing of steps S801 to S809 described above, and the print job status updated in accordance with changes in the status of the print job is transmitted from MFP 10 and MFP 11 to chat server 20.

[0044] Fig. 9 is a flowchart showing the procedure of the notification control process by the chat server 20 of Fig. 1. The notification control process of Fig. 9 is realized by the CPU 121 of the chat server 20 executing the chatbot program 601 stored in the ROM 123. In the notification control process of Fig. 9, a message is sent to the chat application 701 running on the mobile terminal 40 or the mobile terminal 41 based on the print job status received from the MFP10 or the MFP11. The notification control process of Fig. 9 is executed, for example, when the chat server 20 receives the print job status from the MFP10 or the MFP11.

[0045] 9, first, CPU 121 acquires a print job status from MFP 10 or MFP 11 (step S901). CPU 121 registers the print job status acquired from an apparatus such as MFP 10 or MFP 11 in management table 1000 in FIG. 10. Management table 1000 is stored in HDD 124 or the like. Management table 1000 includes occurrence time 1001, user ID 1002, image forming apparatus ID 1003, job ID 1004, file name 1005, and job type 1006. Management table 1000 further includes job status 1007, job acceptance time 1008, print start time 1009, and print end time 1010.

[0046] The time when a change in the status of the print job occurred is set in the occurrence time 1001. An ID indicating the user who instructed the print job to be submitted is set in the user ID 1002. An ID indicating the MFP to which the print job was submitted is set in the image forming device ID 1003. An ID for identifying the print job in the MFP to which the print job was submitted is set in the job ID 1004. The file name of the document data or image data set in the print job is set in the file name 1005.

[0047] The job type 1006 contains information indicating the type of print job, such as "normal print" indicating a normal print job or "reserved print" indicating a reserved print job. The job status 1007 contains information indicating the status of the print job, such as "waiting," "waiting to start printing," "printing," "printing completed," or "cancelled." "Waiting" indicates that the reserved print job has not been moved to the print execution queue 511 and remains stored in the print job storage module 510. "Waiting to start printing" indicates that the print job has been moved to the print execution queue 511 but printing processing by the printer 113 has not yet started. "Printing" indicates that the printer 113 is currently executing printing processing of the print job. "Printing completed" indicates that the printer 113 has completed printing processing of the print job. "Cancelled" indicates that the print job has been canceled in accordance with a cancellation instruction from the user.

[0048] The time when an apparatus such as MFP10 or MFP11 receives a print job is set in job reception time 1008. The time when an apparatus such as MFP10 or MFP11 starts printing processing of the print job is set in print start time 1009. The time when an apparatus such as MFP10 or MFP11 ends printing processing of the print job is set in print end time 1010.

[0049] Next, CPU 121 acquires one print job status from among the multiple print job statuses registered in management table 1000. CPU 121 acquires the job state of the acquired print job status (step S902). Next, CPU 121 determines the job state acquired in step S902 (step S903) and allocates processing based on the job state.

[0050] If it is determined in step S903 that the job status acquired in step S902 is "Waiting," the process proceeds to step S904. In step S904, the CPU 121 determines whether another print job status with the same image forming device ID and a job status of "Printing" is registered in the management table 1000.

[0051] If it is determined in step S904 that another print job status with the same image forming device ID and a job state of "printing" is registered in management table 1000, CPU 121 determines the message ID to be "1" (step S905). The message ID is the ID of a message template for generating a message to be notified to chat application 701. Details of the message template will be described later. Next, the process proceeds to step S911, which will be described later.

[0052] If it is determined in step S904 that another print job status with the same image forming device ID and a job state of "printing" is not registered in the management table 1000, the CPU 121 determines the message ID to be "2" (step S906). Then, the process proceeds to step S911, which will be described later.

[0053] If it is determined in step S903 that the job status acquired in step S902 is "waiting to start printing," CPU 121 determines the message ID to be "3" (step S907). Next, the process proceeds to step S911, which will be described later.

[0054] If it is determined in step S903 that the job status acquired in step S902 is "printing," CPU 121 determines the message ID to be "4" (step S908). Next, the process proceeds to step S911, which will be described later.

[0055] If it is determined in step S903 that the job status acquired in step S902 is "printing completed," CPU 121 determines the message ID to be "5" (step S909). Next, the process proceeds to step S911, which will be described later.

[0056] If it is determined in step S903 that the job status acquired in step S902 is "cancelled," the CPU 121 sets the message ID to "6" (step S910). Next, the CPU 121 determines whether chat information for the print job of the acquired print job status has been registered in the chat information management table 1100 of FIG. 11 (step S911). The chat information management table 1100 is stored in the HDD 124 or the like. The chat information management table 1100 includes a chat management ID 1101, a registration time 1102, a user ID 1103, an image forming device ID 1104, and a job ID 1105. The chat information management table 1100 further includes a job type 1106, a notified message ID 1107, a received button 1108, and a chat status 1109.

[0057] An ID assigned to the chat information when the chat information is registered in the chat information management table 1100 is set in the chat management ID 1101. A time of registration 1102 is set to the time when the chat information is registered in the chat information management table 1100. A user ID 1103 is set to information acquired from the user ID 1002 of the print job status. A image forming apparatus ID 1104 is set to information acquired from the image forming apparatus ID 1003 of the print job status. A job ID 1105 is set to information acquired from the job ID 1004 of the print job status.

[0058] Information acquired from the job type 1006 of the print job status is set in the job type 1106. A message ID determined in any of steps S905 to S910 described above is set in the notified message ID 1107. The type of button event received from the chat application 701 is set in the received button 1108. In this embodiment, the chat server 20 receives, for example, a "print execution button," a "job cancellation button," and a "notification OFF button" as button events. These indicate the types of buttons pressed by the user on the chat screen of the chat application 701. Information indicating the chat status with the chat application 701 regarding the print job is set in the chat status 1109. For example, when a chat with the chat application 701 regarding the print job has ended, "end" indicating this is set in the chat status 1109 corresponding to the print job.

[0059] In step S911, if chat information including the same image forming device ID and job ID as the acquired print job status is registered in the chat information management table 1100, it is determined that the chat information for the print job of the acquired print job status has already been registered in the chat information management table 1100. On the other hand, if chat information including the same image forming device ID and job ID as the acquired print job status is not registered in the chat information management table 1100, it is determined that the chat information for the print job of the acquired print job status has not yet been registered in the chat information management table 1100.

[0060] If it is determined in step S911 that chat information for the print job of the acquired print job status has already been registered in the chat information management table 1100, the process proceeds to step S913 (to be described later). If it is determined in step S911 that chat information for the print job of the acquired print job status has not yet been registered in the chat information management table 1100, the process proceeds to step S912 (to be described later).

[0061] In step S912, CPU 121 registers chat information for the print job of the acquired print job status in chat information management table 1100. Next, CPU 121 executes message notification determination processing (step S913). In the message notification determination processing, if the received button 1108 in the chat information for the print job of the acquired print job status is the "notification OFF button," CPU 121 sets the print job to be notified of messages. On the other hand, if the received button 1108 in the chat information for the print job of the acquired print job status is not the "notification OFF button," CPU 121 sets the print job to be notified of messages. Next, CPU 121 determines whether to notify chat application 701 of a message based on the setting in step S913 (step S914).

[0062] If it is determined in step S914 that the message is not to be notified to chat application 701, the process proceeds to step S918, which will be described later. If it is determined in step S914 that the message is to be notified to chat application 701, the process proceeds to step S915. In step S915, CPU 121 generates chat message data based on the message ID determined in any of steps S905 to S910.

[0063] FIG. 12 shows an example of a message template used to generate chat message data in step S915 of FIG. 9. The message template is a template for generating a message to be sent to the chat application 701. In this embodiment, a different message template is prepared for each message ID, and the content of the message to be sent varies for each message ID. Message ID 1201 corresponds to the message ID determined in any of steps S905 to S910. Message format 1202 is template information that serves as the basis for the message to be sent to the chat application 701. Print job status information is embedded in the brackets (#) and {}. For example, if the message ID is determined to be "1" in step S905 for the print status at the time of occurrence "2021 / 11 / 11 1:11:00" in FIG. 10, a message such as "Reserved print (job ID: 0003, document name: Invoice A) has been accepted. Another user is currently printing, so printing may not be possible for a while" is generated. The chat message data includes such a message.

[0064] The chat message data also includes reply button information 1203, which is information about operation buttons for instructing a reply to the message. The CPU 121 can also acquire the reply button information 1203 from the message template. For example, if the message ID is "1" and the job type is "reserved print," the reply button information will be a "job cancel button," a "print execution button," and a "notification OFF button."

[0065] Furthermore, the chat message data includes the chat management ID 1101 and the image forming device ID 1104 in the chat information management table 1100. Note that, in the present embodiment, the configuration has been described in which the chat server 20 generates chat message data based on the message ID determined in any of steps S905 to S910, but the configuration is not limited to this. For example, the chat server 20 may be configured to transmit the message ID determined in any of steps S905 to S910 to the mobile terminal 40 or 41. The mobile terminal 40 or 41 generates chat message data based on the received message ID and the message template described above.

[0066] Next, CPU 121 determines a destination to which the chat message data is to be sent (step S916). The destination is determined using chat application login user information. The chat application login user information is user information sent from mobile terminal 40 or mobile terminal 41, and is managed by chat application user management module 603.

[0067] Table 1 below is an example of chat application login user information.

[0068] [Table 1]

[0069] The user ID is an ID for identifying the user. The user ID is set to the same ID as the user ID in the print job status. The used terminal ID is an ID for identifying a device equipped with chat application 701 and used by the user, such as mobile terminal 40 or mobile terminal 41. The login status is information indicating whether chat application 701 is running and communication with chat server 20 is possible. "Logged in" in the login status indicates that chat application 701 is running in a device such as mobile terminal 40 or mobile terminal 41 and the device is able to communicate with chat server 20. "Logged out" in the login status indicates that chat application 701 is not running in a device such as mobile terminal 40 or mobile terminal 41 and the device is unable to communicate with chat server 20.

[0070] In step S916, CPU 121 identifies chat application login user information that includes the same user ID as the acquired print job status and whose login state is "logged in." CPU 121 determines the device indicated by the used terminal ID of the identified chat application login user information as the transmission destination.

[0071] Next, CPU 121 sends the chat message data generated in step S915 to the destination determined in step S916 (step S917). Next, CPU 121 determines whether the print job has been completed (step S918). In step S918, if the job state of the acquired print job status is "cancelled" or "printing completed," CPU 121 determines that the print job has been completed. On the other hand, if the job state of the acquired print job status is neither "cancelled" nor "printing completed," CPU 121 determines that the print job has not been completed.

[0072] If it is determined in step S918 that the print job is not to be completed, the process proceeds to step S920, which will be described later. If it is determined in step S918 that the print job is to be completed, the process proceeds to step S919. In step S919, CPU 121 updates chat status 1109 of the chat information corresponding to the acquired print job status in chat information management table 1100 to "completed." Next, CPU 121 determines whether all print job statuses registered in management table 1000 have been processed (step S920).

[0073] If it is determined in step S920 that any of the print job statuses registered in the management table 1000 has not been processed, the process returns to step S902. If it is determined in step S920 that all of the print job statuses registered in the management table 1000 have been processed, the CPU 121 ends this process.

[0074] By the notification control process shown in FIG. 9, a message according to the status of the print job can be sent in real time to the mobile terminal 40 and the mobile terminal 41 used by the user who instructed the execution of the print job.

[0075] 9 is executed when chat server 20 receives the print job status from MFP 10 or MFP 11. However, the timing is not limited to this. For example, the notification control process of FIG. 9 may be executed periodically at predetermined intervals.

[0076] Fig. 13 is a flowchart showing the procedure of button event control processing executed by chat server 20 of Fig. 1. The button event control processing of Fig. 13 is realized by CPU 121 of chat server 20 executing chatbot program 601 stored in ROM 123. The button event control processing of Fig. 13 is executed in parallel with the notification control processing of Fig. 9, for example.

[0077] 13, CPU 121 receives a button event from chat application 701 running on mobile terminal 40 or mobile terminal 41 (step S1301). In this embodiment, as described above, chat server 20 receives, for example, a "print execution button," a "job cancellation button," or a "notification OFF button" as a button event. Next, CPU 121 identifies the pressed button and chat management ID 1101 based on the received button event and information about the sender of the button event (step S1302). Next, CPU 121 determines whether the button identified in step S1302 is the "job cancellation button" (step S1303).

[0078] If it is determined in step S1303 that the button identified in S1302 is not the "job cancel button," the process proceeds to step S1307, which will be described later. If it is determined in step S1303 that the button identified in S1302 is the "job cancel button," CPU 121 executes job cancel button acceptance processing (step S1304). In the job cancel button acceptance processing, CPU 121 notifies the sender of the button event with a message indicating that an instruction to operate the job cancel button has been accepted. Next, CPU 121 adds "cancel button" to the received buttons 1108 of the chat information corresponding to the chat management ID identified in step S1302 in chat information management table 1100 (step S1305). Next, CPU 121 notifies the MFP indicated by image forming device ID 1104 of the chat information corresponding to the chat management ID identified in step S1302 in chat information management table 1100 of the cancellation of the print job indicated by job ID 1105 of the chat information (step S1306) (print job cancellation control means). Next, CPU 121 determines whether the button identified in step S1302 is a "print execution button" (step S1307).

[0079] If it is determined in step S1307 that the button identified in step S1302 is not the "print execute button," the process proceeds to step S1311, which will be described later. If it is determined in step S1307 that the button identified in step S1302 is the "print execute button," CPU 121 executes print execute button acceptance processing (step S1308). In the print execute button acceptance processing, CPU 121 notifies the sender of the button event with a message indicating that an instruction to operate the print execute button has been accepted. Next, CPU 121 adds "print execute button" to the received buttons 1108 of the chat information corresponding to the chat management ID identified in step S1302 in the chat information management table 1100 (step S1309). Next, CPU 121 notifies the MFP indicated by image forming device ID 1104 of the chat information corresponding to the chat management ID identified in step S1302 in chat information management table 1100 of a print instruction for the print job indicated by job ID 1105 of the chat information (step S1310) (print job execution control means). Next, CPU 121 determines whether the button identified in step S1302 is the "notification OFF button" (step S1311).

[0080] If it is determined in step S1311 that the button identified in step S1302 is not the "notification OFF button," the process returns to step S1301. If it is determined in step S1311 that the button identified in step S1302 is the "notification OFF button," CPU 121 executes notification OFF button acceptance processing (step S1312). In the notification OFF button acceptance processing, CPU 121 notifies the sender of the button event with a message indicating that an instruction to operate the notification OFF button has been accepted. Next, CPU 121 adds "notification OFF button" to the received button 1108 of the chat information corresponding to the chat management ID identified in step S1302 in chat information management table 1100 (step S1313). Thereafter, the process returns to step S1301.

[0081] 13, an instruction input by a user by operating mobile terminal 40 or mobile terminal 41 is output to MFP 10 or MFP 11, which executes a print job, via chat server 20. In other words, by operating mobile terminal 40 or mobile terminal 41, the user can instruct MFP 10 or MFP 11 to execute a reserved print job or cancel a print job that is currently being executed. Furthermore, if a message notification regarding a print job is not required, the user can turn off the message notification by operating mobile terminal 40 or mobile terminal 41.

[0082] Next, a description will be given of mobile terminal 40 and the display of a message by mobile terminal 40. In the present embodiment, mobile terminal 40 and mobile terminal 40 display a message in the same procedure, and therefore, as an example, a case where mobile terminal 40 displays a message will be described below.

[0083] Fig. 14 is a flowchart showing the steps of a message display control process executed by mobile terminal 40 of Fig. 1. The message display control process of Fig. 14 is realized by CPU 402 executing a program stored in ROM 403 or the like. Note that in the message display control process of Fig. 14, it is assumed that chat application 701 has already been started on mobile terminal 40.

[0084] 14, CPU 402 performs a login process to log in to chat server 20 (step S1401). Specifically, CPU 402 transmits user information including a user ID indicating the user who owns mobile terminal 40, a terminal ID indicating mobile terminal 40, and a login request to chat server 20. Chat server 20 manages the received user information as shown in Table 1. Next, CPU 402 determines whether chat message data has been received from chat server 20 (step S1402).

[0085] If it is determined in step S1402 that chat message data has not been received from chat server 20, the process proceeds to step S1404, which will be described later. If it is determined in step S1402 that chat message data has been received from chat server 20, CPU 402 updates the screen displayed on operation panel 401 based on the received chat message data (step S1403). Details of the screen displayed on operation panel 401 will be described later. Next, CPU 402 determines whether or not a button displayed on operation panel 401 in step S1403 has been pressed (step S1404).

[0086] If it is determined in step S1404 that a button displayed on operation panel 401 was not pressed in step S1403, the process proceeds to step S1407, which will be described later. If it is determined in step S1404 that a button displayed on operation panel 401 was pressed in step S1403, the process proceeds to step S1405. In step S1405, CPU 402 transmits button information indicating the type of the pressed button and the chat management ID included in the chat message data to chat server 20 as a button event. Next, CPU 402 updates the screen displayed on operation panel 401 to display content corresponding to the type of the pressed button (step S1406). Next, CPU 402 determines whether chat application 701 has terminated (step S1407).

[0087] If it is determined in step S1407 that chat application 701 has not terminated, the process returns to step S1402. If it is determined in step S1407 that chat application 701 has terminated, CPU 402 performs logout processing to log out from chat server 20 (step S1408). Specifically, CPU 402 transmits user information to chat server 20, including a user ID indicating the user who owns mobile terminal 40, a terminal ID indicating mobile terminal 40, and a logout request. Upon receiving this user information, chat server 20 updates the login status corresponding to this user information to "logged out." Then, this process ends.

[0088] Fig. 15 is a sequence diagram showing an example of chat notification performed by the image forming system 1 in Fig. 1. Note that Fig. 15 is based on the assumption that the mobile terminal 40 used by user B is logged in to the chat server 20, and the mobile terminal 41 used by user A is not logged in to the chat server 20.

[0089] 15, user A operates information processing device 31 to submit a reservation print job from information processing device 31 to MFP 10 (step S1501). MFP 10 receives this reservation print job and transmits a print job status in which job status 1007 is "waiting" to chat server 20 (step S1502). Next, user A operates operation unit 111 of MFP 10 to issue a print instruction for the reservation print job submitted in step S1501 (step S1503). Upon receiving this print instruction, MFP 10 starts print processing for the reservation print job submitted in step S1501. MFP 10 also transmits a print job status in which job status 1007 is "printing" to chat server 20 (step S1504).

[0090] Thereafter, user B operates information processing device 30 to submit a reservation print job from information processing device 30 to MFP 10 (step S1505). Having received this reservation print job, MFP 10 transmits a print job status indicating that job status 1007 is "waiting" to chat server 20 because the reservation print job submitted in step S1501 is currently being executed (step S1506). Based on the received print job status, chat server 20 transmits chat message data to chat application 701 of mobile terminal 40 used by user B (step S1507). Having received this chat message data, chat application 701 displays message 1601 (shown in FIG. 16 ) on operation panel 401, indicating that the print job has been accepted but that another user is currently printing (step S1508). Furthermore, based on the button information included in the received chat message data, operation panel 401 displays a button group 1602 including a print execution button, a job cancel button, and a notification OFF button.

[0091] Thereafter, when the print processing of the reservation print job being executed in accordance with user A's print instruction in step S1503 is completed, the process proceeds to step S1509. In step S1509, MFP 10 transmits to chat server 20 a print job status in which job status 1007 indicates "printing completed." Chat server 20, upon receiving this print job status, transmits chat message data to mobile terminal 40 used by user B, including a message indicating that the waiting reservation print job can be executed (step S1510). Chat application 701, upon receiving this chat message data, displays on operation panel 401 a message 1603 indicating that the waiting reservation print job can be executed (step S1511). This allows the user to know that the MFP 10 is in a state where the reservation print job submitted by the user can be executed, even if the user is away from MFP 10. Furthermore, on operation panel 401, a button group 1604 including a print execution button, a job cancel button, and a notification OFF button is displayed based on the button information included in the received chat message data.

[0092] Next, when user B presses the "print execution button" displayed on operation panel 401 of mobile terminal 40, mobile terminal 40 displays message 1605 such as "print execution" on operation panel 401, indicating that the pressed button is the "print execution button." This allows the user to easily know that the pressed button is the "print execution button." Furthermore, chat application 701 of mobile terminal 40 transmits a button event to chat server 20 (step S1512). This button event includes information indicating the pressed "print execution button." Upon receiving this button event, chat server 20 transmits chat message data to mobile terminal 40, including a message indicating that the operation instruction for the print execution button has been accepted (step S1513). Furthermore, chat server 20 instructs MFP 10 to print the reserved print job submitted in step S1505 (step S1514).

[0093] The mobile terminal 40, which has received the chat message data sent from the chat server 20 in step S1513, displays a message 1606 on the operation panel 401 indicating that the operation instruction for the print execution button has been accepted (step S1515).

[0094] Meanwhile, upon receiving the print instruction from chat server 20, MFP 10 starts printing the reserved print job submitted in step S1505. Furthermore, MFP 10 transmits a print job status indicating that job state 1007 is "printing" to chat server 20 (step S1516). Having received this print job status, chat server 20 transmits chat message data including a message indicating that printing is in progress to mobile terminal 40 of user B, who is using chat application 701 (step S1517). Mobile terminal 40, which has received this chat message data, displays message 1607 indicating that printing is in progress on operation panel 401 (step S1518). This allows the user to know that the reserved print job submitted by that user is currently being executed, even if the user is away from MFP 10.

[0095] Thereafter, when the print processing of the reserved print job that was being executed in accordance with the print instruction in step S1514 is completed, the process proceeds to step S1519. In step S1519, MFP 10 transmits to chat server 20 a print job status in which job status 1007 is "printing completed." Chat server 20, which has received this print job status, transmits chat message data including a message indicating that printing has completed to mobile terminal 40 (step S1520). Mobile terminal 40, which has received this chat message data, displays message 1607 indicating that printing has completed on operation panel 401 (step S1521). This allows the user to know that the reserved print job that they submitted has completed, even if they are away from MFP 10.

[0096] As described above, in this embodiment, chat server 20 transmits chat message data for displaying various messages shown in Fig. 16 to mobile terminal 40 that is logged in to chat server 20. On the other hand, chat server 20 does not transmit the chat message data to mobile terminal 41 that is not logged in to chat server 20.

[0097] According to the above-described embodiment, when a reservation print job for user B is submitted to MFP 10 and MFP 10 is currently executing a reservation print job for user A, message 1601 indicating that user B's print job cannot be executed because user A's reservation print job is currently being executed is displayed on operation panel 401 of mobile terminal 40. This allows user B to be informed of the execution status of user B's reservation print job submitted to MFP 10 even if user B is away from MFP 10.

[0098] Furthermore, in the above-described embodiment, when user B presses the print execution button in response to message 1603 displayed on operation panel 401 of mobile terminal 40, the reserved print job of user B that has been submitted to MFP 10 is executed by MFP 10. As a result, even if user B is away from MFP 10, an instruction to execute the reserved print job of user B that has been submitted to MFP 10 can be issued.

[0099] In the above-described embodiment, for each print job submitted from an external device to MFP 10, it is controlled whether or not to display a message on the operation panel of a device such as mobile terminal 40 or mobile terminal 41. This allows the message display function to reflect the user's intention for each print job submitted to MFP 10, thereby making it easier to use the message display function.

[0100] Fig. 17 is a sequence diagram showing another example of chat notification performed by the image forming system 1 of Fig. 1. Note that Fig. 17 is based on the premise that the mobile terminal 40 used by user B and the mobile terminal 41 used by user A are logged in to the chat server 20. In the following, the reference numerals of the components of mobile terminal 40 with an ' suffix attached are referred to as the components of mobile terminal 41.

[0101] 17, user A operates information processing device 31 to submit a reservation print job from information processing device 31 to MFP 10 (step S1701). MFP 10 receives this reservation print job and transmits a print job status in which job state 1007 is "waiting" to chat server 20 (step S1702). Chat server 20 receives this print job status and transmits chat message data including a message indicating that the job is waiting and printing can be performed to mobile terminal 41 used by user A (step S1703). Mobile terminal 41 receives this chat message data and displays message 1801 of FIG. 18(a) indicating that the job is waiting and printing can be performed on operation panel 401' of mobile terminal 41 (step S1704). Furthermore, operation panel 401' displays a button group 1802 including a print execution button, a job cancel button, and a notification OFF button based on button information included in the received chat message data. Next, when user A presses the "notification OFF button" displayed on operation panel 401', mobile terminal 41 displays message 1803 such as "notification OFF" on operation panel 401', indicating that the pressed button is the "notification OFF button." In addition, chat application 701' of mobile terminal 41 transmits a button event to chat server 20 (step S1705). This button event includes information indicating the "notification OFF button" pressed by user A.

[0102] Upon receiving this button event, the chat server 20 sets the chat notification function for the mobile terminal 41 to OFF and transmits chat message data including a message to that effect to the mobile terminal 41 (step S1706). The mobile terminal 41, which has received this chat message data, displays a message 1804 indicating that the chat notification function has been set to OFF on the operation panel 401′ (step S1707). Thereafter, user A operates the operation unit 111 of the MFP 10 to issue a print instruction for the reserved print job submitted in step S1701 (step S1708). The MFP 10, which has received this print instruction, begins printing the reserved print job submitted in step S1701. The MFP 10 also transmits a print job status indicating that the job status 1007 is “printing” to the chat server 20 (step S1709). Note that, because the chat notification function for the mobile terminal 41 has been set to OFF as described above, the chat server 20 does not transmit chat message data to the mobile terminal 41 as a response to the received print job status. In this manner, in this embodiment, a user can set the chat notification function to OFF from a mobile terminal that is logged in to chat server 20.

[0103] Thereafter, user B operates information processing device 30 to submit a reservation print job from information processing device 30 to MFP 10 (step S1710). Having received this reservation print job, MFP 10 transmits a print job status indicating that job status 1007 is "waiting" to chat server 20 because the reservation print job submitted in step S1701 is currently being executed (step S1711). Based on the received print job status, chat server 20 transmits chat message data to chat application 701 of mobile terminal 40 used by user B (step S1712). Having received this chat message data, mobile terminal 40 displays message 1805 of FIG. 18(b) on operation panel 401, indicating that the print job has been accepted but that another user is currently printing (step S1713). Furthermore, based on the button information included in the received chat message data, operation panel 401 displays a button group 1806 including a print execution button, a job cancel button, and a notification OFF button.

[0104] Thereafter, when user B presses the "job cancel button" displayed on operation panel 401, mobile terminal 40 displays message 1807 on operation panel 401. Message 1807 is a message such as "job cancel," indicating that the pressed button is the "job cancel button." Furthermore, chat application 701 of mobile terminal 40 transmits a button event to chat server 20 (step S1714). This button event includes information indicating that the "job cancel button" was pressed by user B. Upon receiving this button event, chat server 20 transmits chat message data including a message indicating that the operation instruction for the "job cancel button" has been accepted to mobile terminal 40 (step S1715). Furthermore, chat server 20 instructs MFP 10 to cancel the reserved print job submitted in step S1710 (step S1716).

[0105] The mobile terminal 40, which has received the chat message data sent from the chat server 20 in step S1715, displays a message 1808 on the operation panel 401 indicating that the operation instruction for the "job cancel button" has been accepted (step S1717).

[0106] Meanwhile, upon receiving the cancellation instruction from chat server 20, MFP 10 performs a cancellation process for the reserved print job submitted in step S1710. As described above, in this embodiment, a user can not only check the execution status of a print job from a mobile terminal logged in to chat server 20, but also issue a cancellation instruction for the print job. Furthermore, MFP 10 transmits a print job status in which job status 1007 is "cancelled" to chat server 20 (step S1718). Upon receiving this print job status, chat server 20 transmits chat message data to user B's mobile terminal 40 (step S1719). This chat message data includes a message indicating that the reserved print job submitted in step S1710 has been canceled.

[0107] Upon receiving this chat message data, mobile terminal 40 displays message 1809 on operation panel 401 indicating that the reserved print job submitted in step S1710 has been canceled (step S1720). This allows the user to easily confirm that a cancellation instruction has been received from the mobile terminal logged in to chat server 20.

[0108] Thereafter, when the print processing of the reserved print job that was being executed in accordance with the print instruction from user A in step S1708 is completed, the process proceeds to step S1721. In step S1721, MFP 10 transmits a print job status in which job status 1007 is "printing completed" to chat server 20. Thereafter, this process ends.

[0109] Although the present invention has been described using the above-mentioned embodiment, the present invention is not limited to the above-mentioned embodiment. For example, in the message notification determination process of step S913, it is also possible to control whether or not to notify the chat application 701 of a message based on information other than the received button 1108 (other than the operation button) of the chat information.

[0110] Fig. 19 is a flowchart showing another procedure of the message notification determination process of step S913 in Fig. 9. The message notification determination process of Fig. 19 is realized by the CPU 121 of the chat server 20 executing the chatbot program 601 stored in the ROM 123.

[0111] 19, CPU 121 determines whether the notification OFF button has been pressed in the chat for the print job of the acquired print job status (step S1901). In step S1901, for example, if the received button 1108 of the chat information for the print job is the "notification OFF button," CPU 121 determines that the notification OFF button has been pressed in the chat for the print job. On the other hand, if the received button 1108 of the chat information for the print job is not the "notification OFF button," CPU 121 determines that the notification OFF button has not been pressed in the chat for the print job.

[0112] If it is determined in step S1901 that the notification OFF button has been pressed in the chat for the print job, CPU 121 sets the print job as not a message notification target (step S1902), and ends this process.

[0113] If it is determined in step S1901 that the notification OFF button has not been pressed in the chat for the print job, the process proceeds to step S1903. In step S1903, CPU 121 determines whether the chat for the print job has ended based on the chat status in the chat information.

[0114] If it is determined in step S1903 that the chat for the print job has ended, the process proceeds to step S1902, which prevents repeated notification of messages for print jobs whose printing process has already been completed.

[0115] If it is determined in step S1903 that the chat for the print job has not ended, CPU 121 determines whether the user who submitted the print job is currently logged in to the MFP to which the print job was submitted (step S1904). In this embodiment, MFP user management module 607 manages the login status of users for each MFP, as shown in Table 2 below. CPU 121 makes the determination in step S1904 based on this information.

[0116] [Table 2]

[0117] If it is determined in step S1904 that the user who submitted the print job is currently logged in to the MFP to which the print job was submitted, the process proceeds to step S1902. Here, the user who is logged in to the MFP to which the print job was submitted can grasp the status of the print job from the operation unit of the MFP, so there is no need to notify the mobile terminal used by such a user of a chat message as described above. In contrast, in this embodiment, if it is determined that the user who submitted the print job is currently logged in to the MFP to which the print job was submitted, a setting is made to indicate that the user is not a target for message notifications. This makes it possible to prevent unnecessary messages from being sent to the mobile terminal used by the user when the user is logged in to the MFP to which the print job was submitted.

[0118] If it is determined in step S1904 that the user who submitted the print job is not currently logged in to the MFP to which the print job was submitted, the process proceeds to step S1905. In step S1905, CPU 121 determines whether another print job submitted by the user who submitted the print job before the print job is incomplete. Note that in FIG. 19, the other print job is referred to as a "preceding job." In step S1905, for example, if a print job status other than "Print Completed" is registered in management table 1000 with the same user ID and image forming device ID as the print job, and whose job reception time is earlier than the print job, the other print job submitted by the user who submitted the print job before the print job is determined to be incomplete. On the other hand, if a print job status matching this condition is not registered in management table 1000, the other print job submitted by the user who submitted the print job before the print job is determined to be not incomplete.

[0119] If it is determined in step S1905 that another print job submitted by the user who submitted the print job before the print job is incomplete, processing proceeds to step S1902. Here, for example, for a user who has received a message via chat informing them that another user is currently printing a previously submitted print job, they do not need to receive a similar message for a print job submitted after the previously submitted print job. In contrast, in this embodiment, if another print job submitted by the user who submitted the print job before the currently submitted print job is incomplete, it is set to not be subject to message notifications. This makes it possible to prevent excessive message notifications via chat.

[0120] If it is determined in step S1905 that another print job submitted by the user who submitted the print job before the print job is not incomplete, the process proceeds to step S1906. In step S1906, CPU 121 determines whether the time elapsed since the reception time of the print job is within a predetermined time. Specifically, CPU 121 determines whether the time elapsed since the job reception time of the acquired print job status is within a predetermined time.

[0121] In step S1906, if the elapsed time since the reception of the print job is within a predetermined time, the process proceeds to step S1902. For example, a user who is in a hurry to print will go to the destination MFP immediately after submitting the print job to directly check the status of the MFP in order to receive the printed matter immediately, and therefore is highly likely not to check the chat message. In fact, there is a concern that such a user would feel annoyed if the chat message was notified immediately after the reception of the print job. In contrast, in this embodiment, if the elapsed time since the reception of the print job is within a predetermined time, a setting is made to indicate that the user is not subject to message notification. This makes it possible to prevent excessive chat message notifications.

[0122] In step S1906, if the elapsed time since the reception time of the print job is not within the predetermined time, the process proceeds to step S1907. In step S1907, CPU 121 determines whether the reserved print job is being executed in accordance with a print instruction issued by a means other than the above-mentioned print execution button. Note that in this embodiment, whether the print instruction is the pressing of the print execution button is determined by the fact that the received buttons in the chat information include "print execution button."

[0123] In step S1907, if a reserved print job is being executed in accordance with a print instruction issued by a means other than the print execution button described above, this means that the user has issued a print instruction directly from the operation unit 111 of the MFP main body. In such a case, the process proceeds to step S1902. This makes it possible to prevent unnecessary notifications via chat from being sent to users who are close enough to the MFP to operate it directly.

[0124] In step S1907, if the reserved print job is not being executed in accordance with a print instruction by means other than the print execution button described above, the process proceeds to step S1908. In step S1908, CPU 121 determines whether the message to be notified is a message that has already been notified to chat application 701. Specifically, CPU 121 determines whether the message ID determined in any of steps S905 to S910 described above is included in the chat information. If the determined message ID is included in the chat information, it is determined that the message to be notified is a message that has already been notified to chat application 701. On the other hand, if the determined message ID is not included in the chat information, it is determined that the message to be notified is not a message that has already been notified to chat application 701.

[0125] In step S1908, if the message to be notified is a message that has already been notified to the chat application 701, the process proceeds to step S1902, which makes it possible to prevent the user from being notified of a message with the same content.

[0126] If it is determined in step S1908 that the message to be notified is not a message that has already been notified to the chat application 701, the CPU 121 sets the message to be notified (step S1909), and ends this process.

[0127] In this way, the message notification determination process of FIG. 19 described above makes it possible to reduce unnecessary notifications via chat.

[0128] Furthermore, in the above-described embodiment, the configuration may be such that an administrator or a user can set whether or not to perform the determinations in steps S1904 to S1908.

[0129] Fig. 20 is a diagram showing an example of a setting screen for setting whether or not to perform the determinations in steps S1904 to S1908 in Fig. 19. The setting screen in Fig. 20 is made up of check boxes 2001 to 2005.

[0130] Checkbox 2001 is a checkbox for switching between enabling and disabling the determination in step S1904. If the checkbox is not checked, the determination in step S1904 is made in the message notification determination process of Fig. 19. On the other hand, if the checkbox is checked, the determination in step S1904 is not made in the message notification determination process of Fig. 19, and the process proceeds to step S1905.

[0131] Check box 2002 is a check box for switching between enabling and disabling the determination in step S1905. If the check box is not checked, the determination in step S1905 is made in the message notification determination process of Fig. 19. On the other hand, if the check box is checked, the determination in step S1905 is not made in the message notification determination process of Fig. 19, and the process proceeds to step S1906 regardless of the status of other print jobs.

[0132] Check box 2003 is a check box for switching between enabling and disabling the determination in step S1906. If the check box is not checked, the determination in step S1906 is made in the message notification determination process of Fig. 19. On the other hand, if the check box is checked, the determination in step S1906 is not made in the message notification determination process of Fig. 19, and the process proceeds to step S1907 regardless of the time that has elapsed since the print job was submitted.

[0133] Check box 2004 is a check box for switching between enabling and disabling the determination in step S1907. If the check box is not checked, the determination in step S1907 is made in the message notification determination process of Fig. 19. On the other hand, if the check box is checked, the determination in step S1907 is not made in the message notification determination process of Fig. 19, and the process proceeds to step S1908 regardless of whether the print execution button on the MFP main body is pressed or not.

[0134] Checkbox 2005 is a checkbox for switching between enabling and disabling the determination in step S1908. If the checkbox is not checked, the determination in step S1908 is made in the message notification determination process of Fig. 19. On the other hand, if the checkbox is checked, the determination in step S1908 is not made in the message notification determination process of Fig. 19, and the process proceeds to step S1909 regardless of whether the message has already been notified.

[0135] In this way, by configuring the system so that the user can set whether or not to perform the determinations in steps S1904 to S1908, the user can set chat notification settings that are suited to the usage environment.

[0136] The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. It can also be realized by a circuit (e.g., ASIC) that realizes one or more functions. [Explanation of symbols]

[0137] 10 MFP 11 MFP 20 Chat Server 40 Mobile Devices 41 Mobile devices 121 CPU 401 Operation Panel

Claims

1. A server device that notifies an application of a communication terminal of information about a print job executed by an image forming device, an acquisition unit that acquires status information of a print job input to the image forming apparatus from an external device; a control means for displaying a predetermined message on a display unit of the communication terminal based on the status information; The control means When a print job is input from an external device to the image forming device and the image forming device is currently executing another print job different from the first print job, a message is displayed on a display unit of the communication terminal indicating that the first print job cannot be executed because the other print job is currently being executed; A server device, characterized in that, when a user operating the communication terminal is logged in to the image forming apparatus, the server device controls so that the predetermined message is not displayed on a display unit of the communication terminal.

2. 2. The server device according to claim 1, wherein the predetermined message includes a message indicating that a print job input from an external device to the image forming device is in a state where it can be executed.

3. 3. The server device according to claim 1, wherein the predetermined message includes a message indicating that a print job input from an external device to the image forming device is currently being executed.

4. 4. The server device according to claim 1, wherein the predetermined message includes a message indicating that a print job input from an external device to the image forming device has been completed.

5. 5. The server device according to claim 1, wherein the predetermined message includes a message indicating that a print job input from an external device to the image forming device has been canceled.

6. A server device as described in any one of claims 1 to 5, further comprising a print job cancellation control means for causing the image forming device to cancel a print job submitted to the image forming device from an external device in accordance with instructions input by a user into the communication terminal in response to a message displayed on the display unit of the communication terminal.

7. A server device as described in any one of claims 1 to 6, further comprising a print job execution control means for causing the image forming device to execute a reserved print job submitted to the image forming device from an external device in accordance with instructions input by a user into the communication terminal in response to a message displayed on the display unit of the communication terminal.

8. The server device according to any one of claims 1 to 7, characterized in that the control means controls whether or not the specified message is displayed on the display unit of the communication terminal for each print job submitted to the image forming device from an external device.

9. 9. The server device according to claim 1, wherein the control means controls the communication terminal so that the predetermined message is not displayed on the display unit of the communication terminal in accordance with an instruction input by a user to the communication terminal.

10. 10. The server device according to claim 1, wherein the control means causes a chat message to be displayed on a display unit of the communication terminal.

11. 11. The server device according to claim 10, wherein the control means controls the communication terminal so that the predetermined message is not displayed on the display unit of the communication terminal when the chat with the communication terminal is ended.

12. The server device according to any one of claims 1 to 11, characterized in that the control means controls the communication terminal not to display the specified message on its display unit if another print job submitted before the print job submitted by the user who submitted the print job to the image forming device is incomplete.

13. The server device according to any one of claims 1 to 12, characterized in that the control means controls the display unit of the communication terminal not to display the specified message until a specified time has elapsed from the time of reception of the print job submitted to the image forming device.

14. a display unit of the communication terminal displays operation buttons for receiving an instruction to execute a print job input to the image forming apparatus; A server device as described in any one of claims 1 to 13, characterized in that the control means controls the communication terminal so that the specified message is not displayed on the display unit when a print job submitted to the image forming device is executed in accordance with instructions from a means other than the operation button.

15. 15. The server device according to claim 1, wherein the control means controls the communication terminal so that the same message is not displayed on the display unit of the communication terminal.

16. 1. A method for controlling a server device that notifies an application of a communication terminal of information about a print job executed by an image forming device, comprising: an acquisition step of acquiring status information of a print job input to the image forming apparatus from an external device; a control step of displaying a predetermined message on a display unit of the communication terminal based on the status information; The control step includes: When a print job is input from an external device to the image forming device and the image forming device is currently executing another print job different from the first print job, a message is displayed on a display unit of the communication terminal indicating that the first print job cannot be executed because the other print job is currently being executed; A control method for a server device, comprising: controlling the communication terminal so that the predetermined message is not displayed on a display unit of the communication terminal when a user operating the communication terminal is logged in to the image forming apparatus.

17. A program for causing a computer to execute each means of the server device according to any one of claims 1 to 15.

Images