Information processing device and control method thereof

Abstract

To reduce time and effort for printing an image based on image data received via fax by an image processing apparatus when there is a situation where a user is highly likely to immediately receive a print and a situation where the user cannot receive the print.SOLUTION: An image processing apparatus of the present invention has: receiving means that receives image data via fax; acquisition means that acquires status information indicating the state of a user from a chat service; and printing means that prints an image based on the received image data on a recording medium. The acquisition means acquires the status information on the user corresponding to information on a transmission source of the received image data. The printing means prints the image based on the received image data on the recording medium on the basis of acquisition of specific status information by the acquisition means, without the image processing apparatus receiving a print instruction from the user after the acquisition of the status information by the acquisition means.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] The present invention relates to an information processing device and a control method thereof. [Background technology]

[0002] There is a technology in which an image processing device transmits received images to a cloud server that provides cloud storage services, chat services, etc. Patent Document 1 describes a technology that allows a user to set whether a document received by fax is to be printed as is or saved in a "fax inbox" without being printed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-15663 Summary of the Invention [Problem to be solved by the invention]

[0004] It is preferable that the printing of an image based on image data received by fax is carried out in a situation where the user who is to receive the printed matter can receive the printed matter immediately.

[0005] In the case of the image processing device of Patent Document 1, whether or not the image processing device prints documents received by fax must be set by the user on an operation unit of the image processing device. Therefore, for example, if a user frequently alternates between going to the office and working from home and wants printed materials to be printed only when they are in the office (when there is a high possibility of receiving printed materials), they must change this setting every time, which is time-consuming.

[0006] The present invention has been made to solve the above-mentioned problems, and aims to reduce the effort required for an image processing device to print an image based on image data received by fax in situations where there are situations where the user is likely to receive the printed material immediately and situations where the user is not likely to receive the printed material immediately. [Means for solving the problem]

[0007] In order to solve the above problems, the image processing apparatus of the present invention includes a receiving unit for receiving image data by FAX and a chat server. B and a printing means for printing an image based on the received image data onto a recording medium, wherein the acquiring means acquires the status information of the user corresponding to the sender information of the received image data, and the printing means prints an image based on the image data received from the image processing device in response to a print instruction from the user after the acquiring means acquires the status information, based on the acquisition of specific status information by the acquiring means. need The present invention is characterized in that an image based on the received image data is printed on a recording medium without requiring a printer to print the image. [Effects of the Invention]

[0008] In cases where there are situations where the user is likely to receive the printed matter immediately and situations where the user is not likely to receive the printed matter immediately, it is possible to reduce the effort required for the image processing device to print an image based on image data received by fax. [Brief explanation of the drawings]

[0009] [Figure 1] A diagram showing an example of the overall configuration of a message application service [Figure 2] A diagram showing an example of the hardware configuration of an MFP10 [Figure 3] FIG. 1 shows an example of the hardware configuration of a user terminal 20. [Figure 4] FIG. 1 is a diagram showing an example of a hardware configuration of a message application server 30. [Figure 5] FIG. 1 is a diagram showing an example of the hardware configuration of a tenant server 40. [Figure 6] FIG. 6 is a diagram showing an example of tenant information 601. [Figure 7] FIG. 7 is a diagram showing an example of a status table 701. [Figure 8]FIG. 8 shows an example of a status table setting screen 810 for setting the status table 701. [Figure 9] FIG. 9 shows an example of a recipient user table 901. [Figure 10] FIG. 9 is a diagram showing an example of a screen for setting a recipient user table 901. [Figure 11] FIG. 10 is a diagram showing an example of a sequence for setting the recipient user table 901. [Figure 12] Flowchart showing an example of a setting process for the recipient user table 901 [Figure 13] FIG. 7 is a diagram showing an example of a sequence for storing a FAX job based on the status table 701. [Figure 14] FIG. 10 is a diagram showing an example of a sequence for printing an image based on image data stored in accordance with a change in the stator; [Figure 15] FIG. 15 shows an example of a chat screen 1500 of a message application. [Figure 16] A flowchart showing an example of processing a fax job received by the MFP 10. DETAILED DESCRIPTION OF THE INVENTION

[0010] The following describes in detail the embodiments of the present invention with reference to the drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention.

[0011] In this embodiment, a multifunction peripheral (MFP) having print, scan, and fax functions will be described as an example of an image processing device. Note that the image processing device in this embodiment is not limited to an MFP, and may be any device that can realize this embodiment, such as a device without a scan function or a device that sends a print instruction to an image forming device having a printing unit.

[0012] Furthermore, although the present embodiment has been described using a fax reception job as an example, the present invention is not limited to this and can also be applied to print jobs other than fax.

[0013] <Example> An embodiment of the present invention will now be described.

[0014] 1 is a diagram illustrating an example of the overall configuration of a message application service. The message application service is an example of a cloud service, and is also a chat service. The cloud service in this embodiment is not limited to the message application service, and may be, for example, a cloud-based service such as email, storage, or information management service.

[0015] The message application service is configured, for example, from an MFP 10, which is an image processing device, a user terminal 20, a message application server 30, and a tenant server 40. The MFP 10, the user terminal 20, and each server are connected via a network 70 and can communicate with each other. The network 70 is a wireless or wired network configured from the Internet, a WAN, a LAN, or the like. The MFP 10 is also connected to a public switched telephone network (PSTN) 80 and is capable of controlling facsimile communication protocols, etc.

[0016] The MFP 10 has the function of receiving image data and the ability to print an image based on the image data on a recording medium. The MFP 10 can receive image data from, for example, a network 70 such as the Internet or a public switched telephone network 80. The MFP 10 in this embodiment also refers to an image processing device that communicates with a message application server 30 via the network 70 and transmits and receives image data. In this manner, the MFP 10 can receive image data from the message application server 30 and print an image based on the received image data. The MFP 10 can also scan an original document, generate image data based on the scanned original document image, and transmit the generated image data based on the scanned original document image to the message application server 30. Note that the data transmitted and received by the MFP 10 is not limited to image data; the MFP 10 can transmit and receive various data and signals, such as signals used to control facsimile communication protocols. While FIG. 1 illustrates an example in which two MFPs 10 are connected, any number of connections are possible.

[0017] The user terminal 20 is an example of an information terminal, such as a smartphone, tablet terminal, or personal computer, that a user uses to use a message application service. While FIG. 1 shows an example in which three user terminals 20 are connected, any number of connections may be used. A user operates the user terminal 20 to access the message application server 30 on the cloud 60, exchange messages with other users, and use installed applications. The user terminal 20 and the message application server 30 are connected to a wired or wireless communication network, and are capable of transmitting and receiving data between them. In this embodiment, the Internet is assumed as an example of a communication network, but a dedicated line may also be used.

[0018] The message application server 30 is a cloud server located on the cloud 60, and is a server that provides services using a message application 306. The message application server 30 executes all processes related to message exchange, such as sending and receiving messages to and from the user terminal 20, and displaying a message sending and receiving screen.

[0019] The tenant server 40 is a cloud server arranged on the cloud 60, and is a server that stores and provides information about each tenant. Details of the tenant information stored in the tenant server 40 will be explained in the section describing FIG. 6.

[0020] The message application server 30 may substitute for the capabilities of the tenant server 40, which will be described later, and for part or all of the processing performed by the tenant server 40. In this case, the tenant server 40 is no longer essential in this configuration.

[0021] 2 is a diagram showing an example of the hardware configuration of MFP 10. MFP 10 is mainly composed of a control unit 110, an operation unit 116, a reading unit 118, a printing unit 120, a wireless communication unit 122, a FAX communication unit 124, and a communication unit 126. The control unit 110 is composed of a CPU 111, a ROM 112, a RAM 113, an HDD 114, and various I / Fs (interfaces). CPU stands for Central Processing Unit, ROM stands for Read-Only Memory, and RAM stands for Random Access Memory. The various I / Fs are an operation unit I / F 115, a reading unit I / F 117, a printing unit I / F 119, a wireless communication unit I / F 121, a FAX unit I / F 123, and a communication unit I / F 125.

