Image processing apparatus, image processing method, and program product

Abstract

The invention discloses an image processing apparatus, an image processing method, and a program product. An image processing apparatus includes: a modem configured to receive image data via fax (FAX); one or more memories storing one or more programs, and one or more processors executing the programs to cause the image processing apparatus to acquire status information indicating a state of a user from a chat service; and a printer that prints an image based on the received image data on a recording medium, in which the processor causes the image processing apparatus to acquire status information about a user corresponding to sender information about the received image data, and in which the printer prints the image based on the received image data on the recording medium based on the acquisition of specific status information. An image based on the received image data is printed on the recording medium without the image processing apparatus having to accept a user's print instruction after the acquisition of the status information.

Description

Technical Field

[0001] The present disclosure relates to an image processing apparatus, an image processing method, and a program product. Background Art

[0002] There is a technology that allows an image processing device to send received images to a cloud server that provides cloud storage services or chat services. Japanese Patent Application Publication No. 2023-15663 discusses a technology that enables settings to determine whether documents received via fax (FAX) are simply printed or stored in a "FAX receiving box" without printing.

[0003] In a case where a user who anticipates receiving a printout can immediately receive the printout, it is desirable to print an image based on image data received via FAX.

[0004] In the case of the image processing apparatus discussed in Japanese Patent Application Publication No. 2023-15663, the setting of whether to print a document received by the image processing apparatus via FAX is preferably switched by the user operating the operating unit of the image processing apparatus. For example, if the user frequently switches between working in the office and working at home and only wants to print printouts when the user is working in the office (a situation in which the user may be able to receive printouts), it is troublesome to change the setting each time. Summary of the Invention

[0005] The present disclosure is intended to reduce workload of an image processing apparatus in printing an image based on image data received via facsimile (FAX) if there are cases where users may be able to immediately receive printouts and cases where they may not.

[0006] According to one aspect of the present disclosure, an image processing device includes: a modem configured to receive image data via facsimile (FAX); one or more memories storing one or more programs, and one or more processors executing the programs to cause the image processing device to obtain status information indicating a user's status from a chat service; and a printer configured to print an image based on the received image data on a recording medium, wherein the processor causes the image processing device to obtain status information about a user corresponding to sender information about the received image data, and wherein the printer is configured to, based on the acquisition of specific status information, print an image based on the received image data on a recording medium after the acquisition of the status information without the image processing device accepting a print instruction from the user.

[0007] Further features of the present disclosure will become apparent from the following description of exemplary embodiments with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a diagram illustrating an example of an overall configuration of a message application service.

[0009] Figure 2 is a diagram illustrating an example of a hardware configuration of a multifunction peripheral (MFP).

[0010] Figure 3 is a diagram illustrating an example of a hardware configuration of a user terminal.

[0011] Figure 4 is a diagram illustrating an example of a hardware configuration of a message application server.

[0012] Figure 5 is a diagram illustrating an example of a hardware configuration of a tenant server.

[0013] Figure 6 is a diagram illustrating an example of tenant information.

[0014] Figure 7 is a diagram illustrating an example of a status table.

[0015] Figure 8 is a diagram illustrating an example of a status table setting screen for setting a status table.

[0016] Figure 9 is a diagram illustrating an example of a recipient user table.

[0017] Figure 10 is a diagram illustrating an example of a screen for setting a recipient user table.

[0018] Figure 11 is a diagram illustrating an example of a sequence for setting a recipient user table.

[0019] Figure 12 is a flowchart illustrating an example of setting processing of a recipient user table.

[0020] Figure 13 is a diagram illustrating an example of a sequence for spooling a fax (FAX) job based on a status table.

[0021] Figure 14 is a diagram illustrating an example of a sequence of printing an image based on spooled image data according to a change in situation.

[0022] Figure 15 is a diagram illustrating an example of a chat screen of a messaging application.

[0023] Figure 16 is a flowchart illustrating an example of processing of a FAX job received by the MFP. DETAILED DESCRIPTION

[0024] The exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The following exemplary embodiments are not intended to limit the scope of the claims, and all combinations of features described in the exemplary embodiments are not necessarily required for the present disclosure.

[0025] In the exemplary embodiments of the present disclosure, a multifunction peripheral (MFP) having printing, scanning, and fax (FAX) functions is described as an example of an image processing apparatus. The image processing apparatus according to this exemplary embodiment is not limited to an MFP, but may be any apparatus capable of implementing this exemplary embodiment. Examples include apparatuses without a scanning function and apparatuses that send print instructions to an image forming apparatus including a printing unit.

[0026] The present exemplary embodiment will be described using a FAX reception job as an example. However, the present disclosure is not limited thereto and can be applied to print jobs other than the FAX reception job.

[0027] Exemplary embodiments of the present disclosure will now be described.

[0028] Figure 1 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 according to this exemplary embodiment is not limited to the message application service and may be, for example, a mail, storage, or information management service in the cloud.

[0029] The message application service includes, for example, an MFP 10 as 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 the servers 30 and 40 are connected via a network 70 and can communicate with each other. The network 70 is a wireless or wired network including the Internet, a wide area network (WAN), and / or a local area network (LAN). The MFP 10 is connected to a public switched telephone network (PSTN) 80 and can control the FAX communication protocol.

[0030] The MFP 10 has a function of receiving image data, and has the ability to print an image based on the image data on a recording medium. For example, the MFP 10 can receive image data from a network 70 (such as the Internet) and a PSTN 80. The MFP 10 according to the present exemplary embodiment refers to an image processing device that also has a function of communicating with the message application server 30 via the network 70 and sending and receiving image data. Therefore, 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 read a document and generate image data based on the read document image, and send the image data generated based on the read document image to the message application server 30. The content sent and received by the MFP 10 is not limited to image data. For example, the MFP 10 can send and receive various types of data and signals, such as signals for controlling the FAX communication protocol. Although Figure 1 An example in which two MFPs 10 are connected is illustrated, but any number of MFPs 10 may be connected.

[0031] The user terminal 20 is an example of an information terminal used by a user when using a message application service. Examples include a smartphone, a tablet terminal, and a personal computer. Figure 1 The example of three user terminals 20 connected is shown, but any number of user terminals 20 may be connected. Users operate user terminals 20 to access the messaging application server 30 in the cloud 60, exchange messages with other users, and use installed applications. The user terminals 20 and messaging application server 30 are connected to a wired or wireless communication network (network 70) and can transmit and receive data with each other. In this exemplary embodiment, the Internet is assumed as an example of the communication network 70. However, a dedicated line may also be used.

