Information processing method, program, and information processing device

Abstract

To prevent unnecessary information from being displayed in displaying information for inputting an instruction to print data based on the uploading of the data to a chat room.SOLUTION: An information processing method includes: a display step of displaying, in a chat room, information for inputting an image formation instruction for executing image forming processing based on data uploaded to the chat room; and an image formation control step of, on the basis of the image formation instruction input by using the displayed information, causing an image forming apparatus to execute the image formation processing based on the data. The display step includes not to display the information on the basis of the state of the image forming apparatus.SELECTED DRAWING: Figure 12

Description

[Technical Field]

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

[0002] Patent Document 1 describes a device that operates a chatbot that responds to a user's post on a chat service, sends the uploaded image data to a printer, and causes the printer to print the image data. [Prior art documents] [Patent documents]

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

[0004] The chatbot described in Patent Document 1 causes a printer to print image data in accordance with a specific message (print instruction) posted by a user on a chat. Alternatively, a configuration is conceivable in which a message is displayed to confirm whether or not to have the printer print image data when image data is uploaded to the chat. In this case, the uploaded image data is printed by the printer when the user inputs a print instruction in response to the message.

[0005] When posting a message on a chat to confirm whether to have the printer print the image data that has been posted, the following problems can be considered: For example, if the message is displayed even when the printer is unable to print, an unnecessary message will be displayed.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to prevent unnecessary information from being displayed when displaying information for inputting a print instruction for data uploaded to a chat room. [Means for solving the problem]

[0007] The information processing method of the present invention includes: a step of inputting an image formation instruction for executing an image formation process based on data uploaded to a chat room; button a display step of displaying the displayed message in the chat room; button and an image forming control step of causing an image forming apparatus to execute the image forming process based on the data based on an image forming instruction input using the button is characterized in that it does not display. [Effects of the Invention]