[0022] The operation unit I / F 115 is a connection unit between the control unit 110 and the operation unit 116, and connects the control unit 110 and the operation unit 116. The reading unit I / F 117 is a connection unit between the control unit 110 and the reading unit 118, and connects the control unit 110 and the reading unit 118. The printing unit I / F 119 is a connection unit between the control unit 110 and the printing unit 120, and connects the control unit 110 and the printing unit 120. The wireless communication unit I / F 121 is a connection unit between the control unit 110 and the wireless communication unit 122, and connects the control unit 110 and the wireless communication unit 122. The FAX unit I / F 123 is a connection unit between the control unit 110 and the FAX communication unit 124, and connects the control unit 110 and the FAX communication unit 124. The communication unit I / F 125 is a connection unit between the control unit 110 and the communication unit 126, and connects the control unit 110 and the communication unit 126.

[0023] The control unit 110 including the CPU 111 controls the overall operation of the MFP 10. The CPU 111 loads a control program stored in the ROM 112 or the HDD 114 into the RAM 113 to perform various types of control, such as reading control and printing control. The ROM 112 stores control programs executable by the CPU 111. The ROM 112 also stores a boot program, font data, and the like. The RAM 113 is the main memory of the CPU 111 and is used as a work area and a temporary storage area for loading the various control programs stored in the ROM 112 and the HDD 114. The HDD 114 stores, for example, image data, print data, various programs, various addresses, and various setting information. The HDD 114 is a storage medium and is not limited to an HDD, but may be a flash memory, an SSD (Solid State Drive), an eMMC (Embedded Multi Media Card), or the like.

[0024] In the MFP 10 of this embodiment, one CPU 111 executes each process shown in the flowcharts described below using one memory (RAM 113), but this is not limited to this. For example, each process can be executed by multiple CPUs, RAMs, ROMs, and HDDs working together. Also, some processes can be executed using hardware circuits such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0025] The operation unit 116 has a display unit such as a touch panel and hard keys, and displays information to the user and accepts input from the user. User inputs include, for example, input of instructions to cause the MFP 10 to execute a desired process, input of characters and symbols to the MFP 10, and operation inputs for the user to view information. An instruction input to cause the MFP 10 to execute a desired process includes, for example, input of instructions to cause the MFP 10 to execute each process executable by the MFP 10, such as a print instruction. An operation input for the user to view information includes, for example, input for selecting a file or changing the display size to view data stored in the HDD 114. The input method for the touch panel may be any common detection method, such as a resistive film method, an infrared method, an electromagnetic induction method, or a capacitive method. The hard keys may be, for example, a keyboard with letters and numbers written on it, or physical buttons for issuing commands such as "Start" or "Reset." Furthermore, for example, a toggle switch, a rocker switch, a push button switch, a rotary switch, a slide switch, a key lock switch, a tactile switch, etc. may also be used.

[0026] The reading unit 118 is, for example, a scanner, which reads the document by moving the document or a sensor, and generates image data such as binary data based on the image of the read document. The image data generated by the reading unit 118 is transmitted to an external device such as an information processing device, stored in an external recording device such as a USB device, or printed on recording paper, for example.

[0027] Printing unit 120 receives image data to be printed (image data to be printed) from CPU 111 and prints the image on recording paper fed from a paper feed cassette (not shown). Note that the operation of printing unit 120 is not limited to printing on paper, and may also be on media other than paper, such as overhead projector sheets.

[0028] The wireless communication unit 122 wirelessly connects the control unit 110 to an external wireless device. The user terminal 20 is an example of a wireless device that can be connected to the MFP 10.

[0029] The FAX communication unit 124 has, for example, a modem and an NCU for facsimile communication, and controls these to connect to the public switched telephone network 80 and control the facsimile communication protocol.

[0030] The communication unit 126 transmits image data and various information stored in the MFP 10 to external devices connected to the network 70, and receives print data and various information from information processing devices connected to the network 70. The various information includes, for example, status information and setting information. Transmission and reception via the network 70 can be performed using, for example, electronic mail (E-mail) or file transmission using other protocols (for example, FTP, SMB, WEBDAV, etc.). Image data and message data can also be transmitted and received over the network 70 by accessing via HTTP communication from the user terminal 20 or the message application server 30. Furthermore, a user can access the MFP 10 from a web browser on the user terminal 20 via the network 70 and configure various settings of the MFP 10 (remote UI function).

[0031] 3 is a diagram showing an example of the hardware configuration of the user terminal 20. Note that the user terminal 20 in this embodiment is assumed to be a device such as a smartphone or a tablet PC, but the user terminal 20 is not limited to these. For example, the user terminal 20 may be any other information processing device that can connect to the network 70 via a wired connection using Ethernet (registered trademark) or a wireless connection using radio waves such as Wi-Fi communication. Note that the wireless connection method is not limited to Wi-Fi communication, and any method that allows communication, such as Bluetooth (registered trademark), may be used.

[0032] The user terminal 20 mainly comprises an operation panel 201, a camera 204, an NFC communication unit 205, a Bluetooth communication unit 206, a CPU 207, a ROM 208, a RAM 209, an HDD 210, and a wireless LAN communication unit 211. NFC is an abbreviation for Near Field Communication, and LAN is an abbreviation for Local Area Network.

[0033] The CPU 207 reads out control programs stored in the ROM 208 or the HDD 210 and executes various processes for controlling the operation of the user terminal 20. The ROM 208 stores control programs executable by the CPU 207. The RAM 209 is the main storage memory of the CPU 207, and is used as a work area and a temporary storage area for expanding the various control programs stored in the ROM 208 and the HDD 210.

[0034] The HDD 210 stores, for example, image data, print data, various programs, various application programs, various addresses, and various setting information. The HDD 305 is a storage medium and is not limited to an HDD, but may be a flash memory, an SSD, an eMMC, or the like.

[0035] In the user terminal 20 of this embodiment, one CPU 207 executes each process shown in the flowcharts described below using one memory (RAM 209), but this is not limited to this. For example, each process can be executed by multiple CPUs, RAMs, ROMs, and HDDs working together. Furthermore, some processes may be executed using hardware circuits such as ASICs and FPGAs. The operation panel 201 has a touch panel function capable of detecting a user's touch operation and displays various screens provided by an OS (Operating System) or applications. The operation panel 201 is also used to check information stored in the message application server 30. A user can input desired operation instructions to the user terminal 20 by inputting a touch operation on the operation panel 201. The user terminal 20 is equipped with hardware keys (not shown), and the user can input operation instructions to the user terminal 20 using these hardware keys. The detection method for detecting a user's touch operation on the touch panel may be any common detection method, such as a resistive film method, an infrared method, an electromagnetic induction method, or a capacitive method. Alternatively, software keys may be displayed on the touch panel, and operation instructions may be input by user operation on the touch panel. The OS may be any OS, such as Windows, macOS, Unix, Linux, Android, or iOS. The application may be any application that performs functions such as sending email, browsing, chatting, taking pictures with a camera, displaying images, and setting settings.

[0036] The camera 204 captures an image in response to a user's imaging instruction. The image captured by the camera 204 is stored in a predetermined area of ​​the HDD 210. It is also possible to acquire information from a QR code read by the camera 204 by storing a program capable of analyzing QR codes in the ROM 208 or the HDD 210 in advance, or by installing an application that performs the same function. Note that information acquisition is not limited to QR codes, and may be performed by analyzing one-dimensional codes such as barcodes, or two-dimensional codes such as DataMatrix, MaxiCode, PDF417, and Aztec.