[0032] The message application server 30 is a cloud server deployed in the cloud 60 and is a server that provides the use of the message application 306 (see Figure 4 The message application server 30 generally performs processing related to message exchange, such as message transmission and reception processing with the user terminal 20 and display of a message transmission and reception screen.

[0033] The tenant server 40 is a cloud server deployed in the cloud 60 and is a server that stores and provides various pieces of tenant information. Details of the tenant information stored in the tenant server 40 will be described below. Figure 6 Provide a description.

[0034] A part or all of the capabilities of the tenant server 40 and the processing performed by the tenant server 40 to be described below may be replaced by the message application server 30. In this case, the tenant server 40 is not necessary in the present configuration.

[0035] Figure 2 is a diagram illustrating an example of the hardware configuration of the MFP 10. The MFP 10 includes 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 includes a central processing unit (CPU) 111, a read-only memory (ROM) 112, a random access memory (RAM) 113, a hard disk drive (HDD) 114, and various interfaces (I / Fs).

[0036] The various I / Fs include 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 .

[0037] Operation unit I / F 115 is a connection unit between control unit 110 and operation unit 116, and connects control unit 110 and operation unit 116. Reading unit I / F 117 is a connection unit between control unit 110 and reading unit 118, and connects control unit 110 and reading unit 118. Printing unit I / F 119 is a connection unit between control unit 110 and printing unit 120, and connects control unit 110 and printing unit 120. Wireless communication unit I / F 121 is a connection unit between control unit 110 and wireless communication unit 122, and connects control unit 110 and wireless communication unit 122. FAX unit I / F 123 is a connection unit between control unit 110 and FAX communication unit 124, and connects control unit 110 and FAX communication unit 124. Communication unit I / F 125 is a connection unit between control unit 110 and communication unit 126, and connects control unit 110 and communication unit 126.

[0038] The control unit 110 including the CPU 111 controls the operation of the entire MFP 10. The CPU 111 reads the control program stored in the ROM 112 or the HDD 114 into the RAM 113 and performs various types of control including reading control and printing control. The ROM 112 stores the control program that can be executed by the CPU 111. The ROM 112 also stores boot programs and font data. The RAM 113 is the main storage memory of the CPU 111 and is used as a temporary storage area and work area for loading 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 types of setting information. The HDD 114 is a storage medium, which is not limited to the HDD 114 and may be a flash memory, a solid-state drive (SSD), or an embedded multimedia card (eMMC).

[0039] The MFP 10 according to this exemplary embodiment is configured so that a single CPU 111 uses a single memory (RAM 113) to perform the processing shown in the flowchart to be described below. However, this is not restrictive. For example, multiple CPUs, RAMs, ROMs, and HDDs can cooperate to perform processing. Hardware circuits such as application-specific integrated circuits (ASICs) and field-programmable gate arrays (FPGAs) can be used to perform some of the processing.

[0040] For example, the operation unit 116 includes a display unit such as a touch screen and hardware keys. The operation unit 116 displays information to the user and accepts input from the user. Examples of user input include inputting instructions for causing the MFP 10 to execute desired processing, inputting characters and symbols into the MFP 10, and user input for browsing information. Examples of inputting instructions for causing the MFP 10 to execute desired processing include inputting instructions for executing a process executable by the MFP 10, such as a print instruction. Examples of user input for browsing information include input for selecting a file or changing the display size to browse data stored in the HDD 114. The touch screen can use any typical input method or detection method, such as resistive, infrared, electromagnetic induction, and capacitive methods. Examples of hardware keys include a keyboard with keys labeled with letters and numbers, and physical buttons for instructing processing, such as a "Start" key and a "Reset" key. For example, a toggle switch, a rocker switch, a push button switch, a rotary switch, a slide switch, a key lock switch, and / or a tactile switch can also be used.

[0041] Examples of the reading unit 118 include a scanner. The reading unit 118 reads a document by moving the document or a sensor, and generates image data (such as binary data) based on the read document image. The image data generated by the reading unit 118 is, for example, transmitted to an external device (such as an information processing device), stored in an external recording device (such as a universal serial bus (USB) device), or printed on a recording sheet.

[0042] The printing unit 120 receives image data to be printed (target image data to be printed) from the CPU 111 and prints the image on a recording sheet fed from a feed cassette (not shown). The operation of the printing unit 120 is not limited to printing on paper and can be performed on non-paper media such as overhead projector (OHP) sheets.

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

[0044] The FAX communication unit 124 includes, for example, a modem and a network control unit (NCU) for FAX communication. The FAX communication unit 124 is connected to the PSTN 80 and controls the FAX communication protocol by controlling the modem and the NCU.

[0045] The communication unit 126 transmits various types of information and image data in the MFP 10 to an external device connected to the network 70, and receives print data and various types of information from an information processing device connected to the network 70. Examples of the various types of information include status information and setting information. Transmission and reception via the network 70 can be achieved, for example, by sending and receiving via electronic mail (email) or by sending and receiving files using other protocols such as File Transfer Protocol [FTP], Server Message Block [SMB], and Web Distributed Authoring and Versioning [WebDAV]. The communication unit 126 can also send and receive image data and message data via the network 70 in response to access from the user terminal 20 and the message application server 30 using Hypertext Transfer Protocol [HTTP] communication. The 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 user interface [UI] function).