[0008] According to the present invention, when information for inputting a print instruction for data uploaded to a chat room is displayed, unnecessary information can be prevented from being displayed. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration of the present invention. [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. 1 shows an example of a hardware configuration of an application data server 50. [Figure 7]FIG. 6 is a diagram showing an example of tenant information 601 stored in the tenant server 40. [Figure 8] FIG. 10 is a diagram showing an example of a message screen displayed on the operation panel 201 of the user terminal 20. [Figure 9] FIG. 10 is a diagram showing an example of a message screen displayed on the operation panel 201 of the user terminal 20. [Figure 10] FIG. 10 is a diagram showing an example of a message screen displayed on the operation panel 201 of the user terminal 20. [Figure 11] A diagram showing an example of MFP status information [Figure 12] 10 is a flowchart showing an example of a print suggestion process performed by the cooperative application A506. [Figure 13] A sequence diagram illustrating an example of a process for posting a message for a printing suggestion. [Figure 14] FIG. 10 is a sequence diagram illustrating an example of a process for registering an MFP in a tenant server 40. [Figure 15] FIG. 10 shows an example of a process in which a cooperative application A506 installed on the message application server 30 receives a print request from a user and the MFP executes printing. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the configurations shown in the following embodiments are merely examples, and the present invention is not limited to the configurations shown in the drawings.

[0011] 1 is a diagram showing an example of a system configuration of the present invention. In the message application service, MFPs (Multi Function Peripherals) 10 and 11, which are image processing devices or image forming devices, and user terminals 20 to 22 are configured as clients. The server side is configured with a message application server 30, a tenant server 40, and an application data server 50.

[0012] MFPs 10 and 11 are image forming devices that have the function of printing images received from message application server 30 or the function of sending image data generated by scanning to message application server 30. While Figure 1 shows an example in which two MFPs are connected, any number of MFPs can be connected. MFPs 10 and 11 have the same configuration, and the following description will focus on MFP 10.

[0013] User terminals 20-22 refer to information processing devices such as smartphones, tablet terminals, and personal computers used by users of the message application service. While FIG. 1 shows an example in which three user terminals 20-22 are connected, any number of connections may be used. A user operates one of the user terminals 20-22 to access a message application server 30 on the cloud, exchange messages with other users, and run installed applications. The user terminals 20-22 and the message application server 30 are connected to a wired or wireless communication network, enabling data transmission and reception between them. In this embodiment, a public line on the Internet is assumed as an example of a communication network, but a dedicated line may also be used. The user terminals 20-22 can have the same configuration, and the following description will focus on user terminal 20.

[0014] 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 and image data to and from the user terminals 20 to 22, and displaying chat room screens. The message application server 30 can process messages and other exchanges between two members, as well as form a group of three or more members and process messages and other exchanges within the group.

[0015] 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. 7.

[0016] The application data server 50 is a cloud server located on the cloud 60, and stores data of the cooperative application A506 that can be installed in the message application 306. In this embodiment, the application data is stored in the application data server 50, but the data of the cooperative application A506 may be downloaded from a network outside the cloud.

[0017] 2 is a diagram showing an example of the hardware configuration of MFP 10. MFP 10 includes a CPU 111, a ROM 112, a RAM 113, a storage 114, an operation unit I / F 115, and an operation unit 116. MFP 10 also includes a reading unit I / F 117, a reading unit 118, a printing unit I / F 119, a printing unit 120, a wireless communication unit I / F 121, a wireless communication unit 122, a communication unit I / F 123, and a communication unit 124.

[0018] The control unit 110, including the CPU 111, controls the overall operation of the MFP 10. The CPU 111 loads control programs stored in the ROM 112 or storage 114 into the RAM 113 to perform various types of control, such as reading control and printing control (image formation 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 a main memory and is used as a work area and a temporary storage area for expanding the various control programs stored in the ROM 112 and storage 114. The storage 114 stores image data, print data, various programs, various addresses, and various setting information. In this embodiment, a flash memory is assumed as the storage 114, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may also be used. An eMMC (Embedded Multi Media Card) may also be used.

[0019] 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 shown in the flowcharts described below can be executed by multiple CPUs, RAMs, ROMs, and storages working together. Also, some processes can be executed using hardware circuits such as ASICs and FPGAs.

[0020] An operation unit I / F 115 connects an operation unit 116 including a display unit such as a touch panel and hard keys to the control unit 110. The operation unit 116 displays a screen and receives input from a user.

[0021] The reading unit I / F 117 connects the control unit 110 to a reading unit 118, such as a scanner. The reading unit 118 reads an image of a document, and the CPU 111 converts the image into image data such as binary data. The image data generated based on the image read by the reading unit 118 is sent to an external device or printed on paper.

[0022] The printing unit I / F 119 connects the control unit 110 to a printing unit 120, such as a printer. The CPU 111 transfers image data (print data) stored in the RAM 113 to the printing unit 120 via the printing unit I / F 119. The printing unit 120 prints an image based on the transferred image data on paper fed from a paper feed cassette.

[0023] The wireless communication unit I / F 121 is an I / F for controlling the wireless communication unit 122, and connects the control unit 110 to an external wireless device via wireless communication. A configuration may be adopted in which a user terminal 20 is used as the external wireless device.

[0024] The communication unit I / F 123 is an I / F for controlling the communication unit, and is connected to the control unit 110 and the communication unit 124. The communication unit 124 transmits image data and various internal information of the device to external devices on the network 100, and receives print data and information on the network 100 from information processing devices on the network 100. Methods for transmitting and receiving data via the network 100 include transmission and reception using electronic mail (E-mail) and file transmission using other protocols (e.g., FTP, SMB, WEBDAV, etc.). Furthermore, image data and various setting data can be transmitted and received over the network 100 by accessing via HTTP communication from the user terminal 20 or the message application server 30.

[0025] 3 is a diagram showing an example of the hardware configuration of the user terminal 20. Note that the user terminal 20 of this embodiment is assumed to be a client terminal of a device such as a smartphone or a PC.

[0026] The CPU 207 reads out a control program stored in the ROM 208 and executes various processes for controlling the operation of the user terminal 20. The ROM 208 stores the control program. The RAM 209 is used as a temporary storage area such as the main memory and work area of ​​the CPU 207. The HDD 210 stores various data such as photographs and electronic documents.

[0027] The operation panel 201 has a touch panel function capable of detecting a user's touch operation, and displays various screens provided by the OS and an email sending application. The operation panel 201 is also used to check information stored in the message application server 30. The user can input desired operation instructions to the user terminal 20 by inputting touch operations on the operation panel 201. The user terminal 20 is also equipped with hardware keys (not shown), and the user can use these hardware keys to input operation instructions to the user terminal 20. The user can also connect a keyboard, mouse, etc. to the user terminal 20 to perform desired operations.

[0028] Camera 204 takes an image in response to an image capture instruction from the user. The photograph taken by camera 204 is stored in a predetermined area of ​​HDD 210. In addition, it is possible to obtain information from the QR code read by camera 204 using a program capable of analyzing QR codes (registered trademark).

[0029] The user terminal 20 can transmit and receive data to and from various peripheral devices via an NFC communication unit 205, a Bluetooth (registered trademark) communication unit 206, and a wireless LAN communication unit 211. The Bluetooth communication unit 206 of the user terminal 20 may be compatible with Bluetooth Low Energy.

[0030] FIG. 4 is a diagram illustrating an example of the hardware configuration of the message application server 30. The CPU 301 reads a control program stored in the ROM 302 and a message application 306 stored in the HDD 305, and executes various processes for controlling the operation of the message application server 30. The ROM 302 stores the control program. The RAM 303 is used as a temporary storage area such as the main memory and work area of ​​the CPU 301. The HDD 305 stores various data such as messages, images, channel information, and applications. Data can be transmitted and received 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 (registered trademark) or wireless communication such as Wi-Fi. The message application 306 is installed in the HDD 305 and runs on the CPU 301.

[0031] FIG. 5 is a diagram showing an example of the hardware configuration of the tenant server 40. The CPU 401 reads out a control program stored in the ROM 402 and executes various processes for controlling the tenant information 601. The stored tenant information 601 will be described later. The ROM 402 stores the control program. The RAM 403 is used as a temporary storage area such as the main memory and work area of ​​the CPU 401. The HDD 405 stores the tenant information 601 and the like. Data can be sent and received to and from devices such as the message application server 30 via the communication unit 404. The communication unit 404 may perform wired communication using Ethernet (registered trademark) or wireless communication such as Wi-Fi.

[0032] FIG. 6 is a diagram showing an example of the hardware configuration of the application data server 50. The CPU 501 reads out a control program stored in the ROM 502 and executes various processes for controlling the application data server 50. The ROM 502 stores the control program. The RAM 503 is used as a temporary storage area such as the main memory and work area of ​​the CPU 501. The HDD 505 stores linked application data A506 to C508. The communication unit 504 can transmit and receive data to and from devices such as the message application server 30. The linked applications A506 to C508 are applications that operate in cooperation with the message application 306 and are stored in the HDD 505. These linked applications A506 to C508 are sent to the message application server 30 via the communication unit 504 in response to a command and installed in the message application server 30. At this time, the linked applications A506 to C508 are installed in the HDD 305 of the message application server 30.

[0033] Fig. 7 is a diagram showing an example of tenant information 601 stored in the HDD 405 in the tenant server 40. One or more groups are associated with the tenant information 601, and in the example of Fig. 7, there are two groups: group 1 (602) and group 2 (609). Depending on the configuration of the message application 306, one piece of tenant information may contain only one piece of group information, in which case the tenant information 601 and the group information will be equivalent.

[0034] Each group 602, 609 has information constituting the group, and group 1 (602) is associated with user information 603, channel information 604, printer information 606, cooperative application information 607, and file 608.

[0035] User information 603 is information for identifying each user belonging to a group. Channel information 604 is information for grouping user information 603, and holds a list 605 that compiles the user information 603 corresponding to each channel. In the message application, a talk room (chat room) is created for each channel indicated in the channel information 604, and users exchange messages and image data with other users within that talk room.

[0036] Printer information 606 is information for identifying MFP 10. This printer information 606 may be the IP address or MAC address of the printer, or a uniquely identifiable ID. The ID may be an ID issued by tenant server 40 when information about MFP 10 is registered in tenant server 40. An application using group information 602 can send commands, such as a print command, to any MFP by referencing this information. While printer information 606 is associated with a group, it may also be associated with a channel or with cooperative application information (described later). For example, application 1 may be associated with MFP1, and application 2 may be associated with MFP1 and MFP2. Printer information 606 may also be associated with tenant information 601. That is, in the case of tenant 1 in FIG. 7 , the printer indicated by printer information 606 associated commonly within tenant 1 is used. This printer information 606 may also be associated with each user in user information 603. For example, user 1 may be associated with MFP1 and MFP2, and user 2 may be associated with MFP2.

[0037] The coordinated application information 607 is information for identifying the coordinated application associated with the group 1 (602). The coordinated application indicated by the coordinated application information 607 is an application installed in the message application server 30.

[0038] File 608 is a file stored in association with group 1 (602). For example, by sending file 608 to MFP 10, MFP 10 can print the file. Although file 608 is associated with a group, it may also be associated with a channel. For example, when a user posts a file to channel 1, which is a chat room, the file posted to channel 1 is stored in association with the file. The user can also check the stored file within the channel or download it to the user terminal 20.

[0039] When a user list is referenced within the message application 306 corresponding to the tenant information 601, the message application server 30 references the information stored in the HDD 405 of the tenant server 40 via the communication unit 304. The reference information at this time is a list of group information 602 and user information 603. The same applies to channel information 604, printer information 606, linked application information 607, and file 608.

[0040] 8 is a diagram showing an example of a message screen displayed on the operation panel 201 of the user terminal 20. The message application server 30 executes the message application 306 corresponding to the group 602, and the screen data is transmitted to the user terminal 20, and the message screen 701 is displayed by the user terminal 20 based on the screen data.

[0041] A message screen 701 shows a case where user 1 accesses message application 306 linked to group 602 .

[0042] In the display area 702, the user's own user information 603 and group information 602 to which the user belongs are displayed.

[0043] Display area 703 displays other user information 603 (information on other users belonging to the group) and channel information 604 (information on channels created within group 1) associated with group information 602. By selecting any person from display area 703, the user can display a message screen for exchanging messages with the selected person, enabling communication. If channel information 604 is selected here, message screen 701 for exchanging messages with all members belonging to the channel is displayed, enabling communication.

[0044] A button 704 is an object for adding the cooperative application A 506, and pressing this button installs the cooperative application A 506. In this embodiment, the cooperative application A 506 is configured to be installed, but other cooperative applications may be displayed in a list so that the user can select the cooperative application to install.

[0045] Display area 705 shows the person with whom you are currently exchanging messages. That is, it displays the person selected from display area 703. On message screen 701, channel 1 is selected.

[0046] Messages 706 and 707 display the history of messages exchanged. As shown in message 706, only text may be displayed, or file 608 information may be added as shown in message 707. Message 707 displays the content displayed when a file is scanned and uploaded from the MFP 10.

[0047] 9 is a diagram showing an example of a message screen displayed on the operation panel 201 of the user terminal 20. A message screen 800 shows a case where the user accesses the message application 306 linked to the group 602.

[0048] Message 801 is a message posted by user 3 when the material is uploaded and the text "Uploading material" is posted.

[0049] Message 802 shows the icon of the MFP Bot application that is installed in association with channel 1. The MFP Bot application is an example of the above-mentioned cooperative application.

[0050] Message 803 is a message posted by MFP Bot application 802 upon detecting that a file has been uploaded in message 801.

[0051] A list 804 shows a list of printers that can print, and is a list for the user to select a printer to issue a print instruction.

[0052] Button 805 is a print button that executes a print instruction to the printer selected from list 804. When this button 805 is selected, the MFP Bot application sends the file uploaded in message 801 and the print instruction to the printer selected in list 804. Note that this print instruction includes print setting information that is set by selecting button 807, which will be described later. The printer that receives the file and the print instruction prints an image based on the received file (image data) on paper in accordance with the print instruction.

[0053] A button 807 is a button for making print settings. When the button 807 is selected, a print setting screen (not shown) is displayed, and print settings can be accepted through user operation.

[0054] Message 806 is a message indicating that printing has been completed as a result of selecting button 805. This message is posted by the MFP Bot application when message application server 30 receives a print completion notification from the printer that sent the file and print instructions.

[0055] 9, the user can issue a print instruction to a printer by selecting the displayed button 805, but this is not limiting. For example, the MFP Bot application detects that a file has been uploaded and posts a message asking, "Do you want to print?". Then, when the user posts the message "Print" in response to that message, the MFP Bot application sends the file and a print instruction to the registered printer. The user can also send the file and a print instruction and select the printer to print the file by replying with the message "Print with MFP1" to the message "Do you want to print?".

[0056] Furthermore, the MFP Bot application does not only detect file uploads by users. For example, it can detect files generated by scanning on the MFP, such as message 707 in Figure 8, that are uploaded by the MFP or a collaborative application that works with the MFP.

[0057] 10 is a diagram showing an example of a message screen displayed on the operation panel 201 of the user terminal 20, similar to Fig. 9. Message 803 is a message posted by the MFP Bot application 802 upon detecting that a file has been uploaded in message 801. In addition to the message content in Fig. 9, recovery measures for the MFP by the user are also listed.

[0058] 11 is a diagram showing an example of MFP status information. The status information is notified to the tenant server 40 and updated every time the status of an MFP registered in the tenant server 40 changes. The MFP list 90 is a list of MFPs stored in the HDD 405 of the tenant server 40, and includes the following information:

[0059] The MFP name 901 is the name of the MFP. The acceptance status 902 is an example of information that can be confirmed when the cooperative application A 506 acquires the status of the MFP registered in the tenant server 40. It is possible to determine from the acceptance status 902 whether the MFP can accept a new job. If this is FALSE, the MFP cannot accept a job, and if this is TRUE, the MFP can accept a job.

[0060] The printer status 903 is an example of information that can be confirmed when the cooperative application A 506 acquires the status of the MFP registered in the tenant server 40. For example, if the network cable is not connected to the MFP or if the power is turned off, the MFP cannot communicate with the tenant server 40, and the status information becomes "unknown."

[0061] Detailed information 904 is an example of an item that can be checked when the cooperative application A 506 acquires detailed status information of the MFP registered in the tenant server 40 while the printer is not in a startup or processing state. Update date / time 905 indicates the date / time when the status information of the MFP was updated.

[0062] Although not shown, user information of users who can use each MFP is associated with each MFP in the MFP list 90. The association of the MFP with the user information is performed by the user in the tenant server 40.

[0063] Fig. 12 is a flowchart showing an example of print suggestion processing by cooperative application A506. It is also a flow diagram showing processing by message application server 30 in Fig. 13, which will be described later. The flow of Fig. 12 is started when user 1 accesses message application server 30 using user terminal 20 and message application server 30 accepts a request to display a message screen. The flow of Fig. 12 is executed by CPU 301 of message application server 30 executing message application 306 and cooperative application A506 stored in ROM 302 or HDD 306.

[0064] In the following example, an example will be described in which cooperative application A506 is associated with a channel. The flow in Fig. 12 is executed independently for each user belonging to the channel associated with cooperative application A506. In the following example, an example will be described in which user 1 accesses and logs in to message application server 30 using user terminal 20, and a request to display a message screen corresponding to user 1 is received. Therefore, the target user in the following description is user 1. If message application server 30 receives a request to display a message screen from another user (user 2, user 3, etc.), the flow in Fig. 12 is started independently.

[0065] 12 starts when the CPU 301 of the message application server 30 executes the cooperative application A 506, which then causes the message application server 30 to execute each process.

[0066] In S1001, the cooperative application A506 checks whether there has been a file change in the message application server 30, and if no file change is detected, the process returns to S1001, and if a file change is detected, the process proceeds to S1002. That is, the cooperative application A506 determines whether a file has been uploaded to the associated channel, and if it has been uploaded, the process proceeds to S1002, and if not, the process returns to S1001. Note that the process of S1001 may be performed not only when a file posting is detected, but also when a message posting requesting a printing suggestion from a user is detected. As an example, if a user's message "print" is detected, the process proceeds to S1002, and if not, the process returns to S1001.

[0067] In S1002, the cooperative application A 506 requests the tenant server 40 to send an MFP list linked to the user who has sent the message screen request. That is, the message application server 30 sends a request for the MFP list to the tenant server 40.

[0068] In S1003, the cooperative application A506 determines whether there is an MFP registered in advance in association with the user who has sent the message screen display request. That is, it determines whether there is an MFP associated with the user information of the user among the MFPs included in the MFP list received in S1002. If there is no MFP associated with the user that the user has permission to use among the MFPs associated with the user, the processing of the cooperative application A506 ends. If there is an MFP that the user has permission to use, the process proceeds to S1004.

[0069] By performing this process, it is possible to prevent a message from being displayed asking the user whether or not to print when there is no printer available for the user to use.

[0070] In S1004, the cooperative application A 506 checks the acceptance status 902 of the MFP list 90 acquired in S1002, and if it is TRUE (if the job can be accepted), proceeds to S1013. If it is FALSE (if the job cannot be accepted), proceeds to S1005. That is, if the MFP associated with the user who has sent the message screen display request is in an accepting state, proceeds to S1013; otherwise, proceeds to S1005. An accepting state means that the cooperative application A 506 can send a file and a print instruction to the MFP. The MFP displayed in the list 804 is the MFP associated with the user who is accessing the message application server 30 using the user terminal 20 to display the message 803. That is, the MFP displayed in the list 804 may or may not be different for each user who is displaying the message 803. Furthermore, users and MFPs are associated and registered in advance in the tenant server 40. The MFP to be printed on is basically set to an MFP close to the user.

[0071] Note that the status information of the MFP does not have to be included in S1002. For example, the status information may be received directly from the MFP by communicating with the MFP included in the MFP list received in S1002.

[0072] The order of determination in S1003 and S1004 may be reversed. One example is determining whether the status of the MFP registered in message application server 30 is in an acceptable state. Then, it is determined whether the determined MFP has the authority to use the user who sent the message screen request from application server 30. The determination order shown in the text is an example, and the present invention is not limited to the illustrated determination order.

[0073] In S1005, the cooperative application A506 checks whether the cause of the MFP's inability to accept the print job is a consumable-related event from the MFP's detailed information 904. If the cause is a consumable-related event, the process proceeds to S1006, and if the cause is not a consumable-related event, the process proceeds to S1007. Note that the processing of S1005 may be omitted. Examples of consumable-related events include a lack of toner, running out of ink, or detection of a media mismatch.

[0074] In S1006, the cooperative application A506 sets a consumables flag because the reason why the MFP cannot accept the print job is due to an event related to consumables.

[0075] In S1007, the cooperative application A506 checks whether the cause of the MFP's inability to accept the job is an event related to the MFP settings, based on the MFP detailed information 904. If the cause is an event related to the MFP settings, the process proceeds to S1008, and if the cause is an event unrelated to the MFP settings, the process proceeds to S1009. Note that the processing of S1007 may be omitted. An example of an event related to the settings is when the job is set to require administrator privileges to execute.

[0076] In S1008, the cooperative application A506 sets a setting flag because the reason why the MFP cannot accept the request is an event related to the MFP settings.

[0077] In S1009, the cooperative application A506 checks from the MFP detailed information 904 whether the cause of the MFP's inability to accept is an event related to the MFP device itself. If the cause is an event related to the MFP device itself, the process proceeds to S1010, and if the cause is an event not related to the MFP device itself, the process proceeds to S1011. Note that the processing of S1007 may be omitted. An example of an event related to the device itself is that the cover is open.

[0078] In S1010, the cooperative application A506 sets a device flag because the reason why the MFP cannot accept the request is due to an event related to the MFP device itself.

[0079] In S1011, it is determined whether to post a message suggesting printing to the user who sent the message screen request from the application server 30. The first determination criterion here is whether the MFP acceptance status 902 is TRUE or FALSE. If the acceptance status is TRUE, the process proceeds to S1012 to post the message suggesting printing. The second determination criterion is when the MFP status is FALSE but any determination in S1005, S1007, or S1009 is TRUE, that is, when the user has a recovery method. In this case, the process proceeds to S1012. The user's recovery method is inferred from the detailed information 904 obtained when the MFP status information is acquired from the message application server 30. If the first and second determination criteria are not met, the processing of the cooperative application A506 is terminated. An example of a case where the first and second determination criteria are not met is when the MFP acceptance status 902 is FALSE. Another example is when the MFP detailed information 904 indicates "eMMC has reached the end of its life" and S1005, S1007, and S1009 are all determined to be FALSE. In other words, this includes cases where the user is unable to perform recovery themselves. Also, if the tenant server 40 and the MFP are unable to communicate because a network cable is not connected to the MFP, for example, the MFP status information cannot be acquired. In such cases, too, the flow proceeds to NO in S1011. In other words, if the MFP status information cannot be acquired, a print job cannot be sent, and therefore there is no need to make a print suggestion.

[0080] It is also possible to determine whether to make a printing proposal based solely on the second criterion without considering the first criterion. For example, if a flag is set in S1006, S1008, or S1010, a printing proposal may be made, but if the MFP status information has not been acquired, a printing proposal may not be made.

[0081] In addition, in this embodiment, if it is determined to be FALSE in S1004, a print suggestion may not be made at any time. In other words, if the operation of the MFP is stopped or if communication via the network is not possible, information for inputting an image formation instruction for executing image formation processing based on data uploaded to the chat room may not be displayed.

[0082] In S1012, it is determined whether to add a statement indicating a user recovery measure to the message for printing suggestions. The statement changes depending on the content of the MFP detailed information 904 and the flags processed in S1006, S1008, and S1010. Message 808 is shown as an example of a user recovery measure. For example, if the remaining toner is low and a consumables flag is set, a message such as "Please replace the toner" is added. Also, if a setting flag is set, a message such as "Please review the settings" is added. Also, if a device flag is set because a cover provided on the MFP main body is open, a message such as "Please close the cover" is added. The message to be added here is determined based on the set flag and the detailed information 904 of the MFP list. Note that S1012 may be omitted, and no message may be added at all.

[0083] In S1013, the cooperative application A506 creates a message suggesting printing. An example of the message to be created is message 803 in Fig. 9. In S1014, the cooperative application A506 creates a message suggesting printing. An example of the message to be created is message 808 in Fig. 10. When adding a message, the message may be added and displayed in association with the name of the MFP so that it is clear which MFP the recovery message is for.

[0084] In S1015, it is determined whether the processes from S1003 onwards have been executed for all MFPs in the MFP list 90 that were requested to be sent in S1002. If the processes from S1003 onwards have been executed for all MFPs listed in the MFP list 90, the process proceeds to S1016. If there is an MFP for which the processes from S1003 onwards have not yet been executed, the process returns to before S1003 was executed. Note that the process of S1015 may be omitted, and the determination may be made for all MFPs available to the user in S1004.

[0085] In S1016, the print suggestion message created in S1013 or S1014 is posted to the channel. The message application 306 creates screen data for displaying the posted message. The user terminal 20 receives the screen data and displays a message screen based on the screen data. The print suggestion message may be posted with a setting that makes it visible only to specific users within the channel. As an example, the message may be posted with a setting that makes it visible only to the user who sent the message screen request from the application server 30.

[0086] In S1017, the cooperative application A 506 determines whether or not the user has pressed the print button 805, and if so, proceeds to S1012. If not, the cooperative application A 506 continues the processing of S1017 and waits for a user operation.

[0087] In S1018, the cooperative application A506 selects an arbitrary MFP from the MFP list described in the print proposal message, and executes printing on the selected MFP.

[0088] As an example, when MFP 804 is selected on the screen displayed on the user terminal in Fig. 9, cooperative application A 506 sends a print instruction to MFP 804. When cooperative application A 506 receives a print completion notification from the MFP that sent the print instruction, it posts a message 806 indicating that printing has been completed to message application 306. Message application 306 creates screen data for displaying the posted message. The flow of this process will be described in detail with reference to Fig. 15.

[0089] 13 is a sequence diagram showing an example of a process for posting a message for a printing suggestion. The cooperative application A506 installed on the message application server 30 has a function of sending a file uploaded from the user terminal 20 to the MFP 10 for printing. This function will be described.

[0090] This sequence shows the operation when cooperative application A506 is installed in HDD 305 in message application server 30 by executing the sequence shown in Fig. 13. Note that the operation of cooperative application A506 is performed by message application server 30. In the sequence of Fig. 13, all steps of message application server 30 are the operation of cooperative application A506.

[0091] In S1101, the CPU 207 of the user terminal 20 transmits a request to display a message screen to the message application server 30 via the wireless LAN communication unit 211. Specifically, the CPU 207 transmits a request for screen data for the user terminal 20 to display the message screen.

[0092] In S1102, the CPU 301 of the message application server 30 determines whether a file has been posted to a channel, which corresponds to S1001 in FIG.

[0093] In S1103, if the posting of a file is detected in S1102, the CPU 301 of the message application server 30 makes the following request to the tenant server 40. A request is made to send a list of MFPs that have been registered in advance in association with the user who made the request to display the message screen. This corresponds to S1002 in FIG. 12.

[0094] In S1104, the tenant server 40 sends a list of MFPs that have been registered in advance in association with the user who requested the message screen requested in S1003.

[0095] In S1105, the CPU 301 of the message application server 30 determines whether or not there is an MFP capable of printing. This corresponds to S1011 in FIG.

[0096] Specifically, it is determined from the MFP list 90 acquired in S1104 whether the user has permission to use each MFP. Then, the acceptance status 902 of the MFP for which the user has permission to use is checked to determine whether printing is possible. This corresponds to the case in FIG. 12 where YES is returned in S1003 and then YES is returned in S1004. Furthermore, if it is determined that printing is not possible, the MFP detailed information 904 is checked to determine whether the cause of the print acceptance status 902 being FALSE can be recovered by the user themselves. This corresponds to S1005 to S1010 in FIG. 12.

[0097] In S1106, if it is determined in S1105 that the MFP previously associated with the user and registered is suitable for printing, a screen for displaying a message suggesting printing is generated. This corresponds to S1014 in FIG. 12.

[0098] In S1107, if it is determined that the MFP registered in advance in association with the user has a recovery method for the user, a screen is generated to display a message indicating the user's recovery method in addition to the print suggestion message. This corresponds to S1013 in Fig. 12.

[0099] If it is determined in S1105 that a message suggesting printing should not be posted, screen data is generated that does not display the message suggesting printing. This corresponds to NO in S1003 or NO in S1011. The message application server 30 transmits the generated screen data to the user terminal 20. The user terminal 20 updates the display on the operation panel 201 based on the received screen data.

[0100] Fig. 14 is a sequence diagram for registering an MFP in advance with tenant server 40. In the following example, an example will be described in which an arbitrary MFP accesses tenant server 40 and registers the MFP with tenant server 40. Therefore, the target user in the following description is user 1. If the MFP receives a request from another user (user 2, user 3, etc.) to register the MFP with tenant server 40, the sequence in Fig. 14 starts independently.

[0101] In addition, the sequence of FIG. 14 causes the MFP to execute each process when the target user registers the MFP.

[0102] In S1201, a sequence for registering the MFP with the tenant server 40 is started by pressing an MFP registration button displayed on the user terminal 20. The sequence can be broadly divided into three phases: "user authentication," "device registration," and "access token acquisition."

[0103] In S1202, the MFP that has accepted the registration request from the target user generates a unique client ID and transmits it to the tenant server 40. This starts the "user authentication" phase.

[0104] In S1203, the CPU 401 of the tenant server 40 that has received the client ID from the MFP accepts the registration request and returns a unique user code, device code, and authentication URL to the MFP if the source MFP is not registered.

[0105] In S1204, the MFP displays the user code and authentication URL returned from the tenant server 40 in S1203.

[0106] In S1205, the MFP requests the tenant server 40 to check the authentication status until authentication of the target user is complete. When checking, the MFP sends the client ID generated in S1202 and the device code returned in S1203. The CPU 401 of the tenant server 40 that received the authentication status check request from the MFP returns a reception response (202). S1205 is repeated until an authentication completion response (200) is returned from the tenant server 40, as in S1209.

[0107] In S1207, the CPU 207 of the user terminal 20 transmits the authentication information displayed in S1204 to the tenant server 40 via the wireless LAN communication unit 211.

[0108] In S1208, the CPU 401 of the tenant server 40 that received the user code from the target user verifies whether the user code is the one entered in the authentication URL returned in S1202. If the verification is successful, the CPU 401 notifies the user terminal that the user authentication was successful, and changes the authentication status of the MFP registered in the tenant server 40 to registered.

[0109] In S1209, the tenant server 40 repeatedly requests the tenant server 40 to confirm the authentication status from S1205 until the MFP completes authentication of the target user. Because the authentication status was changed to successful in S1208, the MFP returns an authentication completion response (200) and a user access token. This completes the "user authentication" phase. Furthermore, if the CPU 401 of the tenant server 40 does not successfully authenticate the user because the authentication URL has expired, for example, the sequence starts again from S1201. In the above, an example was described in which an MFP (printer) is associated with a user, but group information or channel information may also be associated. In this case, a request is made to send a list of printers corresponding to the group information or channel information.

[0110] In S1207, the user inputs authentication information corresponding to his / her tenant data via the operation panel 201 of the user terminal 20. Note that this processing may use the authentication information (ID, password) input when logging in to the message application server 30. In this case, the process proceeds to S1210 without the user inputting authentication information in S1207.

[0111] In S1210, the MFP transmits the user access token returned in S210 to the tenant server 40 and requests device authentication, thereby starting the "device registration" phase.

[0112] In S1211, the CPU 401 of the tenant server 40 returns a reception response (202) and a unique registration ID to the MFP.

[0113] In S1212, the MFP repeatedly requests the tenant server 40 to confirm the device registration status of the registration ID returned in S1211 until a registration success response (200) is returned from the tenant server 40.

[0114] In S1213, the CPU 401 of the tenant server 40 returns a receipt response (202) to the MFP indicating that the request to confirm the device registration status has been received. The receipt response (202) is returned until the MFP associated with the registration ID is registered in the tenant server 40.

[0115] In S1214, when the tenant server 40 has completed registration of the MFP associated with the registration ID, it returns a success response (200) to the MFP registration status confirmation request. This completes the "device registration" phase. Also, if the tenant server 40 has not successfully authenticated the user because the user access token has expired, for example, the sequence starts again from S1201.

[0116] In S1215, the MFP requests the tenant server 40 to send a nonce, which is a one-time password for obtaining an access token for the MFP registered with the tenant server 40. This starts the "access token acquisition" phase.

[0117] In S1216, when the tenant server 40 receives the nonce request, the CPU 401 of the tenant server 40 creates a nonce and returns it to the MFP.

[0118] In S1217, the MFP that received the nonce requests that a device access token be sent using the registration ID and nonce returned in S1211. A JSON with a digital signature called a Json Web Token (JWT), which is a key pair, is generated and sent to the tenant server 40. In S1218, the CPU 401 of the tenant server 40 that received the JWT generates a JWT that serves as an authentication key pair from the registration ID of the registered MFP and the nonce generated in S1216, and verifies whether it matches the JWT sent in S1217. If confirmation is successful, the CPU 401 returns a device access token and the expiration date of the device access token to the MFP. This completes the "access token acquisition" phase. Furthermore, if the CPU 401 of the tenant server 40 is not successful in acquiring the device access token due to a mismatch in the JWT that serves as the authentication key pair, for example, the sequence starts again from S1215. In the above example, the message 803 suggesting printing is posted in chat format, but this is not limiting. For example, when a file is uploaded, a pop-up screen may be displayed on the message screen, and print settings and print instructions may be accepted on the pop-up screen. In this case, the cooperative application A 506 causes the message application server 30 to generate the pop-up screen.

[0119] The configuration shown in this embodiment is merely an example, and the present invention is not limited to the illustrated configuration.

[0120] 15 is a diagram showing an example of a process in which a cooperative application A506 installed on the message application server 30 receives a print request from a user and an MFP executes printing. The MFP that executes printing is registered in advance in the tenant server 40 in association with the user and the channel, as shown in FIG.

[0121] In S1301, when a print job targeted at the MFP is registered in the tenant server 40, the MFP requests the tenant server 40 to notify the MFP. The notification can be a pull notification or a push notification, and either can be selected.

[0122] In S1302, the CPU 301 of the message application server 30 determines whether or not the user has pressed the print button 805 in S1017. If pressed, the CPU 207 of the user terminal 20 sends a print request to the message application server 30.

[0123] In S1303, the CPU 301 of the message application server 30 generates a screen for displaying a message for making print settings. The message application server 30 transmits the generated screen data to the user terminal 20. The user terminal 20 updates the display on the operation panel 201 based on the received screen data.

[0124] In S1304, if the user presses the print execution button displayed on the user terminal, the process proceeds to S1305.

[0125] In S1305, the CPU 301 of the message application server 30 makes a job creation request for the file for which printing has been proposed, and transmits the request to the tenant server 40 together with the printer ID.

[0126] In S1306, the CPU 401 of the tenant server 40 receives the job creation request from the MFP, and returns a creation response (201) to the message application server 30 if the job creation is successful.

[0127] In S1307, since the CPU 401 of the tenant server 40 has set in S1301 that notification will be made once the job for the MFP has been confirmed, the tenant server 40 notifies the MFP that the job has been registered.

[0128] In S1308, the MFP that has received the job registration notification from the tenant server 40 requests the tenant server 40 to send a job list.

[0129] In S1309, the CPU 401 of the tenant server 40 returns the job list to the MFP.

[0130] In S1310, the MFP that has received the job list adds the received job list to its own job record.

[0131] In S1311, the MFP requests the tenant server 40 to acquire job information.

[0132] In S1312, the CPU 401 of the tenant server 40 returns the job template in which the job information is described.

[0133] In S1313, the MFP updates the job information in the device using the returned job template.

[0134] In S1314, the MFP notifies the tenant server 40 that the information requested in S1311 has been acquired.

[0135] In S1315, the CPU 401 of the tenant server 40 returns a notification that the notification in S1314 was successfully received.

[0136] In S1316, the MFP notifies the tenant server 40 of the job status within the device and that the device status will be changed to ready to print.

[0137] In S1317, the MFP updates the device state in the device.

[0138] In S1318, the MFP requests the tenant server 40 to acquire job information.

[0139] In S1319, the CPU 401 of the tenant server 40 receives the job information acquisition request from the MFP and returns the job information.

[0140] In S1320, the MFP notifies the tenant server 40 in S1318 that the information requested has been acquired.

[0141] In S1321, the CPU 401 of the tenant server 40 returns a notification that the notification in S1320 was successfully received.

[0142] In S1322, the MFP notifies the tenant server 40 that the job status and device state will be changed to printing.

[0143] In S1323, the MFP changes the device state in the device to printing.

[0144] In S1324, the MFP executes printing.

[0145] In S1325, the MFP notifies the tenant server 40 that the job status and device state will be changed to "printing."

[0146] In S1326, the MFP changes the device status within the device to waiting for a job.

[0147] With the above configuration, when data is uploaded to a chat room and the user is asked whether to have the printer print the data, unnecessary messages can be prevented from being displayed.

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

[0149] 10 MFP 20 User terminal 30 Message Application Server 40 Tenant Servers

Claims

1. a display step of displaying, in the chat room, a button for inputting an image formation instruction for executing an image formation process based on the data uploaded to the chat room; an image formation control step of causing an image forming apparatus to execute the image formation process based on the data, based on an image formation instruction input using the displayed button; The information processing method is characterized in that the display step prevents the button from being displayed based on the state of the image forming apparatus.

2. further comprising an acquisition step of acquiring status information of the image forming apparatus; 2. The information processing method according to claim 1, wherein the display step prevents the button from being displayed based on the state information acquired in the acquisition step.

3. 3. The information processing method according to claim 2, wherein the display step prevents the button from being displayed when the state information is not acquired in the acquisition step.

4. 2. The information processing method according to claim 1, wherein the display step displays the button and information indicating that the consumable is in short supply when the consumable is in short supply in the image forming apparatus.

5. The information processing method according to any one of claims 1 to 4, characterized in that the display step prevents the button from being displayed based on the status of the image forming device associated with the user logged in to the information processing device that executes the information processing method.

6. 6. The information processing method according to claim 5, wherein the display step prevents the button from being displayed when there is no image forming apparatus corresponding to the user.

7. 2. The information processing method according to claim 1, wherein the display step displays the button and an object for setting the image forming process in the chat room.

8. a display step of displaying, in the chat room, a button for inputting an image formation instruction for executing an image formation process based on the data uploaded to the chat room; an image formation control step of causing an image forming apparatus to execute the image formation process based on the data, based on an image formation instruction input using the displayed button; The display step prevents the button from being displayed based on the state of the image forming apparatus.

9. further comprising an acquisition step of acquiring status information of the image forming apparatus; 9. The program according to claim 8, wherein the display step prevents the button from being displayed based on the state information acquired in the acquisition step.

10. 10. The program according to claim 9, wherein the display step prevents the button from being displayed when the state information is not acquired in the acquisition step.

11. 9. The program according to claim 8, wherein the display step displays the button and information indicating that the consumable is in short supply when the consumable is in short supply in the image forming apparatus.

12. The program according to any one of claims 8 to 11, characterized in that the display process prevents the button from being displayed based on the status of the image forming device associated with the user logged in to the information processing device that executes the program.

13. 13. The program according to claim 12, wherein the display step prevents the button from being displayed when there is no image forming apparatus corresponding to the user.

14. 9. The program according to claim 8, wherein the display step displays the button and an object for setting the image forming process.

15. a display means for displaying in the chat room a button for inputting an image formation instruction for executing an image formation process based on data uploaded to the chat room; an image forming control unit that causes an image forming apparatus to execute the image forming process based on the data, based on an image forming instruction input using the displayed button; The information processing apparatus is characterized in that the display means does not display the button based on the state of the image forming apparatus.

Images