[0037] The user terminal 20 can connect to and send and receive data with various wireless devices via the NFC communication unit 205, the Bluetooth communication unit 206, and the wireless LAN communication unit 211. The Bluetooth communication unit 206 of the user terminal 20 may be compatible with the Bluetooth Low Energy standard or the Bluetooth Classic standard.

[0038] Although the user terminal 20 in this embodiment is connected to the network wirelessly, it may be connected to the network in a wired manner by attaching a wired port (not shown), for example.

[0039] 4 is a diagram showing an example of the hardware configuration of the message application server 30. The message application server 30 is a chat server that provides a chat service.

[0040] The message application server 30 mainly comprises a CPU 301 , a ROM 302 , a RAM 303 , a communication unit 304 , and a HDD 305 .

[0041] The CPU 301 reads out the control program stored in the ROM 302 and the message application 306 stored in the HDD 305, expands them in the RAM 303, and executes various processes for controlling the operation of the message application server 30. The ROM 302 stores control programs executable by the CPU 301. The RAM 303 is the main storage memory of the CPU 301, and is used as a work area and a temporary storage area for expanding the various control programs stored in the ROM 302 and the HDD 305.

[0042] The HDD 305 stores various data such as messages, image data, channel information, application programs, etc. The HDD 305 is a storage medium, and is not limited to an HDD, but may be a flash memory, an SSD, an eMMC, or the like.

[0043] In the message application server 30 of this embodiment, one CPU 301 executes each process shown in the flowcharts described below using one memory (RAM 303), but this is not limited to this. For example, each process can be executed by multiple CPUs, RAMs, ROMs, and HDDs working together. Also, some processes can be executed using hardware circuits such as ASICs and FPGAs.

[0044] The message application 306 is an application installed in the HDD 305 and runs on the CPU 301 or the RAM 303 .

[0045] The communication unit 304 is used for communication with other devices, and can transmit and receive data to and from various devices, such as the user terminal 20 and the MFP 10, via the communication unit 304. The communication unit 304 may perform wired communication using Ethernet or wireless communication such as Wi-Fi. An example of the operation of the message application server 30 when a message is posted using the user terminal 20 will be described. The CPU 301 loads a message application 306 read from the HDD 305 into the RAM 303, and receives a posted message sent from the user terminal 20 via the communication unit 304 under the control of the message application 306. The posted message received from the user terminal 20 is then stored in the HDD 305. If necessary, the communication unit 304 can notify the user terminal 20 or another user terminal 20 that a message has been posted via the network 70. The user terminal 20, upon receiving the notification, displays the message on the touch-panel type operation panel 201.

[0046] FIG. 5 is a diagram illustrating an example of the hardware configuration of the tenant server 40. As shown in FIG.

[0047] The tenant server 40 mainly includes a CPU 401 , a ROM 402 , a RAM 403 , a communication unit 404 , and an HDD 405 .

[0048] The CPU 401 reads out the control program stored in the ROM 402 or the HDD 405 and executes various processes for controlling the tenant information 601. The saved tenant information 601 will be described later. The ROM 402 stores the control program executable by the CPU 401. The RAM 403 is the main storage memory of the CPU 401, and is used as a work area and a temporary storage area for expanding the various control programs stored in the ROM 402 and the HDD 405.

[0049] The HDD 405 stores, for example, tenant information 601. The HDD 405 is a storage medium, and is not limited to an HDD, but may be a flash memory, an SSD, an eMMC, or the like.

[0050] In the tenant server 40 of this embodiment, one CPU 401 executes each process shown in the flowcharts described below using one memory (RAM 403), but this is not limited to this. For example, each process can be executed by multiple CPUs, RAMs, ROMs, and HDDs working together. Also, some processes can be executed using hardware circuits such as ASICs and FPGAs.

[0051] The communication unit 404 is used for communication with other devices, and can transmit and receive data to and from various devices such as the message application server 30 via the communication unit 404. The communication unit 304 may perform wired communication using Ethernet, or may perform wireless communication such as Wi-Fi.

[0052] An example of the operation of the tenant server 40 when the tenant information 601 is transmitted from the tenant server 40 to the MFP 10 will be described. First, the CPU 401 receives a request to acquire specific information from the tenant information 601 from the MFP 10 via the communication unit 404 and the network 70. Here, the specific information refers to any of various types of information managed by the tenant server 40, such as group information, user information, and channel information, contained in the tenant information 601 (described below), and changes in response to a user instruction. Next, the CPU 401 accesses the tenant information 601 stored in the HDD 405 using a control program loaded from the ROM 402 to the RAM 403, and acquires the requested specific information. After acquiring the specific information, the CPU 401 transmits the specific information to the MFP 10, which sent the request to acquire the specific information, via the communication unit 404 and the network 70.

[0053] As described above, the message application server 30 may take over the capabilities of the tenant server 40 and some or all of the processing performed by the tenant server 40 .

[0054] 6 is a diagram showing an example of tenant information 601. In this embodiment, the tenant information 601 is stored in the HDD 405 of the tenant server 40, for example.

[0055] 6, there are two groups, group 1 and group 2, and group information 602 and group information 610 are managed. Depending on the configuration of the message application 306, one piece of tenant information may have only one piece of group information, in which case the tenant information 601 and the group information will be the same.

[0056] The group information 602 and the group information 610 each include information that constitutes a group. For example, the group information 602 has user information 603 , channel information 604 , printer information 606 , cooperative application information 607 , and file information 608 .

[0057] User information 603 indicates information about each user belonging to a group. Each user in the user information 603 has, for example, a unique ID. Each user information 603 also has status information 609. The status information 609 is a group of information indicating the current status of the user, such as an attendance status indicating whether the user is at work or at home, and a situation status indicating the current user situation. Examples of attendance status include "in the office," "remote," and "out of office," and examples of situation status include "available" and "away." In addition to the examples shown in FIG. 7, various other statuses, such as "active" and "away," can be managed. Note that the status information 609 is not limited to an attendance status or situation status, and various statuses are possible depending on the service that manages and provides the status.

[0058] The channel information 604 is information for grouping the user information 603, and includes a list 605 that compiles the user information belonging to each channel. In the channel information 604, each channel has, for example, a unique ID.

[0059] The printer information 606 indicates device information about the MFP 10. Device information about the MFP 10 includes, for example, manufacturer information, model number, serial number, MAC address, IP address, etc. An application that uses the group information 602 can send various commands to any MFP by referencing or acquiring this information.

[0060] The linked application information 607 is information about an application that links with the message application 306 corresponding to group 1. The application that links with the message application 306 includes, for example, various Office applications (software) provided by Microsoft.

[0061] The file information 608 is information about a file that is saved and shared within a group. For example, when printing is performed by the MFP 10, the file information 608 is sent to the MFP 10.

[0062] In this embodiment, a chat room is a place where chats between individual users are displayed and is not managed as a channel. A channel may have other functions, such as a schedule sharing function, in addition to displaying chats. The names of the chat rooms are not limited to these, and may be set by the service provider.

[0063] For example, when the message application 306 wishes to obtain a list of users in group 1, it obtains a list of user information 603 in group information 602 stored in the HDD 405 of the tenant server 40 via the communication unit 304 and the network 70. Similarly, channel information 604, printer information 606, linked application information 607, file information 608, and status information 609 are also obtained by the message application 306 as needed and used appropriately.

[0064] 7 is a diagram showing an example of the status table 701. In this embodiment, the status table 701 is stored in the HDD 114 of the MFP 10, for example.