[0046] Figure 3 2 is a diagram illustrating an example of a hardware configuration of the user terminal 20. Although the user terminal 20 according to the present exemplary embodiment is assumed to be a device such as a smartphone and a tablet personal computer (PC), the user terminal 20 is not limited thereto. For example, a user terminal 20 may be used which can be configured by using Wired connections or wireless connections using radio waves (such as Wi-Fi Any other information processing device connected to the network 70 for communication. The wireless connection method is not limited to For example, you can use and other communication methods.

[0047] The user terminal 20 includes an operation panel 201, a camera 204, a near field communication (NFC) communication unit 205, Communication unit 206 , CPU 207 , ROM 208 , RAM 209 , HDD 210 , and wireless LAN communication unit 211 .

[0048] The CPU 207 reads a control program stored in the ROM 208 or the HDD 210 and executes various types of processing for controlling the operation of the user terminal 20. The ROM 208 stores a control program that can be executed by the CPU 207. The RAM 209 is a main storage memory of the CPU 207 and is used as a temporary storage area and a work area for loading various control programs stored in the ROM 208 and the HDD 210.

[0049] The HDD 210 stores, for example, image data, print data, various programs, various application programs, various addresses, and various types of setting information. The HDD 210 is a storage medium that is not limited to an HDD and may be a flash memory, an SSD, or an eMMC.

[0050] The user terminal 20 according to this exemplary embodiment is configured so that a single CPU 207 uses a single memory (RAM 209) to perform the processing shown in the flowchart to be described below. However, this is not restrictive. For example, multiple CPUs, RAMs, ROMs, and HDDs can collaborate to perform processing. Some processing can be performed using hardware circuits such as ASICs and FPGAs. The operation panel 201 has a touch screen function that can detect the user's touch operation and displays various screens provided by the operating system (OS) and applications. The operation panel 201 is also used to check the information stored in the message application server 30. The user can input the desired operation instruction to the user terminal 20 by inputting a touch operation to the operation panel 201. The user terminal 20 includes hardware keys not shown, and the user can use the hardware keys to input operation instructions to the user terminal 20. The detection method for detecting the user's touch operation on the touch screen can be any typical detection method such as resistive, infrared, electromagnetic induction, and capacitive methods. Software keys can be displayed on the touch screen so that the operation instruction is input by the user operation on the touch screen. Any OS can be used as the OS. Examples include Windows, macOS, Unix, Linux, Android, and iOS. Examples of the application may include applications for performing email sending, browsing, chatting, camera imaging, image display, and setting configuration functions.

[0051] The camera 204 captures an image based on an imaging instruction of the user. The image captured by the camera 204 is stored in a predetermined area of the HDD 210. A program capable of analyzing a Quick Response (QR) code may be pre-stored in the ROM 208 or the HDD 210, or an application having this function may be installed so that the QR code read from the camera 204 can be analyzed. Information acquisition is not limited to QR For example, one-dimensional codes such as bar codes or two-dimensional codes such as DataMatrix, MaxiCode, Portable Data File 417 (PDF417), and Aztec Code may be analyzed for information acquisition.

[0052] The user terminal 20 can communicate with the NFC communication unit 205, The communication unit 206 and the wireless LAN communication unit 211 are connected to various wireless devices and transmit and receive data. The communication unit 206 can support Low power standards and / or Classic standard.

[0053] Although user terminal 20 according to the present exemplary embodiment establishes a wireless network connection, for example, a wired port not shown may be disposed to establish a wired network connection.

[0054] Figure 4 3 is a diagram illustrating an example of a hardware configuration of the message application server 30. The message application server 30 refers to a chat server that provides a chat service.

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

[0056] The CPU 301 reads the control program stored in the ROM 302 and the message application 306 stored in the HDD 305, loads the programs into the RAM 303, and executes various types of processing for controlling the operation of the message application server 30. The ROM 302 stores the control program that can be executed by the CPU 301. The RAM 303 is the main storage memory of the CPU 301 and is used as a temporary storage area and work area for loading various control programs stored in the ROM 302 and the HDD 305.

[0057] The HDD 305 stores various types of data such as messages, image data, channel information, and applications. The HDD 305 is a storage medium that is not limited to an HDD and may be a flash memory, an SSD, or an eMMC.

[0058] The message application server 30 according to this exemplary embodiment is configured so that a single CPU 301 uses a single memory (RAM 303) to perform the processing shown in the following flowchart. However, this is not restrictive. For example, multiple CPUs, RAMs, ROMs, and HDDs may cooperate to perform the processing. Some of the processing may be performed using hardware circuits such as ASICs and FPGAs.

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

[0060] The communication unit 304 is used to communicate with other devices. For example, data can be sent to and received from various devices such as the user terminal 20 and the MFP 10 via the communication unit 304. The communication unit 304 can perform wired communication using Ethernet or a wireless communication such as Wireless communication of communication. 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 the message application 306 read from the HDD 305 into the RAM 303 and receives the posted message sent from the user terminal 20 via the communication unit 304 under the control of the message application 306. The CPU 301 then stores the posted message received from the user terminal 20 in the HDD 305. The CPU 301 can appropriately notify the user terminal 20 or other user terminals 20 of the posting of the message via the communication unit 304 through the network 70. The notified (one or more) user terminals 20 display the notification on their / their touch screen-type operation panel 201.

[0061] Figure 5 is a diagram illustrating an example of the hardware configuration of the tenant server 40 .

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

[0063] The CPU 401 reads the control program stored in the ROM 402 or the HDD 405 and executes various types of processing for controlling the tenant information 601. The tenant information 601 to be stored will be described below. The ROM 402 stores the control program that can be executed by the CPU 401. The RAM 403 is the main storage memory of the CPU 401 and is used as a temporary storage area and work area for loading various control programs stored in the ROM 402 and the HDD 405.

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

[0065] The tenant server 40 according to this exemplary embodiment is configured so that a single CPU 401 uses a single memory (RAM 403) to perform various processes shown in the flowchart below. However, this is not restrictive. For example, multiple CPUs, RAMs, ROMs, and HDDs may collaborate to perform processes. Some processes may be performed using hardware circuits such as ASICs and FPGAs.

[0066] The communication unit 404 is used to communicate with other devices. Data can be sent to and received from various devices such as the message application server 30 via the communication unit 404. The communication unit 404 can perform wired communication using Ethernet or a network such as Such wireless communications.

[0067] Now, we will describe an example of the operation of tenant server 40 when tenant server 40 transmits tenant information 601 to MFP 10. CPU 401 first receives a request from MFP 10 via communication unit 404 and network 70 to obtain specific information in tenant information 601. As described herein, specific information refers to any of the various types of information managed by tenant server 40 in tenant information 601, such as group information, user information, and channel information, described below, and varies according to user instructions. Using a control program loaded from ROM 402 to RAM 403, CPU 401 accesses tenant information 601 stored in HDD 405 and retrieves the requested specific information. Once the specific information is retrieved, CPU 401 transmits the specific information to MFP 10, which transmitted the request, via communication unit 404 and network 70.

[0068] As described above, part or all of the capabilities of the tenant server 40 and the processing performed by the tenant server 40 may be replaced by the message application server 30 .

[0069] Figure 6 is a diagram illustrating an example of the tenant information 601. In the present exemplary embodiment, the tenant information 601 is stored in the HDD 405 of the tenant server 40, for example.

[0070] Tenant information 601 includes one or more groups. Figure 6 In the example of , tenant information 601 includes two groups, ie, group 1 and group 2, whereby group information 602 and group information 610 are managed.

[0071] Depending on the configuration of the message application 306, there may be a case where one piece of tenant information only includes one piece of group information. In this case, the tenant information 601 is the same as the group information.

[0072] Each of the group information 602 and the group information 610 includes various pieces of information constituting the group. For example, the group information 602 includes user information 603, channel information 604, printer information 606, associated application information 60, and file information 608.

[0073] The user information 603 includes information about each user belonging to the group. For example, the user information 603 includes an identifier (ID) specific to each user. The user information 603 also includes corresponding pieces of status information 609. The status information 609 is a set of information indicating what state the user is currently in, including an attendance status indicating whether the user is working in the office or at home, and a situation status indicating the user's current situation. Examples of attendance status include "in office", "at home", and "out". Examples of situation status include "available" and "away from desk". In addition to Figure 7In addition to the example shown in , various states such as "active" and "away" can also be managed. The status information 609 is not limited to the attendance status or the situation status. Various statuses can be used according to the service that manages and provides the status.

[0074] The channel information 604 is information for grouping the pieces of user information 603, and includes a list 605 that summarizes user information about users belonging to each channel. For example, the channel information 604 includes an ID specific to each channel.

[0075] The printer information 606 indicates machine information about the MFP 10. Examples of the machine information about the MFP 10 include manufacturer information, model number, serial number, media access control (MAC) address, and internet protocol (IP) address. An application using the group information 602 can send various commands to a given MFP 10 by referring to or acquiring the group information 602.

[0076] The associated application information 607 is information about applications associated with the message application 306 corresponding to group 1. Examples of applications associated with the message application 306 include various Office applications (software).

[0077] The file information 608 is information about a file stored and shared within the group. For example, when the MFP 10 prints, the file information 608 is sent to the MFP 10.

[0078] In this exemplary embodiment, a location that displays chat messages exchanged between users and is not managed as a channel is referred to as a chat room. In addition to displaying chat messages, a channel may also have other functions, such as schedule sharing. Such names are not limited to these, and channels and chat rooms may be given different names depending on the service provider.

[0079] To obtain a user list of group 1, for example, the message application 306 obtains a list of user information 603 in the group information 602 stored in the HDD 405 of the tenant server 40 via the communication unit 304 and the network 70. The message application 306 also appropriately obtains and uses the channel information 604, printer information 606, associated application information 607, file information 608, and status information 609 in a similar manner.

[0080] Figure 7 is a diagram illustrating an example of the status table 701. In the present exemplary embodiment, the status table 701 is stored in the HDD 114 of each MFP 10, for example.

[0081] The status table 701 includes parameters corresponding to the status information 609 stored in the tenant server 40. In the present exemplary embodiment, as examples of the parameters, the above-mentioned situation status is stored in the "status" column of the status table 701, the attendance status is stored in the "workplace" column, and the operation mode of the MFP 10 when each status is acquired is stored in the "mode" column. For example, when the status status is "available" and the workplace status is "in the office", the operation mode of the MFP 10 is stored in the "mode" column. Figure 7 The operation mode in the status table 701 of the MFP 10 is “printing.” As will be described below, the MFP 10 performs an operation corresponding to the operation mode based on the status table 701 .

[0082] As described herein, the "Print" operation mode refers to a mode in which the MFP 10 performs printing without spooling when receiving a FAX message. For example, the "Spool" operation mode refers to a process in which, upon receiving information including image data, the MFP 10 does not immediately print the received information including image data, but instead stores the received information including image data in the MFP 10's RAM 113 or HDD 114, or in a non-volatile area such as a cloud storage device. The HDD 114 and cloud storage device are examples of storage devices. Spooling is an example of storage processing. In response to a user's print instruction, an image based on the image data spooled by the MFP 10 is printed. Operational examples in these modes will be described below.

[0083] The status table 701 may be stored in the MFP 10 (e.g., in the HDD 114) or in an external device that can communicate with the MFP 10. In the present exemplary embodiment, the status table 701 is configured so that the user can freely specify the operation mode via the operation unit 116 of the MFP 10. However, this is not restrictive, and the status table 701 may not be modifiable.

[0084] Figure 8 701. FIG. 702 is a diagram illustrating 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. FIG.

[0085] Status item 811 corresponds to the "Status" column of status table 701. Work Location item 812 corresponds to the "Work Location" column of status table 701. The user can select an operating mode corresponding to each status by selecting selection field 813. The options selectable in selection field 813 represent operating modes that can be executed by MFP 10. If the image processing apparatus according to this exemplary embodiment is a device that does not perform recording, operating modes that can be executed by a device that performs recording based on instructions from the image processing apparatus may be included as options. If change button 814 is selected, MFP 10 updates status table 701 stored in HDD 114 with the set values. Alternatively, the operating mode selected by the user in selection field 813 may be registered when the change button 814 is not provided. The number of status tables 701 to be stored is not limited to one; multiple status tables 701 may be stored. For example, multiple status tables 701 may be named "Weekdays" and "Holidays" for easy identification. In addition to change button 814, status table setting screen 810 may include a "Register New" button (not shown). In this case, when the new registration button is selected, the MFP 10 may store a new status table 701 instead of updating the values of the existing table. The storage location of the new status table 701 may be the same as or different from the storage location (e.g., HDD 114) of the existing status table 701. The new status table 701 may be stored in any location that the CPU 111 of the MFP 10 can refer to during operation of this exemplary embodiment.

[0086] Figure 9 is a diagram illustrating an example of the recipient user table 901. In the present exemplary embodiment, the recipient user table 901 is stored in the HDD 114 of the MFP 10, for example.

[0087] The recipient user table 901 is a table that associates FAX sender information (hereinafter, simply referred to as sender information) with user information 603 about the recipient user. In this exemplary embodiment, the sender FAX number when receiving a FAX document is described as an example of sender information. The sender information is not limited to the FAX number and can be, for example, an area code, a Session Initiation Protocol (SIP) address, or a name. The recipient user is the user from whom the MFP 10 requests status information 609 from the tenant server 40. The sender FAX number refers to the FAX number of an MFP or FAX machine that is different from the MFP 10 and faxes various types of information, including image data, to the MFP 10. User information 603 refers to the above-mentioned information managed by the tenant server 40. In other words, the recipient user table 901 is a table that the MFP 10 refers to based on the sender information when receiving a FAX document. The recipient user table 901 also stores access token information corresponding to the user information 603. Instead of access token information which generally has an expiration date, the recipient user table 901 may store information related to authentication, such as user ID, email address, phone number, password, and passcode.

[0088] The recipient user table 901 can be configured to include users who receive FAX documents from senders with unregistered FAX numbers. In this exemplary embodiment, the recipient user table 901 shows an example in which "Other" is registered as the sender FAX number, as an example of receiving FAX documents from unregistered numbers. The user can register "All" (not shown) or a blank as the sender FAX number so that status information 609 about the same user is acquired in response to image data received from any FAX number. In this case, the CPU 111 of the MFP 10 receiving the FAX document can skip the process of referring to the sender information and the recipient user table 901 in the processing described below.

[0089] The user can specify only the area code of the sender FAX number, ie, the first 1 to 3 digits of the FAX number and register it in the recipient user table 901 to register a recipient user corresponding to the geographical area where the FAX sender is located.

[0090] The recipient user table 901 may be stored in the MFP 10 (e.g., in the HDD 114) or in an external device that can communicate with the MFP 10. In the present exemplary embodiment, the MFP 10 is configured to acquire sender information via various communication units. However, the MFP 10 may acquire sender information by accepting user input via the operation unit 116, for example, and register or update the recipient user table 901.

[0091] The information for identifying the sender (sender information) is not limited to the FAX number. For example, if the MFP 10 receives various types of information including image data via the network 70, the IP address or MAC address of the sender user terminal 20 can be acquired and registered in the recipient user table 901 for use in sender identification.

[0092] Figure 10 is a diagram illustrating an example of a screen for setting the recipient user table 901 . Figure 10 Illustrated are a user information addition / modification 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. The screen group is displayed on the operation unit 116 of the MFP 10.

[0093] When the unillustrated menu screen displayed on the operation unit 116 of the MFP 10 is shifted to the recipient user table setting screen via a user operation, a user information addition / modification screen 1010 is displayed on the operation unit 116 of the MFP 10 .

[0094] User information add / modify screen 1010 displays the information currently registered in recipient user table 901. Area 1011 displays information related to the current recipient user table 901. Button 1012 is an add button. When button 1012 is selected, user information add / modify screen 1010 displayed on operation unit 116 of MFP 10 transitions to user information input screen 1020.

[0095] The user information addition / modification screen 1010 may include, for example, a modification button (not shown) for modifying information registered in the recipient user table 901 and / or a deletion button (not shown) for deleting information registered in the recipient user table 901 .

[0096] The user information input screen 1020 is a screen for adding information to the recipient user table 901. The user can select an option 1021 or 1023.

[0097] An input item 1022 is an item for inputting a FAX number. If the selection item 1021 is selected, the user can input the FAX sender information to be registered into the input item 1022.

[0098] If the selection item 1023 is selected, the user can register the user information 603 about the user who received the FAX document from the sender not registered in the recipient user table 901. More specifically, when the selection item 1023 is selected, "other" is entered into the recipient user table 901.

[0099] Input item 1024 is an item for entering authentication information for authenticating user information 603. Authentication information is not limited to an ID and password; any information related to authentication can be used. Examples include an email address, a phone number, and a password. Button 1025 is a confirmation button. When this button 1025 is selected, the currently entered information is added to the recipient user table 901. When button 1025 is selected, the user information input screen 1020 displayed on the operation unit 116 of the MFP 10 changes to the user information registration completion screen 1030.

[0100] Input to input items 1022 and 1024 is performed from the operation unit 116 of the MFP 10. For example, physical buttons such as a keyboard and a numeric keypad on the operation unit 116 can be operated. A software keyboard (not shown) can be displayed on the screen of the MFP 10 and operated. The CPU 111 of the MFP 10 can detect the selection of the input item 1021 and automatically display the software keyboard (not shown), so that the user can enter the FAX number into the input item 1022 without selecting the input item 1022.

[0101] These screens can be configured so that during the "spool" operating mode, the user can also specify the storage location of various types of information, including image data received by the MFP 10. For example, the user information input screen 1020 can display a storage location selection button (not shown) to allow the user to select a storage location from one or more options, such as the HDD 114 and a cloud storage device. For example, the user information input screen 1020 can also display buttons, input fields, and / or selection fields (not shown) to set conditions for temporarily spooling image data (such as a spool time), so that the spooled data can be moved or deleted when the conditions are met.

[0102] User information registration completion screen 1030 is a screen used to notify the user that the addition of information to recipient user table 901 has been completed. When the user selects back button 1031, user information registration completion screen 1030 transitions to user information add / modify screen 1010. Alternatively, user information registration completion screen 1030 may transition to a screen displayed before user information add / modify screen 1010, such as the home screen. For example, user information registration completion screen 1030 may also display an "Add More" button (not shown) or "Yes" and "No" buttons and a message "Add More?", and if the user presses the "Add More" button or the "Yes" button, more entries can be registered. In this case, the screen may transition again to user information input screen 1020.

[0103] User information add / modify screen 1010 may include, for example, a not-shown edit button for modifying information registered in recipient user table 901. For example, the user selects one of the users displayed in area 1011 and selects the edit button, or selects the edit button and then selects one of the displayed users. CPU 111 of MFP 10 detects the pressing of the edit button and the user's selection, causing the screen to transition to user information input screen 1020 and displaying the sender information registered for the selected user in entry field 1022. User information input screen 1020 may also include a not-shown confirm button, so that when the confirm button is selected, recipient user table 901 is modified, with the input data being used as information regarding the selected user.

[0104] User information add / modify screen 1010 may include, for example, a not-shown delete button for deleting information registered in recipient data table 901. For example, the user selects one of the users displayed in area 1011 and selects the delete button, or selects the delete button and then selects one of the displayed users. CPU 111 of MFP 10 detects the selection of the delete button and the user's selection, and deletes the stored information corresponding to the selected user from recipient user table 901. Before deleting the information, for example, user information add / modify screen 1010 may display a not-shown "Execute Delete" button, or "Yes" and "No" buttons, and a message "Delete?", and if the user selects the "Execute Delete" button or the "Yes" button, the information is deleted.

[0105] As will be described below, authentication information input in input item 1024 when button 1025 is selected is sent to tenant server 40. If authentication fails due to an unregistered item or an input error by the user, notification thereof may be displayed on operation unit 116 of MFP 10.

[0106] In displaying the notification, the CPU 111 may display the user information input screen 1020 on the operation unit 116 again, display the input information again, or display a part or all of the items as blank.

[0107] As will be described below, the user information input screen 1020 may be configured so that account information about an individual user and a channel to which the user belongs may be input or the channel information 604 may be input, and the CPU 111 may accept such input.

[0108] The recipient user table 901 can be registered by performing the following processing (not shown). The user first logs in to the user account of the message application service by inputting authentication information intended for authentication of the user information 603. Alternatively, based on the user's login to the MFP 10, the CPU 111 logs in to the user account corresponding to the information about the user logged in to the MFP 10. Next, the CPU 111 of the MFP 10 communicates with the tenant server 40 to acquire information managed by the tenant server 40, such as group information 602, user information 603, channel information 604, and list 605 related to the logged-in user account. The CPU 111 finally displays the acquired information on the operation unit 116, and the user selects the user information 603 and channel information 604 from the displayed information, thereby registering the information in the recipient user table 901.

[0109] When the channel information 604 is registered in the recipient user table 901, the CPU 111 can check the status of all users in the list 605 that summarizes the user information belonging to the channel. If any user is in a state corresponding to the print mode, the CPU 111 can execute printing. In such a configuration, the user registers the authentication information of some or all users belonging to the target channel in the recipient user table 901.

[0110] Figure 11 is a diagram illustrating an example of a sequence for setting the recipient user table 901. This sequence begins 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.

[0111] [Step S1101: Input sender information]

[0112] In step 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 sender information into the input item 1021, or selects the selection item 1023, and the CPU 111 accepts the sender information.

[0113] [Step S1102: Input authentication information]

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

[0115] [Step S1103: Send Request]

[0116] In step S1103, the CPU 111 sends an access token request to the tenant server 40. When the button 1025 is selected, step S1103 is executed. When sending the access token request, the CPU 111 sends the authentication information accepted in step S1102 to the tenant server 40.

[0117] [Step S1104: Receive reply]

[0118] In step S1104, the CPU 401 of the tenant server 40 performs authentication processing using the authentication information received from the MFP 10. If authentication is successful, the CPU 401 transmits the authenticated user information 603 and access token information to the MFP 10. The CPU 111 of the MFP 10 receives this information. Successful authentication refers to the case where the authentication information received from the MFP 10 matches the authentication information registered in the HDD 405 of the tenant server 40. If authentication fails, the CPU 401 transmits a notification of authentication failure to the MFP 10. Authentication failure refers to the case where the authentication information received from the MFP 10 does not match any authentication information registered in the HDD 405 of the tenant server 40. If authentication fails, the CPU 401 does not necessarily notify the MFP 10 of the failure and may terminate or abort the process at that point. In this case, the sequence can be configured so that if the user information and access token information are not transmitted from the CPU 401 of the tenant server 40 within a predetermined time, the CPU 111 of the MFP 10 terminates the process.

[0119] [Step S1105: Generate table information]

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

[0121] Once the generation of the table information is complete, the process ends.

[0122] Figure 12 : is a flowchart illustrating an example of setting processing of the recipient user table 901 .

[0123] This process 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 process is performed appropriately based on the user's operation and the response from the tenant server 40. The steps of the flowchart according to this exemplary embodiment are performed by the CPU 111 of the MFP 10 reading a control program stored in the ROM 112 or the HDD 114 into the RAM 113 and executing the control program.

[0124] [Step S1201: Input sender information]

[0125] In step S1201, CPU 111 accepts input of FAX sender information via operation unit 116. Specifically, the user selects option 1021 and enters sender information into input item 1022, or selects option 1023, and CPU 111 accepts the sender information. The accepted sender information is temporarily stored in RAM 113. Once the input of the sender information is completed, the process proceeds to step S1202.

[0126] [Step S1202: Input authentication information]

[0127] In step S1202, CPU 111 accepts input of authentication information via operation unit 116. Specifically, the user enters authentication information into input item 1024, and CPU 111 accepts the authentication information. The accepted authentication information is temporarily stored in RAM 113. Once the input of authentication information is completed and the user selects button 1025, the process proceeds to step S1203.

[0128] [Step S1203: Send Request]

[0129] In step S1203, the CPU 111 sends an access token request to the tenant server 40. When sending the access token request, the CPU 111 also sends the sender information and authentication information received in steps S1201 and S1202 and temporarily stored in the RAM 113 to the tenant server 40. Once the request is sent, the process proceeds to step S1204.

[0130] [Step S1204: Authentication Confirmation]

[0131] In step S1204, the CPU 111 waits for a response from the tenant server 40. An example of a response sent from the tenant server 40 is a notification indicating whether the authentication is successful or failed. If the authentication is successful, the response also includes user information and access token information. The CPU 111 detects the receipt of the response from the tenant server 40. If the authentication is successful based on the received response ("Yes" in step S1204), the CPU 111 temporarily stores the user information and access token information received from the tenant server 40 in the RAM 113, and the process proceeds to step S1205. If the authentication is unsuccessful based on the response received from the tenant server 40 ("No" in step S1204), the CPU 111 determines that the registration in the recipient user table 901 has failed, and the process ends.

[0132] [Step S1205: Add user information]

[0133] In step S1205 , the CPU 111 associates the sender information, user information, and access token information temporarily stored in the RAM 113 , and adds the respective pieces of information to the recipient user table 901 .

[0134] Once the addition of the user information is completed, the process ends. After the process of step S1205 ends, the CPU 111 deletes the sender information temporarily recorded in step S1201 from the RAM 113.

[0135] Figure 13 This diagram illustrates an example of a sequence for spooling a FAX job based on status table 701. This sequence begins when the MFP 10 receives a FAX job via its FAX communication unit 124. A FAX job is a job that, in addition to FAX reception, performs a series of processes until image data received via FAX is recorded on a recording medium. This sequence describes the processes performed by the MFP 10, tenant server 40, and message application server 30. Recipient user table 901 according to this exemplary embodiment stores the sender FAX number, recipient user, and access token information in association with one another.

[0136] [Step S1301: Receiving FAX Job]

[0137] In step S1301 , the CPU 111 of the MFP 10 executes analysis processing on the FAX job information received via the FAX communication unit 124 , and stores FAX sender information in the RAM 113 .

[0138] [Step S1302: Refer to the Recipient User Table]

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

[0140] [Step S1303: Requesting Status Information]

[0141] In step S1303 , the CPU 111 transmits the access token information corresponding to the sender information acquired in step S1302 to the tenant server 40 , and requests the status information 609 on the recipient user corresponding to the access token information.

[0142] [Step S1304: Receiving Status Information]

[0143] In step S1304, the CPU 401 of the tenant server 40 acquires the status information 609 on the user 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 status information 609 on the user requested by the MFP 10 is successfully acquired, the CPU 401 transmits the status information 609 on the user requested by the MFP 10 to the MFP 10. The CPU 111 of the MFP 10 receives the status information 609.

[0144] [Step S1305: Refer to Status Table]

[0145] In step S1305, the CPU 111 acquires the operating mode information (operation mode) corresponding to the status information 609 received in step S1304 based on the status table 701 stored in the HDD 114. The CPU 111 stores the status information 609 transmitted from the tenant server 40 in step S1304 in the HDD 114. In step S1402 described below, the status information 609 stored here is referenced. The following sequence is performed on the premise that the acquired operation mode is "spooling."

[0146] [Step S1306: Spooling Image Data]

[0147] In step S1306, in order to move the received FAX job information to the non-volatile area, the CPU 111 moves the FAX job information from the RAM 113 to the HDD 114. This control will be referred to as spool control. The spool control refers to a process (storage process) of storing the received information including image data in the RAM 113 of the MFP 10 or a non-volatile area such as the HDD 114 when the MFP 10 receives the information including image data without immediately printing the image data. An image based on the image data spooled by the MFP 10 is printed in response to a print instruction from the user. The moving destination is not limited to the HDD 114 of the MFP 10, and may be an external non-volatile area (storage device) such as a cloud storage device and a flash memory. By storing the image data received via FAX in the non-volatile area through the spool control, the FAX job information can be retained without being lost even if subsequent processing is interrupted due to an event such as a power outage or power failure of the MFP 10. For example, if FAX job information is stored in a cloud storage device, users with access permission can browse the FAX job information through the cloud service. This enables ubiquitous access, thereby improving convenience.

[0148] [Step S1307: Chat execution request]

[0149] In step S1307, the CPU 111 generates a chat execution request for the recipient user corresponding to the received FAX sender information based on the access token information acquired in step S1302. Next, the CPU 111 transmits the chat execution request (send instruction) to the messaging application server 30. The chat message that the CPU 111 requests to be published is "MFP 10 has received a FAX document, and image data is spooled."

[0150] [Step S1308: Posting a chat message]

[0151] In step S1308, the CPU 301 of the messaging application server 30 sends a notification of the chat execution request issued in step S1307 and a chat message to the user terminal 20. The notification and chat message may be sent actively by the CPU 301 of the messaging application server 30, or passively, for example, based on a timeline acquisition request from the user terminal 20. The messaging application 306 installed on the HDD 210 of the user terminal 20 sends the chat message (chat message 1503; see Figure 15 ) is displayed on the operation panel 201 of the user terminal 20 to notify the recipient user.

[0152] The chat message notified in step S1308 may include a portion of the FAX job information. For example, the chat message 1503 includes FAX sender information. When the chat execution request is issued in step S1307, the MFP 10 also transmits the FAX job information so that the message application server 30 can acquire the FAX job information.

[0153] Figure 14 This diagram illustrates an example of a sequence for printing an image based on spooled image data based on a change in status. This sequence represents the processing that occurs when, in step S1307 or later, CPU 111 detects a change in status information 609 regarding the same user and, based on status table 701, finds that the operation mode corresponding to the changed status information 609 is "Print." The status can be manually input and updated through user operation of user terminal 20 via message application 306, or automatically estimated and updated based on information such as the update history of tenant information 601 and the operation history of user terminal 20. This processing is performed without requiring a print instruction from the user. This sequence describes the processing performed by MFP 10, tenant server 40, and message application server 30.

[0154] [Step S1401: Requesting Status Information]

[0155] In step S1401, the CPU 111 of the MFP 10 transmits the access token information acquired from the recipient user table 901 in step S1302 to the tenant server 40 and requests status information. The status information 609 requested in step S1401 is the status information 609 regarding the recipient user corresponding to the sender information regarding the image data spooled in step S1306. The CPU 111 may request the status information 609 regarding all users stored in the tenant server 40.

[0156] [Step S1402: Receiving Status Information]

[0157] In step S1402, the CPU 401 of the tenant server 40 acquires the status information 609 about the user 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 status information 609 about the user requested by the MFP 10 is successfully acquired, the CPU 401 transmits the status information 609 about the user requested by the MFP 10 to the MFP 10. The CPU 111 of the MFP 10 receives the status information 609. If the status information 609 transmitted from the tenant server 40 is different from the status information 609 received in step S1304, the CPU 111 of the MFP 10 determines that a change has been detected and executes the processing of step S1403.

[0158] [Step S1403: Refer to Status Table]

[0159] In step S1403, the CPU 111 acquires operation mode information corresponding to the status information 609 acquired in step S1402 based on the status table 701 stored in the HDD 114. The following sequence is performed on the premise that the mode indicated by the acquired operation mode information is "printing".

[0160] [Step S1404: Checking Spooled Image Data]

[0161] In step S1404, the CPU 111 searches for image data received by the MFP 10 and spooled in the HDD 114 by the spool control of step S1306. Although the spool control is performed in step S1306, if, for example, the user operates the operation unit 116 of the MFP 10 and prints the spooled image data before the status information 609 is updated, there may be no spooled image data in step S1404.

[0162] [Step S1405: Printing an Image Based on the Spooled Image Data]

[0163] In step S1405, CPU 111 prints an image based on the image data received and spooled by MFP 10, as searched in step S1404. More specifically, printing unit 120 of MFP 10 records an image based on the image data received according to the FAX job received by MFP 10 in step S1301 on a recording medium. Printing on a recording sheet is an example of this. For example, if the image data received by MFP 10 in step S1306 is spooled not in HDD 114 but in a cloud storage device, MFP 10 retrieves the image data from the spooled cloud storage device and prints the image data. Step S1405 is executed without requiring a print instruction from the user. MFP 10 can execute a print process for printing an image based on the image data received by MFP 10 via FAX in response to a print instruction from the user.

[0164] [Step S1406: Chat Execution Request]

[0165] In step S1406, the CPU 111 generates a chat execution request for the recipient user corresponding to the sender information regarding the received FAX job based on the access token information acquired from the recipient user table 901 in step S1302. Next, the CPU 111 transmits the chat execution request (send instruction) to the message application server 30. The chat message that the CPU 111 requests to be published is "The MFP has received the FAX document, and printing of the image based on the spooled FAX-received image data is complete."

[0166] [Step S1407: Posting Chat Message]

[0167] In step S1407 , the CPU 301 of the message application server 30 transmits a notification to the user terminal 20 that the chat execution request is issued from the MFP 10 in step S1406 .

[0168] The notification may be actively sent by the CPU 301 of the message application server 30, or may be passively sent, for example, based on a timeline acquisition request from the user terminal 20. The message application 306 installed on the HDD 210 of the user terminal 20 displays the chat message (chat message 1504) received from the message application server 30 on the operation panel 201 of the user terminal 20 to notify the recipient user.

[0169] Upon completing issuance of the chat message request in step S1406, the CPU 111 ends the processing.

[0170] Notification to the recipient user in steps S1405 and S1406 is not essential, and the MFP 10 does not necessarily need to issue a notification to print the spooled image data.

[0171] The status information 609 requested in step S1401 may be information on the status of the user corresponding to the sender information on the image data remaining in the HDD 114, rather than information on the status of the user corresponding to the sender information on the image data spooled in step S1306. In this case, for example, the processing of steps S1404 and S1608 described below may be omitted because a job that is cleared by the user operating the operation unit 116 of the MFP 10 to print the spooled image data before the status information 609 is updated will not be processed.

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

[0173] A display field 1501 displays information about the user. A chat screen 1500 is a screen used by user A. A display field 1502 displays a list of chat partners having chat records. The chat screen 1500 displays a chat screen with the MFP 10 .

[0174] Chat message 1503 is the chat message posted in step S1308 and is an example of a chat message for notifying the user that the MFP 10 has received the FAX document and that the image data has been spooled. Chat message 1504 is the chat message posted in step S1407 and is an example of a chat message for notifying the user that the spooled image data has been printed.

[0175] The types and layouts of the pieces of information displayed on the chat screen 1500 are merely examples and may differ from the examples depending on the provider of the message application 306 and the user who customizes the message application 306 .

[0176] The MFP 10 may be configured to accept a user's print instruction from the chat screen 1500, so that the user can instruct the MFP 10 to print an image based on the spooled image data via the chat screen 1500. With such a configuration, when the MFP 10 spools the image data received by the MFP 10, the recipient user corresponding to the sender information can send a print instruction to the MFP 10 that is performing the spooling process via the chat screen 1500. Upon receiving the print instruction, the MFP 10 prints the image based on the image data spooled in the HDD 114 using, for example, the printing unit 120.

[0177] If a plurality of MFPs 10 are connected and can transfer spooled image data to each other, the user can send a print instruction to any one of the MFPs 10, such as the MFP 10 closest to the user's current location.

[0178] The print instruction from the user of the chat screen 1500 can be issued using a software button displayed by the message application 306 or a physical button on the user terminal 20. The print instruction can be given by the user replying a sentence such as "Print it" in the chat. The user terminal 20 may include a gyro sensor, for example, and may be configured to send a print instruction to the MFP 10 in response to a specific action of the user (such as shaking) after displaying the chat message 1503.

[0179] Figure 16 1 is a flowchart illustrating an example of processing of a FAX job received by the MFP 10. Specifically, Figure 16 Illustrated is a process in which the MFP 10 spools or prints received image data based on the acquired status information 609 about the user and the status table 701. This process is started by the MFP 10 receiving a FAX job via the FAX communication unit 124.

[0180] [Step S1601: Receiving FAX Job]

[0181] In step S1601, the CPU 111 of the MFP 10 temporarily stores the received FAX job information in the RAM 113. Upon completion of reception of the FAX job, the process proceeds to step S1602.

[0182] [Step S1602: Searching for User Information]

[0183] In step 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 about the FAX job information stored in the RAM 113 in step S1601. Upon completing the search for the user information 603, the process proceeds to step S1603.

[0184] [Step S1603: Confirmation of User Information Found]

[0185] In step S1603, the CPU 111 of the MFP 10 determines whether the user information 603 corresponding to the sender information is found in the recipient user table 901 in step S1602. If the CPU 111 determines that the user information 603 corresponding to the sender information is found in the recipient user table 901 ("YES" in step S1603), the process proceeds to step S1604. If the CPU 111 determines that the user information 603 corresponding to the sender information is not found in the recipient user table 901 ("NO" in step S1603), the process proceeds to step S1612 regardless of the information in the recipient user table 901.

[0186] [Step S1604: Requesting Status Information]

[0187] In step S1604, the CPU 111 of the MFP 10 acquires access token information corresponding to the found user information 603 from the recipient user table 901. The CPU 111 further sends the access token information to the tenant server 40 and requests status information 609. Upon completing the request for status information 609, the process proceeds to step S1605.

[0188] [Step S1605: Determination of Acquisition Status Information]

[0189] In step S1605, the CPU 111 of the MFP 10 waits until the status information 609 is transmitted from the tenant server 40. If the CPU 111 determines that the status information 609 is transmitted from the tenant server 40 and is successfully acquired ("YES" in step S1605), the process proceeds to step S1606. If the CPU 111 determines that the status information 609 has not been successfully acquired ("NO" in step S1605), the process returns to step S1605 and the CPU 111 continues to wait.

[0190] [Step S1606: Search Status Table]

[0191] In step 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 step S1605 , and acquires the operation mode.

[0192] [S1607: Determine the operation mode]

[0193] In step S1607, the CPU 111 of the MFP 10 determines whether the operation mode corresponding to the status information 609 acquired in step S1606 is "spool" or "print." If the CPU 111 determines that the operation mode corresponding to the acquired status information 609 is "spool" ("No" in step S1607), the process proceeds to step S1608. If the CPU 111 determines that the operation mode corresponding to the acquired status information 609 is "print" ("Yes" in step S1607), the process proceeds to step S1611.

[0194] [Step S1608: Determine whether the spooling process is completed]

[0195] In step S1608, the CPU 111 of the MFP 10 determines whether the spooling process of the FAX job being processed is completed. If the CPU 111 determines that the spooling process of the FAX job being processed is completed ("YES" in step S1608), the process proceeds to step S1604. If the CPU 111 determines that the spooling process of the FAX job being processed is not completed ("NO" in step S1608), the process proceeds to step S1609.

[0196] [Step S1609: Spooling Process]

[0197] In step S1609, the CPU 111 of the MFP 10 moves the FAX job information stored in the RAM 113 in step S1601 to the HDD 114 to perform spooling of the image data. Upon completion of the spooling of the image data, the process proceeds to step S1610.

[0198] [Step S1610: Notification of “Completion of Spooling”]

[0199] In step S1610, the CPU 111 of the MFP 10 notifies the message application server 30 that the image data has been spooled by the MFP 10. In other words, in step S1610, the CPU 111 issues a chat message 1503 to the user via the message application server 30 and the message application 306. Once the notification of "spooling completion" is completed, the process proceeds to step S1604. This notification is sent to the chat room corresponding to the user who acquired the status information 609.

[0200] [Step S1611: Determine whether the spooling process is completed]

[0201] In step S1611, the CPU 111 of the MFP 10 determines whether the spooling process of the FAX job being processed is completed. If the CPU 111 determines that the spooling process of the FAX job being processed is not completed ("No" in step S1611), the process proceeds to step S1612. If the CPU 111 determines that the spooling process of the FAX job being processed is completed ("YES" in step S1611), the process proceeds to step S1613.

[0202] [Step S1612: Printing]

[0203] In step S1612, the CPU 111 of the MFP 10 issues an instruction to print an image based on the image data stored in the RAM 113 in step S1601, and the printing unit 120 prints the image. Upon completion of printing, the process proceeds to step S1615.

[0204] [Step S1613: Determine whether there is remaining spooled image data]

[0205] In step S1613, the CPU 111 of the MFP 10 determines whether the image data stored by the spooling process in step S1609 remains in the HDD 114. If the CPU 111 determines that the image data stored by the spooling process remains in the HDD 114 ("YES" in step S1613), the process proceeds to step S1614. If the CPU 111 determines that the image data stored by the spooling process does not remain in the HDD 114 ("NO" in step S1613), the process proceeds to step S1615. Examples of reasons why the image data stored by the spooling process does not remain in the HDD 114 include the user directly operating the operation unit 116 in the MFP 10 to print an image based on the image data and quitting printing.

[0206] [Step S1614: Printing an Image Based on the Spooled Image Data]

[0207] In step S1614, the CPU 111 of the MFP 10 issues an instruction to print an image based on the image data stored in the HDD 114 by spooling, and the printing unit 120 prints the image. Once the printing of the image based on the spooled image data is completed, the process proceeds to step S1615. When the image based on the spooled image data is printed by the MFP 10, the CPU 111 deletes the spooled image data. This deletion is not essential, and the spooled image data may continue to remain even after the MFP 10 prints the image based on the spooled image data.

[0208] [Step S1615: Notification of “Completion of Printing”]

[0209] In step S1615, the CPU 111 of the MFP 10 notifies the message application server 30 that the MFP 10 has completed printing. In other words, in step S1615, the CPU 111 publishes a chat message 1504 to the user via the message application server 30 and the message application 306. This notification is sent to the chat room corresponding to the user who acquired the status information 609. Once the notification of "printing completion" is complete, the process ends. Upon completion of step S1615, the CPU 111 deletes the sender information temporarily recorded in step S1601 from the RAM 113.

[0210] With the above configuration, the job received by the MFP 10 can be printed or spooled with reference to the status table 701, the recipient user table 901, and the status information 609 stored in the tenant server 40. The MFP 10 can perform printing by detecting changes in the status information 609 stored in the tenant server 40.

[0211] Conventionally, if an MFP performs spooling of received image data, the spooled image data is printed in response to a user action such as operating the MFP to issue a print instruction, sending a print instruction in a chat, and bringing the user terminal close to the MFP.

[0212] According to this exemplary embodiment, if the image data is spooled, the image processing apparatus detects the change in status information 609 as specific status information 609 indicating that the user can immediately receive a printout, and prints an image based on the image data without requiring any user operation. Therefore, in a case where the user can immediately receive a printout, this exemplary embodiment can provide an effect of reducing the workload of printing an image of the received image data.

[0213] In the case where the recipient user cannot immediately receive the FAX document received by the MFP 10, such as when the recipient user is absent, the FAX document is not printed immediately after being received. This provides an effect of ensuring security in terms of information security.

[0214] In the present exemplary embodiment, as described above, the operating mode of the MFP 10 is associated with the situation status and the presence status as the situation information 609. However, the situation information 609 may include only the situation status, and there may be cases where this can provide the effects of the present exemplary embodiment. However, in order to enhance the effects of the present exemplary embodiment, it is desirable to use multiple indicators of different attributes for the situation information 609, as in the present exemplary embodiment.

[0215] In the present exemplary embodiment, the recipient user table 901 is configured so that user information 603 is registered therein. However, channel information 604 may be registered instead of the user information 603. This configuration makes it possible to check the status of all users in the list 605 that summarizes the user information belonging to the channel information 604, and if any one user is in a state corresponding to the print mode, printing is possible. With such a configuration, the user registers authentication information about some or all users belonging to the target channel in the recipient user table 901. As described above, the MFP 10 acquires and registers access token information about each user, and acquires status information 609 about each user. The user can register the channel information 604 in the recipient user table 901 by inputting a channel ID. In such a configuration, the MFP 10 issues a chat execution request not to individual users but to a shared channel (such as a group chat).

[0216] In this configuration, when one of the users in the list 605 that summarizes the user information belonging to the channel information 604 sends a print instruction to the MFP 10 via the chat screen 1500, the MFP 10 can print. In the present exemplary embodiment, the MFP 10 is configured to execute the process for acquiring the status information 609 in step S1304 with the reception of the FAX job in step S1301 as a trigger. However, the MFP 10 may be configured to periodically acquire the status information 609 before receiving the FAX job and store the status information 609 in the HDD 114. This allows the sequence to be continued without accessing the tenant server 40.

[0217] If the recipient user of image data received by the MFP 10 can be identified or the cloud service can be accessed without authentication information, then access token information may not necessarily be handled. For example, if the cloud service manages users using only user-specific IDs without authentication, the user's ID can be registered in the recipient user table 901 instead of the access token information. In this case, the authentication information-related processing in steps S1102 to S1104, S1201 to S1204, S1303, and S1401 according to this exemplary embodiment can be omitted.

[0218] If there are cases where users may be able to immediately receive printouts and cases where they may not, the workload of the image processing apparatus in printing images based on image data received via FAX can be reduced.

[0219] Other embodiments

[0220] The (one or more) embodiments of the present disclosure may also be implemented by a computer reading out and executing computer-executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be more fully referred to as a "non-transitory computer-readable storage medium") to perform the functions of one or more of the above-mentioned (one or more) embodiments and / or a system or device including one or more circuits (e.g., application-specific integrated circuits (ASICs)) for performing the functions of one or more of the above-mentioned (one or more) embodiments, and by a method executed by a computer of the system or device, for example, by reading out and executing computer-executable instructions from a storage medium to perform the functions of one or more of the above-mentioned (one or more) embodiments and / or controlling one or more circuits to perform the functions of one or more of the above-mentioned (one or more) embodiments. The computer may include one or more processors (e.g., a central processing unit (CPU), a microprocessing unit (MPU)), and may include a network of separate computers or separate processors to read out and execute computer-executable instructions. The computer-executable instructions may be provided to the computer, for example, from a network or a storage medium. The storage medium may include, for example, a hard disk, a random access memory (RAM), a read-only memory (ROM), a storage device of a distributed computing system, an optical disk (such as a compact disk (CD), a digital versatile disk (DVD), or a Blu-ray disk (BD)). TM ), one or more of flash memory devices, memory cards, etc.