[0065] The status table 701 has parameters corresponding to the status information 609 held by the tenant server 40. In this embodiment, as example parameters, the status table 701 stores the aforementioned situation status in a "status" row, the arrival status in the office in a "workplace" row, and the operation mode when the MFP 10 acquires each status in a "mode" column. In the status table 701 of FIG. 7, for example, when the situation status is "available" and the office location status is "arrived at work," the operation mode is stored as "print." As will be described later, the MFP 10 executes an operation corresponding to the operation mode based on the status table 701.

[0066] Here, the "print" operating mode refers to a mode in which, when the MFP 10 receives a fax, it prints the received data without storing it. The "storage" mode refers to a process in which, when the MFP 10 receives information including image data, it does not immediately print the data, but stores the received information including image data in a non-volatile area, such as the RAM 113 or HDD 114 of the MFP 10 or cloud storage. The HDD 114 and cloud storage are examples of storage devices, and the storage process is an example of storage processing. To print an image based on image data stored by the MFP 10, a print instruction from the user is required. Examples of the operation of these modes will be described later.

[0067] Status table 701 may be stored inside MFP 10 (for example, HDD 114), or may be stored in an external device that can communicate with MFP 10. In this embodiment, the user is configured to be able to specify any operation mode via operation unit 116 of MFP 10, but this is not limitative, and status table 701 may be unchangeable.

[0068] 8 is a diagram showing an example of a status table setting screen 810 for setting the status table 701. The status table setting screen 810 is displayed on the operation unit 116 of the MFP 10.

[0069] The status item 811 corresponds to the "status" in the status table 701, and the work location item 812 corresponds to the "work location" in the status table 701. The user can select an operation mode corresponding to each status by selecting a selection field 813. The options selectable in the selection field 813 are operation modes that the MFP 10 can perform. If the image processing device in this embodiment is a device that does not perform recording, the options may be operation modes that a device that performs recording in response to instructions from the image processing device can perform. When the change button 814 is pressed, the MFP 10 updates the status table 701 stored in the HDD 114 to the set value. It is also possible to register the operation mode selected by the user in the selection field 813 at the time of selection, without providing the change button 814. It is also possible to store multiple status tables 701 rather than just one. The multiple status tables 701 can be identified by assigning them names, such as "weekday" and "holiday." In addition to change button 814, for example, a "new registration" button (not shown) may be provided in status table setting screen 810. In this case, when the new registration button is pressed, MFP 10 may newly store new status table 701 rather than updating the values ​​of the existing table. The storage location of new status table 701 may be the same as or different from the location (e.g., HDD 114) where existing status table 701 is stored, as long as it is a location that can be referenced by CPU 111 of MFP 10 during operation of this embodiment.

[0070] 9 is a diagram showing an example of the recipient user table 901. In this embodiment, the recipient user table 901 is stored in the HDD 114 of the MFP 10, for example.

[0071] The receiving user table 901 is a table that associates fax sender information with the user information 603 of the receiving user. In this embodiment, the fax number of the sender when receiving a fax will be described as an example of the sender information. The sender information is not limited to a fax number and may be, for example, station information, a SIP address, a name, or the like. The receiving user is also a user who requests the status information 609 from the tenant server 40 via the MFP 10. The sender fax number is the fax number of an MFP or fax sender other than the MFP 10 that has faxed various information, including image data, to the MFP 10. The user information 603 is information managed by the tenant server 40. In other words, when the MFP 10 receives a fax, the receiving user table 901 is used to refer to the user information 603 corresponding to the sender information from the sender information. Furthermore, the receiving user table 901 also stores access token information corresponding to the user information 603. The information stored in the recipient user table 901 may not be access token information, which generally has an expiration date, but may be information required for authentication, such as a user ID, email address, telephone number, password, or passcode.

[0072] Note that a user who receives a fax from a sender whose fax number is not registered may be set in the receiving user table 901. In this embodiment, as an example of receiving a fax from an unregistered number, the receiving user table 901 shows an example in which "Other" is registered as the sender fax number. Also, a user may register the sender fax number as "All" (not shown) or leave it blank, so that the same user's status information 609 is acquired for image data received from any fax number. In this case, the CPU 111 of the MFP 10 that receives the fax can skip the step of referencing the sender information and the receiving user table 901 in the processing described below.

[0073] In addition, the user may register a receiving user corresponding to the area of ​​the sender of the fax by specifying only the area code of the sender's fax number, i.e., the first 1 to 3 digits of the fax number, and registering it in the receiving user table 901.

[0074] Note that the recipient user table 901 may be stored inside the MFP 10 (for example, the HDD 114), or may be stored in an external device that can communicate with the MFP 10. Furthermore, in this embodiment, the sender information is acquired via various communication units of the MFP 10, but the MFP 10 may acquire the sender information by accepting input from the user via the operation unit 116, for example, and register or update the recipient user table 901.

[0075] Note that information for identifying the sender (sender information) is not limited to a fax number. For example, when the MFP 10 receives various information including image data via a network, the sender may be identified by acquiring, for example, the IP address or MAC address of the sender's user terminal 20 and registering it in the recipient user table.

[0076] 10 shows an example of a screen for setting the recipient user table 901, and shows a user information addition / change screen 1010 for registering a new item in the recipient user table 901, a user information input screen 1020, and a user information registration completion screen 1030. This group of screens is displayed on the operation unit 116 of the MFP 10.

[0077] When a user operates a menu screen (not shown) displayed on the operation unit 116 of the MFP 10 to transition to a recipient user table setting screen, a user information addition / change screen 1010 is displayed on the operation unit 116 of the MFP 10.

[0078] The user information addition / change screen 1010 is a screen that displays information currently registered in the recipient user table 901. An area 1011 is an area that displays the current information in the recipient user table 901. A button 1012 is an add button, and pressing this button transitions the user information addition / change screen 1010 that has been displayed on the operation unit 116 of the MFP 10 to a user information input screen 1020.

[0079] In addition, the user information addition / change screen 1010 may be provided with, for example, a change button (not shown) for changing the information registered in the recipient user table 901, or a delete button (not shown) for deleting the information registered in the recipient user table 901.

[0080] The user information input screen 1020 is a screen for adding information to the recipient user table 901. The user can select either a selection item 1021 or a selection item 1023.

[0081] The input item 1022 is an item where a FAX number can be input, and when the selection item 1021 is selected, the FAX sender information to be registered can be input into the input item 1022.

[0082] When the selection item 1023 is selected, it is possible to register the user information 603 of a user who will receive a FAX received from a sender who is not registered in the recipient user table 901. In other words, by selecting the selection item 1023, the user is entered as "Other" in the recipient user table 901.

[0083] Input item 1024 is an item for inputting authentication information for authentication as user information 603. Note that the authentication information is not limited to an ID and PASSWORD, and may be any information used for authentication, such as an email address, telephone number, or passcode. Button 1025 is a confirmation button, and pressing this button adds the information entered at the time of pressing to recipient user table 901. Pressing button 1025 transitions user information input screen 1020 displayed on operation unit 116 of MFP 10 to user information confirmation screen 1030.

[0084] Input to input item 1022 and input item 1024 is performed from operation unit 116 of MFP 10. This may be performed using physical buttons such as a keyboard or numeric keypad provided on operation unit 116, or MFP 10 may display a software keyboard (not shown) on the screen and perform input using this. Furthermore, CPU 111 of MFP 10 may detect that selection item 1021 has been selected and automatically display a software keyboard (not shown), allowing the user to input to input item 1022 without selecting it.

[0085] Note that, when the "storage" operation mode is being executed, the user may also be able to specify a destination for saving various information including image data received by MFP 10. For example, a save destination selection button (not shown) may be displayed on user information input screen 1020, allowing the user to select from one or more options, such as HDD 114 or cloud storage. Furthermore, for example, buttons, input fields, selection fields, etc. (not shown) may be displayed on user information input screen 1020, allowing the user to set conditions such as a retention time for temporary storage, and allowing the stored data to be moved or deleted when the conditions are met.

[0086] The user information confirmation screen 1030 is a screen that notifies the user that the addition of information to the recipient user table 901 has been completed. When the user presses the back button 1031, the user information confirmation screen transitions to the user information addition / change screen 1010. Note that the screen may transition to a screen that was displayed before the user information addition / change screen 1010 was displayed, such as a home screen. Furthermore, for example, an "Add more" button (not shown) may be provided, or a message "Do you want to add more?" may be provided with "Yes" or "No" buttons, allowing the user to perform successive additional registrations by pressing the "Add more" or "Yes" button. In this case, the screen may transition again to the user information input screen 1020.

[0087] The user information addition / change screen 1010 may be provided with, for example, a change button (not shown) for changing the information registered in the recipient user table 901. For example, the user selects any user displayed in area 1011 and presses the change button, or presses the change button and then selects any user displayed. The CPU 111 of the MFP 10 detects the pressing of the change button and the user's selection, and transitions to the user information input screen 1020, while displaying the destination information registered for the selected user in input field 1022. Furthermore, the user information input screen 1020 may be provided with a confirm button (not shown), and when the confirm button is pressed, the data entered at that time is changed into the recipient user table 901 as the information of the selected user.

[0088] The user information addition / change screen 1010 may be provided with, for example, a delete button (not shown) for deleting information registered in the recipient user table 901. For example, the user selects any user displayed in area 1011 and presses the delete button, or presses the delete button and then selects any user displayed. The CPU 111 of the MFP 10 detects the pressing of the delete button and the user's selection, and deletes the information stored in the recipient user table 901 corresponding to the selected user. Before deleting the information, for example, a "delete" button (not shown) may be provided, or a "do you want to delete?" message may be provided with "yes" or "no" buttons, and the information may be deleted by the user pressing the "delete" or "yes" button.

[0089] As will be described later, when button 1025 is pressed, the authentication information entered in input item 1024 is sent to tenant server 40. However, if authentication fails due to non-registration or an input error by the user, a message informing that effect may be displayed on operation unit 116 of MFP 10. In this case, CPU 111 may again display user information input screen 1020 on operation unit 116, may again display the entered information, or may display some or all of the items blank.

[0090] As will be described later, the user information input screen 1020 may be configured to allow input of not only the user's personal account information, but also the channel to which the user belongs, or channel information 604, and the CPU 111 may accept these.

[0091] Registration in recipient user table 901 may be performed by performing the following process (not shown): First, a user logs in to a user account of the message application service by inputting authentication information for authenticating user information 603. Alternatively, based on the user's login to MFP 10, CPU 111 logs in to a user account corresponding to the information of the user who logged in to MFP 10. Next, CPU 111 of MFP 10 communicates with tenant server 40 and acquires information managed by tenant server 40, such as group information 602, user information 603, channel information 604, and list 605, which are related to the logged-in user account. Finally, CPU 111 displays the acquired information on operation unit 116, and the user selects user information 603 or channel information 604 from the displayed information, thereby registering the information in recipient user table 901.

[0092] When channel information 604 is registered in the receiving user table 901, the CPU 111 may check the status of all users in the list 605 that lists user information belonging to that channel. At that time, a configuration may be adopted in which printing is executed if any of the checked users is in a status corresponding to the print mode. In this configuration, the user registers authentication information for some or all users belonging to the target channel in the receiving user table 901.

[0093] 11 is a diagram showing an example of a sequence for setting the recipient user table 901. This sequence is started when information is added to the recipient user table 901, that is, when the user information input screen 1020 is displayed on the operation unit 116 of the MFP 10. In this sequence, the processing performed by the MFP 10 and the tenant server 40 will be described.

[0094] [S1101: Enter sender information] In S1101, the CPU 111 of the MFP 10 accepts input of FAX sender information via the operation unit 116. Specifically, the user selects the selection item 1021 and inputs information into the input item 102, or selects the selection item 1023, thereby causing the CPU 111 to accept the sender information.

[0095] [S1102: Enter authentication information] In S1102, the CPU 111 accepts the input of authentication information via the operation unit 116. Specifically, the user inputs the information into the input item 1024, and the CPU 111 accepts the authentication information.

[0096] [S1103: Send request] In S1103, the CPU 111 transmits an access token request to the tenant server 40. S1103 is executed by pressing the button 1025. When transmitting the access token request, the CPU 111 transmits to the tenant server 40 the authentication information accepted in S1102.

[0097] [S1104: Answer received] In S1104, the CPU 401 of the tenant server 40 performs authentication processing using the authentication information received from the MFP 10. If the authentication is successful, the CPU 401 transmits the authenticated user information and access token information to the MFP 10, and the CPU 111 of the MFP 10 receives them. Note that authentication is successful when the authentication information received from the MFP 10 matches the authentication information registered in the HDD 405 of the tenant server 40. If the authentication is unsuccessful, the CPU 401 transmits a message indicating that the authentication has failed to the MFP 10. Note that authentication is unsuccessful when the authentication information received from the MFP 10 does not match the authentication information registered in the HDD 405 of the tenant server 40. Note that if the authentication is unsuccessful, the CPU 401 is not required to notify the MFP 10, and the processing may be interrupted or stopped at that point. In this case, the CPU 111 of the MFP 10 may be configured to interrupt the processing if the user information and access token information are not transmitted from the CPU 401 of the tenant server 40 within a predetermined time.

[0098] [S1105: Generate table information] In S1105, the CPU 111 associates the sender information acquired in S1101 with the access token information acquired in S1104, and adds the information to the recipient user table 901.

[0099] When the table information generation is completed, the CPU 111 ends this process.

[0100] 12 is a flowchart showing an example of processing for setting the recipient user table 901. This processing starts when information is added to the recipient user table 901, that is, when the user information input screen 1020 is displayed on the operation unit 116 of the MFP 10. This processing progresses appropriately depending on operations by the user and responses from the tenant server 40. Each step of the flowchart of this embodiment is executed by the CPU 111 of the MFP 10 reading a control program stored in the ROM 112 or HDD 114 into the RAM 113.

[0101] [S1201: Enter sender information] In S1201, the CPU 111 accepts input of FAX sender information via the operation unit 116. Specifically, the CPU 111 accepts the sender information when the user selects a selection item 1021 and inputs information into an input item 1022, or when the user selects a selection item 1023. The accepted sender information is temporarily stored in the RAM 113. When the input of the sender information is completed, the process proceeds to S1202.

[0102] [S1202: Enter authentication information] In S1202, the CPU 111 accepts input of authentication information via the operation unit 116. Specifically, the user enters the information in the input field 1024, which causes the CPU 111 to accept the authentication information. The accepted authentication information is temporarily stored in the RAM 113. When the input of the authentication information is completed and the user presses the button 1025, the process proceeds to S1203.

[0103] [S1203: Request sent] In S1203, the CPU 111 transmits an access token request to the tenant server 40. When transmitting the access token request, the CPU 111 also transmits the access token request together with the authentication information that was received in S1201 and S1202 and temporarily stored in the RAM 113 to the tenant server 40. When the request transmission is completed, the process proceeds to S1204.

[0104] [S1204: Authentication Decision] In S1204, the CPU 111 waits for a response from the tenant server 40. The response sent from the tenant server 40 is, for example, a notification that authentication has been successful or failed, and if authentication has been successful, the response also includes user information and access token information. The CPU 111 detects receipt of the response from the tenant server 40, and if it determines from the received response that authentication has been successful, it temporarily stores the user information and access token information received from the tenant server 40 in the RAM 113 and proceeds to S1205. If the CPU 111 determines from the response received from the tenant server 40 that authentication has been unsuccessful, it regards registration in the recipient user table 901 as unsuccessful and ends the processing.