[0221] Other embodiments

[0222] The embodiments of the present invention can also be implemented by the following method, that is, providing software (program) that performs the functions of the above-mentioned embodiments to a system or device through a network or various storage media, and the computer or central processing unit (CPU) or microprocessing unit (MPU) of the system or device reads and executes the program.

[0223] While the present disclosure has been described with reference to exemplary embodiments, it is to be understood that the present disclosure is not limited to the disclosed exemplary embodiments. The scope of the following claims is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structures and functions.

Claims

1. An image processing device, comprising: a modem configured to receive image data via facsimile (FAX); one or more memories storing one or more programs, and one or more processors executing the programs to cause the image processing apparatus to acquire status information indicating a status of a user from a chat service; as well as a printer configured to print an image based on the received image data on a recording medium, wherein the processor causes the image processing apparatus to acquire status information about a user corresponding to sender information about received image data, and The printer is configured to, based on the acquisition of the specific status information, print an image based on the received image data on a recording medium without the image processing apparatus accepting a print instruction from a user after the status information is acquired. 2 . The image processing apparatus according to claim 1 , wherein the image processing apparatus performs different processing according to the acquired situation information.

3. An image processing apparatus according to claim 2, wherein, in a case where the acquired status information is the specific status information, a printing process for printing an image based on the received image data on a recording medium is performed, and in a case where the acquired status information is not the specific status information, a storage process for storing the received image data in a storage device is performed. 4 . The image processing apparatus according to claim 3 , wherein a printing process is not executed until the acquisition of the specific status information. 5 . The image processing apparatus according to claim 4 , wherein the received image data is stored in a storage device until the specific situation information is acquired. 6 . The image processing apparatus according to claim 5 , wherein the image processing apparatus is configured to accept a user's setting of the specific situation information.