[0105] [S1205: Add user information] In S1205, the CPU 111 associates the sender information, user information, and access token information temporarily stored in the RAM 113, and adds the information to the recipient user table 901.

[0106] When the addition of the user information is completed, the CPU 111 ends this process. Also, when the process of S1205 is completed, the transmission source information temporarily recorded in S1201 is deleted from the RAM 113.

[0107] 13 is a diagram showing an example of a sequence for storing a fax job based on the status table 701. This sequence is started when the MFP 10 receives a fax job via the fax communication unit 124. A fax job is a job for executing a series of processes, from fax reception processing to recording image data received by fax on a recording medium. This sequence describes the processing performed by the MFP 10, tenant server 40, and message application server 30. In this embodiment, a receiving user table 901 stores sender numbers, receiving users, and access token information in association with each other.

[0108] [S1301: FAX job received] In step S1301 , the CPU 111 of the MFP 10 analyzes the FAX job information received via the FAX communication unit 124 and stores the FAX sender information in the RAM 113 .

[0109] [S1302: Refer to recipient user table] In S1302, the CPU 111 searches the recipient user table 901 stored in the HDD 114 for access token information of the recipient user corresponding to the sender information, based on the FAX sender information stored in the RAM 113 in S1301, and acquires this information.

[0110] [S1303: Status information request] In S1303, the CPU 111 transmits the access token information corresponding to the transmission source information acquired in S1302 to the tenant server 40, and requests the status information of the receiving user corresponding to the access token information.

[0111] [S1304: Status information received] In S1304, the CPU 401 of the tenant server 40 acquires the user status information 609 requested by the MFP 10 from the tenant information 601 stored in the HDD 405, based on the access token information transmitted from the MFP 10. If the acquisition of the user status information 609 requested by the MFP 10 is successful, the CPU 401 transmits the user status information requested by the MFP 10 to the MFP 10, and the CPU 111 of the MFP 10 receives this.

[0112] [S1305: See status table] In S1305, the CPU 111 acquires operation mode information corresponding to the status information received in S1304, based on the status table 701 stored in the HDD 114. The status information 609 sent from the tenant server 40 in S1304 is also stored in the HDD 114. In S1402, which will be described later, the status information 609 stored at this time is referenced. In this sequence, the subsequent sequence is carried out assuming that the acquired operation mode is "storage."

[0113] [S1306: Storing image data] In S1306, the CPU 111 moves the received fax job information from the RAM 113 to the HDD 114 to move it to a non-volatile area. This control is called storage control. Storage control refers to a process (storage process) in which, when the MFP 10 receives information including image data, the MFP 10 does not immediately print the information but instead stores the received information including the image data in a non-volatile area such as the RAM 113 or HDD 114 of the MFP 10. To print an image based on the image data stored by the MFP 10, a print instruction from the user is required. Note that the destination of this movement is not limited to the HDD 114 of the MFP 10, but may be an external non-volatile area (storage), such as cloud storage or flash memory. By storing the image data received by fax in a non-volatile area through storage control, the fax job information is retained and not lost even if the processing is interrupted during subsequent processing due to an event such as a power outage or a power outage of the MFP 10. Furthermore, if the data is stored in cloud storage, for example, users with access rights can view it through cloud services, which increases convenience by realizing ubiquity.

[0114] [S1307: Chat execution request] In S1307, the CPU 111 creates a request to execute a chat with the recipient user corresponding to the sender information of the received FAX, based on the access token information acquired in S1302. Next, the CPU 111 transmits this execution request to the message application server 30 (transmission instruction). At this time, the content of the chat requested by the CPU 111 is "MFP 10 received the FAX and executed the saving."

[0115] [S1308: Chat execution] In S1308, the CPU 301 of the message application server 30 transmits to the user terminal 20 a message indicating that a chat execution request has been made in S1307, along with the received content. This transmission may be actively transmitted from the CPU 301 of the message application server 30, or may be passively transmitted based on, for example, a timeline acquisition request from the user terminal 20. The message application installed in the HDD 210 of the user terminal 20 displays the chat received from the message application server 30 on the operation panel 201 of the user terminal (chat 1503), and notifies the receiving user.

[0116] Note that the chat content notified in S1308 may be configured to include part of the FAX job information. For example, in chat 1503, FAX sender information is included in the chat content. The MFP 10 sends the FAX job information together with the chat execution request notified in S1307, which allows the message application server 30 to acquire the FAX job information.

[0117] FIG. 14 shows an example of a sequence for printing an image based on image data stored in response to a status change. This sequence describes the processing performed when, from step S1307 onward, the CPU 111 detects a change in the user's status information 609 and, based on the status table 701, the operation mode corresponding to the changed status information 609 is "print." The status may be updated by the user manually inputting it via a message application through the user terminal 20, or it may be automatically estimated and updated based on information such as the update history of the tenant information 601 and the operation history of the user terminal 20. This processing is performed even if the user does not issue a print instruction. This sequence describes the processing performed by the MFP 10, the tenant server 40, and the message application server 30.

[0118] [S1401: Status information request] In S1401, the CPU 111 of the MFP 10 transmits the access token information acquired from the recipient user table 901 in S1302 to the tenant server 40 and requests status information. The request made in S1401 is the status information 609 of the recipient user corresponding to the sender information of the image data stored in S1306. Note that the status information request may be made to all users stored in the tenant server 40.

[0119] [S1402: Status information received] In S1402, the CPU 401 of the tenant server 40 acquires the user status information 609 requested by the MFP 10 from the tenant information 601 stored in the HDD 405, based on the access token information transmitted from the MFP 10. If the acquisition of the user status information 609 requested by the MFP 10 is successful, the CPU 401 transmits the user status information 609 requested by the MFP 10 to the MFP 10, and the CPU 111 of the MFP 10 receives this information. If the status information 609 transmitted from the tenant server 40 differs from the status information received in S1304, the CPU 111 of the MFP 10 executes the process of S1403, assuming that a change has been detected.

[0120] [S1403: See status table] In S1403, the CPU 111 acquires operation mode information corresponding to the status information acquired in S1402 based on the status table 701 stored in the HDD 114. In this sequence, the CPU 111 proceeds with the subsequent sequence assuming that the mode indicated by the acquired operation mode information is "printing."

[0121] [S1404: Checking stored image data] In S1404, the CPU 111 searches for image data received by the MFP 10 and stored in the HDD 114 through the storage control in S1306. While storage control is performed in S1306, if the user operates the operation unit 116 of the MFP 10 to print the stored image data before the status information 609 is updated, for example, the stored image data will no longer exist in S1404.

[0122] [S1405: Printing images based on stored image data] In S1405, CPU 111 executes printing of an image based on the image data received and stored by MFP 10, which was searched for in S1404. That is, in printing unit 120 of MFP 10, an image based on the image data received based on the FAX job received by MFP 10 in S1301 is recorded on a recording medium. For example, printing on recording paper is one example. Note that if image data received by MFP 10 is stored in, for example, cloud storage rather than HDD 114 in S1306, MFP 10 obtains the image data from the cloud storage where it is stored and prints it. S1405 is executed without a print instruction from the user. Note that a print process may be performed in which an image based on image data received by MFP 10 via FAX is printed on a recording medium in response to a print instruction from the user.

[0123] [S1406: Chat execution request] In S1406, the CPU 111 creates a request to execute a chat with the recipient user corresponding to the sender information of the received FAX, based on the access token information acquired from the recipient user table 901 in S1302. Next, the CPU 111 transmits this execution request to the message application server 30 (transmission instruction). At this time, the content of the chat execution requested by the CPU 111 is "The MFP has received the FAX, and printing of the image based on the stored image data received by FAX has been completed."