7. The image processing apparatus according to claim 1, further comprising a communicator, The communicator is configured to send a notification sending instruction to the chat server via the network. 8 . The image processing apparatus according to claim 7 , wherein the notification transmission instruction is an instruction to transmit a notification of processing contents of the image processing apparatus. 9 . The image processing apparatus according to claim 8 , wherein the notification is a notification to execute a storage process for storing the received image data in a storage device, the storage process being executed if the acquired status information is not the specific status information.

10. The image processing apparatus according to claim 8, wherein the notification is a notification to execute a printing process for printing an image based on the received image data on a recording medium, the printing process being executed if the acquired status information is the specific status information. 11 . The image processing apparatus according to claim 8 , wherein the notification is sent to a chat room corresponding to the user about whom the status information is acquired. 12 . The image processing apparatus according to claim 8 , wherein the notification is sent to a channel to which the user about whom the status information is acquired belongs. The image processing apparatus according to claim 8 , wherein the notification is presented in a chat. 14 . The image processing apparatus according to claim 1 , wherein the image processing apparatus is configured to accept a print instruction from an external apparatus configured to communicate with the image processing apparatus via a network.

15. The image processing apparatus according to claim 1, The processor enables the image processing device to accept a print instruction. 16 . The image processing apparatus according to claim 1 , wherein the processor causes the image processing apparatus to acquire status information about a user belonging to a channel associated with sender information about the received image data. 17 . The image processing apparatus according to claim 1 , wherein the printer is configured to print an image based on received image data on a recording medium, the image data being received from a cloud storage apparatus.

18. An image processing method for an image processing device, the method comprising: Receiving image data via fax (FAX); Obtaining status information indicating the user's status from the chat service; as well as printing an image based on the received image data on a recording medium, wherein situation information about a user corresponding to sender information about received image data is acquired, and Based on the acquisition of the specific status information, an image based on the received image data is printed on a recording medium without the image processing apparatus accepting a print instruction from a user after the status information is acquired.

19. A program product storing a program for causing an image processing apparatus to execute an image processing method, the image processing method comprising: Receiving image data via fax (FAX); Obtaining status information indicating the user's status from the chat service; as well as printing an image based on the received image data on a recording medium, wherein situation information about a user corresponding to sender information about received image data is acquired, and Based on the acquisition of the specific status information, an image based on the received image data is printed on a recording medium without the image processing apparatus accepting a print instruction from a user after the status information is acquired.

Images