[0124] [S1407: Chat execution] In S1407, the CPU 301 of the message application server 30 notifies the user terminal 20 that there has been a chat execution request in S1406 from the MFP 10. This transmission may be actively transmitted from the CPU 301 of the message application server 30, or may be passively transmitted based on, for example, a timeline acquisition request from the user terminal 20. The message application installed in the HDD 210 of the user terminal 20 displays the chat received from the message application server 30 on the operation panel 201 of the user terminal (chat 1504) and notifies the user of the receipt.

[0125] When the request to start a chat in S1406 is completed, the CPU 111 ends this process.

[0126] It should be noted that the notification to the user of the receipt in steps S1405 and S1406 is not essential, and the MFP 10 does not necessarily have to notify the user that the stored image data has been printed.

[0127] Note that the status information request made in S1401 may be for the user status corresponding to the sender information of the image data remaining in HDD 114, rather than the user status corresponding to the sender information of the image data for which the buffering control in S1306 was performed. In this case, for example, the user operates operation unit 116 of MFP 10 to print buffered image data before the status information 609 is updated, eliminating the need to perform processing for the reduced job, and making it possible to omit the processing in S1404 and S1608 (described later).

[0128] 15 is a diagram showing an example of a chat screen 1500 of a message application. The chat screen 1500 is a screen provided by the message application, and is a chat screen displayed on the operation panel 201 of the user terminal 20.

[0129] Display field 1501 shows information about the user himself / herself, and chat screen 1500 is the screen used by user A. Display field 1502 is a field that displays a list of people with whom there is a chat record, and screen 1500 displays a chat screen with MFP 10.

[0130] Chat 1503 is an example of a chat notified in S1308 in which the user is notified that the MFP 10 has received a FAX and that image data has been stored. Chat 1504 is an example of a chat notified in S1407 in which the user is notified that the stored image data has been printed.

[0131] The types and layout of information displayed on the chat screen 1500 are merely examples, and may differ significantly from this example depending on the provider of the message application and the user customizing it.

[0132] Alternatively, the MFP 10 may be configured to accept a print instruction from a user via the chat screen 1500, and the user may be configured to instruct printing of an image based on image data stored in the MFP 10 via the chat screen 1500. In this configuration, when the image data received by the MFP 10 is stored by the MFP 10, the receiving user corresponding to the sender information can send a print instruction to the MFP 10 that performed the storage process via the chat screen 1500. The MFP 10 that has received the print instruction in this manner prints, for example, an image based on the image data stored in the HDD 114 using the printing unit 120.

[0133] In addition, if multiple MFPs 10 are connected and the stored image data can be communicated with each other, the user may send a print instruction to any MFP 10, such as the MFP 10 closest to the user's current location.

[0134] The user may issue a print instruction from chat screen 1500 using a software button displayed by a message application or a physical button on user terminal 20. This print instruction may also be issued by the user replying to the chat with a sentence such as "Please print it." Furthermore, user terminal 20 may be equipped with a gyro sensor, for example, so that after chat 1503 is displayed, a print instruction is sent to MFP 10 in response to a specific user action, such as shaking.

[0135] 16 is a flowchart showing an example of processing of a FAX job received by the MFP 10. Specifically, the flowchart shows processing in which the MFP 10 stores or prints the received image data based on the acquired user status information 609 and status table 701. This processing starts when the MFP 10 receives a FAX job via the FAX communication unit 124.

[0136] [S1601: Receiving a fax job] In S1601, the CPU 111 of the MFP 10 temporarily stores the received FAX job information in the RAM 113. When the reception of the FAX job is completed, the process proceeds to S1602.

[0137] [S1602: Search for account information] In S1602, the CPU 111 of the MFP 10 searches the recipient user table 901 stored in the HDD 114 for user information 603 corresponding to the sender information, based on the sender information of the FAX job information stored in the RAM 113 in S1601. When the search for the account information is completed, the process proceeds to S1603.

[0138] [S1603:Determine whether account information was found] In S1603, the CPU 111 of the MFP 10 determines whether or not the user information 603 corresponding to the sender information was found in the recipient user table 901 in S1602. If the CPU 111 determines that the user information 603 corresponding to the sender information was found in the recipient user table 901, the process proceeds to S1604. If the CPU 111 determines that the user information 603 corresponding to the sender information was not found in the recipient user table 901, the process proceeds to S1612 without relying on the information in the recipient user table 901.

[0139] [S1604: Status information request] In S1604, the CPU 111 of the MFP 10 acquires access token information corresponding to the searched user information 603 from the recipient user table 901. Furthermore, the CPU 111 transmits the access token information to the tenant server 40 and requests the status information 609. When the request for the status information 609 is completed, the process proceeds to S1605.

[0140] [S1605: Status information acquisition decision] In S1605, CPU 111 of MFP 10 waits until status information 609 is transmitted from tenant server 40. If CPU 111 determines that status information 609 has been transmitted from tenant server 40 and that the status information 609 has been acquired, the process proceeds to S1606. If CPU 111 determines that the status information 609 has not been acquired, the process continues to wait and remains in S1605.

[0141] [S1606: Status table search] In S1606, the CPU 111 of the MFP 10 searches the status table 701 for an operation mode corresponding to the status information 609 based on the status information 609 acquired in S1605, and acquires the operation mode.

[0142] [S1607: Determining the operating mode] In S1607, the CPU 111 of the MFP 10 determines whether the operating mode corresponding to the status information 609 acquired in S1606 is the storage setting or the print setting. If the CPU 111 determines that the operating mode corresponding to the acquired status information 609 is the storage setting, the process proceeds to S1608. If the CPU 111 determines that the operating mode corresponding to the acquired status information 609 is the print setting, the process proceeds to S1611.

[0143] [S1608: Determine whether the storage process has been completed] In S1608, the CPU 111 of the MFP 10 determines whether the FAX job being processed has been stored. If the CPU 111 determines that the FAX job being processed has been stored, the process proceeds to S1604. If the CPU 111 determines that the FAX job being processed has not been stored, the process proceeds to S1609.

[0144] [S1609: Storage Processing] In S1609, the CPU 111 of the MFP 10 moves the FAX job information saved in the RAM 113 in S1601 to the HDD 114 and executes the image data storage process. When the image data storage process is completed, the process proceeds to S1610.

[0145] [S1610: "Storage completed" notification] In S1610, the CPU 111 of the MFP 10 notifies the message application server 30 that the image data has been stored by the MFP 10. That is, in S1610, the CPU 111 notifies the user of the chat 1503 via the message application server 30 and the message application. Once the "storage completed" notification is complete, the process proceeds to S1604. This notification is sent to the talk room corresponding to the user for whom the status information 609 was acquired.

[0146] [S1611: Determine whether the storage process has been completed] In S1611, the CPU 111 of the MFP 10 determines whether the FAX job being processed has been stored. If the CPU 111 determines that the FAX job being processed has not been stored, the process proceeds to S1612. If the CPU 111 determines that the FAX job being processed has been stored, the process proceeds to S1613.

[0147] [S1612:Print] In S1612, the CPU 111 of the MFP 10 instructs printing of an image based on the image data stored in the RAM 113 in S1601, and the printing unit 120 prints this image. When printing is complete, the process proceeds to S1615.

[0148] [S1613: Determining whether or not stored image data remains] In S1613, CPU 111 of MFP 10 determines whether the image data saved in the storage process in S1609 remains in HDD 114. If CPU 111 determines that the image data saved in the storage process remains in HDD 114, the process proceeds to S1614. If CPU 111 determines that the image data saved in the storage process does not remain in HDD 114, the process proceeds to S1615. Note that examples of factors that may cause image data saved in the storage process to not remain in HDD 114 include the user directly using operation unit 116 in MFP 10 to print an image based on the image data, or interrupting printing.

[0149] [S1614: Printing images based on stored image data] In S1614, CPU 111 of MFP 10 instructs printing of an image based on image data saved in HDD 114 during the storage process, and printing unit 120 prints this image. When printing of the image based on the stored image data is completed, the process proceeds to S1615. Note that when the image based on the stored image data is printed by MFP 10, CPU 111 deletes the stored image data. Note that this deletion is not essential, and the stored image data may continue to be held even after the image based on the stored image data is printed by MFP 10.

[0150] [S1615: "Printing complete" notification] In S1615, the CPU 111 of the MFP 10 notifies the message application server 30 that printing has been executed by the MFP 10. That is, in S1615, the CPU 111 notifies the user of the chat 1504 via the message application server 30 and the message application. This notification is sent to the chat room corresponding to the user from whom the status information 609 was acquired. Once the "printing completed" notification is complete, the CPU 111 ends this processing. Furthermore, once the processing of S1615 is completed, the sender information temporarily recorded in S1601 is deleted from the RAM 113.

[0151] With the above configuration, it becomes possible to execute print processing or storage processing for a job received by MFP 10 by referring to status table 701, recipient user table 901, and status information 609 stored in tenant server 40. It also becomes possible for MFP 10 to execute printing by detecting a change in status information 609 stored in tenant server 40.

[0152] Conventionally, when an MFP executes a process for storing received image data, a user action is required to print the stored image data, such as operating the MFP to instruct printing, sending a print instruction via chat, or bringing a user terminal close to the MFP. According to the present invention, even when image data is stored, the image processing device detects that the status information 609 has changed to specific status information 609 indicating that the user is ready to receive the image, and an image based on the image data is printed without any user action. As described above, the present invention has the effect of reducing the effort required to print an image of received image data in a situation where the user can immediately receive the printed matter.

[0153] Furthermore, in cases where the receiving user cannot immediately receive a fax received by MFP10, for example, when the receiving user is absent, the fax will not be printed immediately after it is received, which has the effect of ensuring safety from the perspective of information security.

[0154] As described above, in this embodiment, the situation status and attendance status are set as status information 609 and correspond to the operation mode of the MFP 10, but for example, only the situation status may be set as status information 609, and the effects of the present invention may still be exhibited. However, in order to improve the effects of the present invention, it is preferable to use multiple indicators with different attributes as status information 609, as in this embodiment.

[0155] In this embodiment, user information 603 is registered in the receiving user table 901. However, channel information 604 may be registered instead of the user information 603. This configuration may be used to check the status of all users in a list 605 that compiles user information belonging to the channel information 604, and if any of the users is in a status corresponding to the print mode, printing may be performed. In this configuration, the user registers authentication information for some or all users belonging to the target channel in the receiving user table 901. As described above, the MFP 10 acquires and registers access token information for each user and acquires status information 609 for each user. The user may also register channel information 604 in the receiving user table 901 by entering a channel ID. In this configuration, the MFP 10 issues a chat execution request not to an individual user but to a channel shared by the user, such as a group chat. In this configuration, the MFP 10 may print by having one of the users in the list 605 that compiles user information belonging to the channel information 604 send a print instruction to the MFP 10 via the chat screen 1500. Furthermore, in this embodiment, the MFP 10 is configured to execute the status information 609 acquisition process S1302 with the receipt of a FAX job S1301 as a trigger, but the MFP 10 may be configured to periodically acquire the status information 609 before receiving a FAX job and store it in the HDD 114. This makes it possible to continue the sequence without accessing the tenant server 40.

[0156] Note that if the recipient user of image data received by MFP10 can be identified or access can be made on a cloud service without using authentication information, handling of access token information is not essential. For example, in the case of a cloud service that does not have an authentication process and manages each user only by their unique ID, the user may register their ID instead of access token information in recipient user table 901. Furthermore, in this case, the processing related to authentication information can be omitted from S1102 to S1104, S1201 to S1204, S1303, and S1401 in this embodiment. [Explanation of symbols]

[0157] MFP 10 User terminal 20 Message Application Server 30 Tenant Server 40 Tenant Information 601 Status Table 701 Recipient User Table 901

Claims

1. An image processing device, receiving means for receiving image data by FAX; an acquisition means for acquiring status information indicating the status of a user from a chat server; a printing means for printing an image based on the received image data onto a recording medium, the acquiring means acquires the status information of the user corresponding to the transmission source information of the received image data, The printing means prints an image based on the received image data onto a recording medium based on the specific status information acquired by the acquisition means, without the image processing device needing a print instruction from a user after the status information is acquired by the acquisition means.

1. An image processing device comprising:

2. 2. The image processing apparatus according to claim 1, wherein the process executed by the image processing apparatus differs depending on the acquired status information.

3. An image processing device as described in claim 2, characterized in that if the acquired status information is specific status information, a printing process is executed to print an image based on the received image data on a recording medium, and if the acquired status information is not the specific status information, a storage process is executed to store the received image data in a storage device.

4. 4. The image processing apparatus according to claim 3, wherein the printing process is not executed until the specific status information is acquired by the acquisition unit.

5. 5. The image processing apparatus according to claim 4, wherein the received image data is stored in the storage device until the specific status information is acquired by the acquisition means.

6. 6. The image processing apparatus according to claim 5, wherein the specific status information is set by a user.

7. further comprising a communication means; 2. The image processing apparatus according to claim 1, wherein the communication means transmits a notification transmission instruction to the chat server via a network.

8. 8. The image processing apparatus according to claim 7, wherein the instruction to send a notification is an instruction to send a notification of the content of a process performed by the image processing apparatus.

9. The image processing device according to claim 8, characterized in that the notification is a notification that a storage process for storing the received image data in a storage device has been executed when the acquired status information is not the specific status information.

10. The image processing device according to claim 8, characterized in that the notification is a notification that a printing process has been executed to print an image based on the received image data onto a recording medium, which is made when the acquired status information is specific status information.

11. The image processing device according to claim 8 , wherein the notification is sent to a talk room corresponding to the user from whom the status information is acquired.

12. 9. The image processing apparatus according to claim 8, wherein the notification is sent to a channel to which the user from whom the status information was acquired belongs.

13. The image processing device according to claim 8 , wherein the notification is given by chat.

14. 2. The image processing apparatus according to claim 1, wherein the print instruction is an instruction received by the image processing apparatus from an external device that can communicate with the image processing apparatus via a network.

15. Further comprising an operation unit, The image processing apparatus according to claim 1 , wherein the operation unit receives the print instruction.

16. 2. The image processing apparatus according to claim 1, further characterized in that the acquisition means acquires the status information of the user who belongs to a channel associated with information on a sender of the received image data.

17. The image processing device according to claim 1 , further characterized in that the printing means prints, onto the recording medium, an image based on the image data received by the image processing device and stored in cloud storage.

18. a receiving step of receiving image data by fax; an acquisition step of acquiring status information indicating the status of the user from the chat server; a printing step of printing an image based on the received image data onto a recording medium; and the acquiring step acquires the status information of the user corresponding to the transmission source information of the received image data; The printing step is a step of printing an image based on the received image data onto a recording medium, based on the specific status information acquired by the acquisition step, without requiring a print instruction from a user by the image processing device after the status information is acquired by the acquisition step. An image processing method comprising:

19. a receiving step of receiving image data by fax; an acquisition step of acquiring status information indicating the status of the user from the chat server; a printing step of printing an image based on the received image data onto a recording medium; and the acquiring step acquires the status information of the user corresponding to the transmission source information of the received image data; The printing step is a step of printing an image based on the received image data onto a recording medium, based on the specific status information acquired by the acquisition step, without requiring a print instruction from a user by the image processing device after the status information is acquired by the acquisition step.

2. A program for causing an image processing device to execute an image processing method comprising:

Images