Image processing device, control method thereof, and program

Abstract

To enable a user to simply upload image data generated by reading an image of a document by an image processing device to a desired thread.SOLUTION: An image processing device of the present invention is an image processing device capable of communicating with an information processing device. The image processing device includes: reading means for reading an image of a document and generating image data; reception means for accepting designation of a thread in a chat service channel; and transmission means for transmitting the image data to the information processing device, so that information indicating the image data generated by the reading means is added to the thread, designation of which is accepted by the reception means.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to an image processing apparatus, a control method thereof, and a program. [Background technology]

[0002] Patent Document 1 discloses that an image processing device scans an image of a document, generates image data, and transmits the image data to a chat server that provides a chat service. As a result, the image data is uploaded to a chat room of the chat service and shared. [Prior art documents] [Patent documents]

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

[0004] In chat rooms on chat services, multiple chats are organized into threads, each consisting of a series of conversations. Users chat using separate threads for each topic, allowing them to view a series of conversations all at once.

[0005] In Patent Document 1, it is not possible to know to which thread in a chat room the image data generated by an image processing device scanning an image of a document will be uploaded, so there is a possibility that the image data will be uploaded to a thread that the user does not intend.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to enable a user to easily upload image data generated by an image processing device reading an image of a document to a desired thread. [Means for solving the problem]

[0007] The image processing device of the present invention is an image processing device capable of communicating with an information processing device, and includes: a reading means for reading an image of a document and generating image data; and a receiving means for receiving a designation of a thread of a channel of a chat service. The image data generated by the reading means; The thread whose designation has been accepted by the accepting means The identification information of and a transmitting means for transmitting to the information processing device. The image data is added to the thread indicated by the identification information by the information processing device. It is characterized by: [Effects of the Invention]

[0008] This allows a user to easily upload image data generated by an image processing device reading an image of a document to a desired thread. [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 the MFP101 [Figure 3] FIG. 1 is a diagram showing an example of a hardware configuration of a mobile terminal 200. [Figure 4] FIG. 1 is a diagram illustrating an example of a hardware configuration of a message application server 300. [Figure 5] FIG. 1 shows an example of the hardware configuration of a bot server 400. [Figure 6] FIG. 10 shows an example of a home screen displayed on an operation unit 116 of the MFP 101. [Figure 7] FIG. 10 shows an example of a sequence in which the MFP 101 transmits a file generated by scanning to the message application server 300. [Figure 8] A flowchart showing an example of scan-to-chat processing executed by the MFP 101. [Figure 9] A diagram showing an example of the file structure in the Message App server [Figure 10] A diagram showing an example of a message screen in a messaging app [Figure 11] An example of the screen transition for scan-to-chat processing [Figure 12] FIG. 10 is a diagram showing an example of a setting registration screen. [Figure 13] A diagram showing an example of a thread selection screen 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] FIG. 1 is a diagram illustrating an example of a system configuration of the present invention. The system configuration of this embodiment includes an MFP (Multi Function Peripheral) 101, which is an image processing device capable of communicating with a mobile terminal 200, which is an example of a terminal device, via a network 100, and a message app server 300. A bot server 400 is also connected via the network 100 and is capable of communication. The message app server 300 is a chat server that receives messages and image data transmitted from the MFP 101 and the mobile terminal 200 and manages a chat service that displays the messages and image data on the mobile terminal 200 or a PC (not shown) in response to a user operation. The bot server 400 associates the MFP 101 with information (token information) corresponding to a bot app installed in the message app server 300 connected to the MFP 101, and forwards a request from the MFP 101 to the message app server 300. The network 100 in this embodiment may be the Internet or a local area network (LAN). The network 100 may be wired or wireless.

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

[0013] The control unit 110, including the CPU 111, controls the overall operation of the MFP 101. The CPU 111 loads a control program stored in the ROM 112 or the storage 114 into the RAM 113 to perform various control operations, such as scanning control and printing control. The ROM 112 stores control programs executable by the CPU 111. The ROM 112 also stores a boot program, font data, and the like. The RAM 113 is 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 the storage 114. The storage 114 stores image data, print data, various programs, 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.

[0014] In the MFP 101 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 using multiple CPUs, RAMs, ROMs, and storages in cooperation with each other. Also, some processes can be executed using hardware circuits such as ASICs and FPGAs.

[0015] The operation unit I / F 115 connects the control unit 110 to an operation unit 116 including a display unit such as a touch panel and hard keys. The operation unit 116 displays information to the user and detects inputs from the user.

[0016] 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 an original document, and the CPU 111 converts the image into image data such as binary data. Image data generated based on the image read by the reading unit 118 is sent to an external device or printed on recording paper. The reading unit also has an ADF, and can transport an original document placed on an original document tray provided in the MFP 101, read the image of the transported original document, and generate image data.

[0017] 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 recording paper fed from a paper feed cassette.

[0018] 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 (here, the mobile terminal 200) via wireless communication.

[0019] The control unit 110 is connected to the public line network 107 by controlling a FAX communication unit 124 such as a facsimile via a FAX unit I / F 123. The FAX unit I / F 123 is an I / F for controlling the FAX communication unit 124, and by controlling a modem and NCU for facsimile communication, it is possible to connect to the public line network, control the facsimile communication protocol, and the like.

[0020] The communication unit I / F 125 connects the control unit 110 to the network 100. The communication unit I / F 125 allows the communication unit 126 to transmit image data and various internal device information to external devices on the network 100, and to receive 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 email 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 mobile terminal 200, the message application server 300, and the bot server 400.

[0021] 3 is a diagram showing an example of the hardware configuration of the mobile terminal 200. Note that although the mobile terminal 200 of this embodiment is assumed to be a device such as a smartphone or a tablet PC, it may be any other device as long as it is an information processing device capable of Wi-Fi communication.

[0022] The CPU 207 reads out a control program stored in the ROM 208 and executes various processes for controlling the operation of the mobile terminal 200. 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.

[0023] 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 email sending application. The operation panel 201 is also used to check information stored in the message application server 300. The user can input desired operation instructions to the mobile terminal 200 by inputting a touch operation to the operation panel 201. The mobile terminal 200 is also equipped with hardware keys (not shown), and the user can input operation instructions to the mobile terminal 200 using these hardware keys.

[0024] 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. It is also possible to obtain information from a QR code read by camera 204 using a program capable of analyzing QR codes (registered trademark).

[0025] The mobile terminal 200 can exchange data with 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 mobile terminal 200 may be compatible with Bluetooth (registered trademark) Low Energy.

[0026] 4 is a diagram showing an example of the hardware configuration of the message application server 300. The CPU 301 reads out a control program stored in the ROM 302 and executes various processes for controlling the operation of the message application server 300. 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, image data, and channel information. Data can be transmitted and received to and from various devices such as the mobile terminal 200 and MFP 101 via the communication unit 304. The communication unit 304 may perform wired communication using Ethernet (registered trademark) or wireless communication such as Wi-Fi.

[0027] FIG. 5 is a diagram showing an example of the hardware configuration of the bot server 400. The CPU 401 reads out a control program stored in the ROM 402 and executes various processes for controlling the operation of the message application server. 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 various data such as messages, image data, and channel information. Data can be sent and received via the communication unit 404 with various models such as the mobile terminal 200, MFP 101, and message application server 300.

[0028] 6 is a diagram showing an example of a home screen displayed on operation unit 116 of MFP 101. Operation unit 116 is made up of touch panel 601 that displays the operation screen, and LEDs 610 and 611. Touch panel 601 is an instruction means, and functions both as an acceptance means that accepts instructions from a user and as a display means that displays a screen. A user directly touches the screen displayed on touch panel 601 with a finger, a stylus, or other object to instruct the execution of each function based on the displayed screen.

[0029] 6 displays a home screen 608. The home screen 608 is the first screen for instructing the execution of each function of the MFP 101, and is a screen for selecting a screen display for making various settings for each function executed by the MFP 101, such as copy, fax, scan, and media print.

[0030] A status check button 605 is an object for displaying a screen (status check screen) for checking the status of the MFP 101. A transmission history and job execution history can be displayed from the status check screen (not shown).

[0031] The scan-to-chat button 602 is an object for displaying a settings screen for the scan-to-chat process. When the scan-to-chat button 602 is selected by the user, a scan-to-chat screen 1101 shown in Fig. 11 is displayed on the operation unit 116. The scan-to-chat process will be described in detail with reference to Figs. 7 and 8.

[0032] The scan button 603 is an object for displaying a scan selection screen (not shown) from the MFP 101. The scan selection screen is a screen for selecting a transmission function such as email transmission (E-mail), file transmission via SMB, FTP, or HTTP, and Internet fax (I-fax) transmission. Touching the object representing the displayed transmission function displays a setting screen for each transmission function.

[0033] An address book button 604 is an object for displaying an address book screen of the MFP 101 when selected by the user. LEDs 610 and 611 notify the user of the status of the MFP 101. The LED 610 lights up while an e-mail or a print job is being received or executed, and the LED 611 lights up when an error occurs in the MFP 101. The stop button 606 is an object for canceling various operations and is an object that is always displayed on the operation unit 116. The HOME button 607 is an object for displaying a home screen 608 and is an object that is always displayed on the operation unit 116. The menu button 612 is an object for displaying a screen for setting the environment, such as the language used, and for setting each function.

[0034] Fig. 7 is a diagram showing an example of a sequence in which the MFP 101 transmits a file generated by scanning to the message application server 300. The sequence in Fig. 7 is started in response to selection of the destination setting button 1114 on the scan-to-chat screen 1101 in Fig. 11.

[0035] In S701, the CPU 111 of the MFP 101 controls the communication unit 126 to request channel list information and thread list information via HTTP communication from the message app server 300. Specifically, the MFP 101 transmits to the message app server 300 token information input by the MFP 101 and information indicating a request for a channel list in the workspace indicated by the token information. Here, by transmitting the user ID information input by the MFP 101 to the message app server 300, information related to the user ID in the workspace is identified. Furthermore, if only the individual user is allowed to read and write user information in the workspace, this authority is acquired by transmitting password information corresponding to the user ID information input by the MFP 101 to the message app server 300.

[0036] Here, an example of the command to be sent is "HTTP GET https: / / message.com / api / channels.list". The URL "https: / / message.com / api / channels.list" described in this command is a URL for accessing the message app server 300. By sending token information to this URL, the message app server 300 searches for a workspace corresponding to the token information and a channel associated with the user. Similarly, by sending token information and a user ID to the URL "https: / / message.com / api / thread.list", the message app server 300 searches for a workspace corresponding to the token information and a thread associated with the user. Note that the token information is input by the user via the setting registration screen 1201 of FIG. 12 displayed on the operation unit 116 of the MFP 101.

[0037] Here, a workspace is like an organization to which multiple users belong within a messaging app, and is sometimes called a team. Also, a channel is synonymous with a chat room within a workspace. A chat room here is a mechanism by which multiple users participating in the chat room can send and receive messages with each other and interact like a conversation. Also, in this embodiment, a channel is described as a chat room, but it is not limited to this as long as it is a mechanism by which multiple users can send and receive messages and interact like a conversation. For example, it may be something like a group chat, room, talk room, or group.

[0038] Here, the bot app is an application for registering the MFP 101 as a user in a message app and posting messages and image data, and is installed in the message app server 300. By specifying a bot app and sending image data to the message app server 300, the bot app posts the sent image data in the message app. Furthermore, the HDD 305 of the message app server 300 stores bot apps and tokens in association with each other, and also associates bot apps with workspaces. Therefore, by receiving token information from the MFP 101, the message app server 300 can return information about the workspace associated with the bot app associated with the token information. Note that the token information, bot app, and workspace may also be directly associated with each other. This allows a workspace (a workspace to which the user wants to send image data) corresponding to pre-registered token information to be selected from a large number of workspaces.

[0039] In S702, the CPU 301 of the message app server 300 checks whether access to the URL is permitted based on the token information and user ID received from the MFP 101 via the communication unit 304. If permitted, channel list information included in the workspace corresponding to the token information is generated. The channel list information is array information indicating channel information. The channel information includes the channel ID, the channel name, information indicating the users participating in the channel, and channel setting values ​​indicating settings such as whether the channel is an archived channel.

[0040] In S703, the CPU 301 of the message application server 300 checks whether access to the URL is permitted based on the token information and user ID received from the MFP 101 via the communication unit 304. If permitted, thread list information included in the workspace corresponding to the token information is generated. The thread list information is array information indicating thread information. The thread information includes a thread ID, the posted content of the thread, information indicating the posting user ID of the thread, and thread setting values ​​indicating information such as the thread update time.

[0041] In S704, the CPU 301 of the message application server 300 controls the communication unit 304 to transmit the channel list information and thread list information generated in S702 and S703 to the MFP 101 as response information of the HTTP communication.

[0042] In S705, CPU 111 of MFP 101 generates channel selection screen 1119 based on the channel information included in the received channel list information. Then, when the user selects destination setting button 1114, CPU 111 of MFP 101 displays channel selection screen 1119 on touch panel 601 of operation unit 116 and waits for a user operation. Channel selection screen 1119 will be described later in the description of FIG. 11.

[0043] In S706, the CPU 111 of the MFP 101 confirms the information of the channel to which the posting is to be made by selecting at least a channel on the channel selection screen 1119 and selecting the back button. After the channel selection is made, the user selects the thread selection button 1118, and the thread selection screen 1120 is displayed. The thread is selected on the thread selection screen 1120, and the information of the thread to which the posting is to be made is confirmed by selecting the back button.

[0044] In S707, the CPU 111 of the MFP 101 receives a scan execution instruction via the operation unit 116.

[0045] In S708, the CPU 111 of the MFP 101 scans the image of the document based on the scan execution instruction and the scan settings set by the user.

[0046] In step S709, the CPU 111 of the MFP 101 generates image data of the scanned image in a format set in the scan settings. The scan settings are those specified by the user on a scan-to-chat advanced settings screen (not shown). The scan settings may be displayed and set together with the transmission settings on the transmission settings screen 1112 in FIG. 11.

[0047] In S710, the CPU 111 of the MFP 101 transmits the same token information as in S701 and information about the destination channel selected in S706 to the message app server 300 via the communication unit 126 by HTTP communication. Information about the destination thread (identification information such as a thread ID), the file format, and the image data generated in S709 are also transmitted by HTTP communication. The file format used is the file format specified by the user on the scan-to-chat transmission settings screen 1112.

[0048] In S711, the CPU 301 of the message app server 300 searches for the workspace information and app information registered in the token information received in S710, and stores the received image data in association with the channel specified by the channel information. If a thread to which the image data is to be posted is specified, the CPU 301 stores the received image data in the thread to which the image data is to be posted. As a result, when a user launches the message app on the mobile terminal 200 and specifies a thread to check the content of the conversation in the previous thread, a screen in which the received image data is posted in the specified thread in the specified channel is displayed. Furthermore, if a user to which the image data is to be posted is specified, the CPU 301 further stores the received image data in association with the channel and the user to which the image data is to be posted. As a result, when a user launches the message app on the mobile terminal 200 and specifies a channel to check the content of the conversation in the previous channel, a screen in which the received image data is posted is displayed. This screen is displayed on the display unit of the device that accessed the message app server 300.

[0049] In S712, the CPU 301 of the message application server 300 transmits a result indicating whether the posting was successful or not to the MFP 101 as HTTP communication response information. If the posting is successful, the CPU 111 of the MFP 101 may display a notification indicating that the posting was successful on the operation unit 116. If the posting is unsuccessful, the CPU 111 of the MFP 101 may display a notification indicating that the posting was unsuccessful on the operation unit 116. Alternatively, if the posting is successful, no notification may be displayed, and only if the posting is unsuccessful, a notification indicating that the posting was unsuccessful may be displayed.

[0050] Fig. 8 is a flowchart showing an example of scan-to-chat processing executed by MFP 101. CPU 111 reads a program stored in ROM 112 into RAM 113 and executes it, thereby executing the processing of the flowchart in Fig. 8. The flow in Fig. 8 also starts when MFP 101 is powered on.

[0051] In S801, the CPU 111 determines whether or not the scan-to-chat button 602 has been selected. If it is determined that the scan-to-chat button 602 has been selected, the process proceeds to S802. If not, the process returns to S801.

[0052] In S802, the CPU 111 displays a scan-to-chat screen 1101 on the touch panel 601 of the operation unit 116. Here, the screen transition when the scan-to-chat button 602 is selected will be described with reference to FIG.

[0053] 11 is a diagram showing an example of screen transitions during scan-to-chat processing. When the scan-to-chat button 602 displayed on the home screen 608 is selected, a scan-to-chat screen 1101 is displayed on the touch panel 601 of the operation unit 116.

[0054] A destination confirmation button 1105 is displayed on the scan to chat screen 1101. The destination confirmation button 1105 displays the number of destinations set as destinations for posting image data generated by scanning. In the example of FIG. 11, an example will be described in which one channel is selected as a posting destination. If multiple destinations are selected, the number of set posting destinations is displayed as the number of destinations.

[0055] When the confirm destination button 1105 is selected, a scan-to-chat destination confirmation screen 1106 is displayed. The scan-to-chat destination confirmation screen 1106 displays the sending setting posting destinations that were set when the set destination button 1114 was selected. The posting destination button 1107 displays the number of posting destinations that are currently set, and when selected by the user, a details screen (not shown) is displayed, displaying details of the set posting destinations.

[0056] In this embodiment, only one posting destination is displayed on the scan-to-chat destination confirmation screen 1106, but this is not limiting. For example, the MFP 101 can set multiple posting destinations from the message application server 300, thereby displaying multiple posting destination buttons on the scan-to-chat destination confirmation screen 1106.

[0057] When the reset button 1108 is selected on the scan-to-chat screen 1101, the set information is cleared. At this time, the set destination information is also cleared. When the black and white start button 1109 and color start button 1110 are selected on the scan-to-chat screen 1101, the scan and send process is started.

[0058] When the transmission setting button 1111 is selected, a transmission setting screen 1112 is displayed. On this screen, transmission settings such as file format 1113 can be changed and confirmed.

[0059] When the destination setting button 1114 is selected, a destination selection mode selection screen 1116 is displayed. On this screen, a channel selection button 1117 and a thread selection button 1118 can be selected.

[0060] When the channel selection button 1117 is selected, a channel selection screen 1119 is displayed. The channels and users displayed on this channel selection screen 1119 are displayed based on the channel list information that the MFP 101 receives from the message app server 300. On this screen, it is possible to select the channel to post to and which users belonging to that channel to notify. In other words, it is possible to select the channel to post to and the people to mention. When a channel button is selected, the users belonging to that channel are displayed in a pull-down menu. On this screen, it is possible to select both a channel and a user, or to select only a channel to post to all users belonging to that channel. It is also possible to select multiple channels, or it is possible to select one channel and then select multiple users within that channel. It is also possible to select multiple channels and then select different users belonging to each channel.

[0061] When the back button 1115 is selected, the channel selection is maintained and the scan-to-chat screen 1101 is displayed again. At this time, the destination field 1102 displays the name of the selected channel that is the destination of the posting and the name of the user to be notified, "Destination: Channel 3 @ User 1." The CPU 111 of the MFP 101 also stores the destination of the posting based on the channel and user set at this time in the RAM 113 or storage 114.

[0062] When the thread selection button 1118 is selected, a thread selection screen 1120 is displayed, displaying information about multiple threads. The threads and users displayed on this thread selection screen 1120 are displayed based on thread list information received by the MFP 101 from the message application server 300. On this screen, it is possible to select the thread to post to and which users belonging to the channel containing that thread will be notified. In other words, it is possible to select the thread to post image data to and the users to mention. When the thread button is selected, a list of messages for that thread is displayed in a pull-down menu. On this screen, it is possible to select both a thread and a user, or to select only the thread. It is also possible to select multiple threads, or it is possible to select one thread and then select multiple users in the channel containing that thread. It is also possible to select multiple threads and then select different users belonging to each thread. The configurable variations of this screen are described in detail in FIG. 13.

[0063] The thread selection screen 1120 displays a list of threads and the title of each thread or the first message posted in each thread. Furthermore, by selecting each thread, the last message posted in the selected thread or each message posted in that thread may be displayed. Note that, when only some of the messages posted in a thread, such as the first or last message of a thread, are to be displayed, the MFP 101 may receive only some of the messages from the message application server 300. This eliminates the need to receive all messages in the specified thread, thereby reducing the storage area required for the MFP 101. Furthermore, by displaying only some of the threads, the user can recognize which thread each thread is without overwhelming the screen display.

[0064] The thread list displayed on the thread selection screen 1120 may display threads included in the channel selected on the channel selection screen 1119. If no channel is selected, a list of all threads in a workspace (team) designated in advance may be displayed. Also, in the above example, thread candidates are displayed to the user for selection, but this is not limiting. For example, if there is identification information such as a thread name or ID, the user may be allowed to manually input the identification information. Alternatively, the user may be allowed to select the identification information.

[0065] Now, returning to the explanation of the flow in Fig. 8, in S802, the CPU 111 displays the scan-to-chat screen 1101 in Fig. 11 on the operation unit 116. In S803, the CPU 111 detects that the destination setting button 1114 has been selected.

[0066] In S804, the CPU 111 executes processing to transmit request information for channel information to the message application server 300 by HTTP communication using the token information 1203 and the user ID registered in advance in accordance with the user's selection of the channel selection button.

[0067] Here, the setting registration screen in Fig. 12 will be described. Fig. 12 is a diagram showing an example of the setting registration screen. The setting registration screen 1201 is a screen displayed on the operation unit 116 of the MFP 101. Note that the setting registration screen 1201 may also be displayed as a web page on the operation unit of an information processing device such as a PC connected to the MFP 101 via a network. The content registered on the setting registration screen 1201 is stored.

[0068] Connection destination 1202 is a column showing organizational information of the connection destination. Token information 1203 is a column of registered token information. Operation buttons 1204 is a column of operation buttons. In this item, an edit button 1205 and a generate button 1206 are displayed.

[0069] When the edit button 1205 is selected, character strings such as token information, connection destination information, etc. can be input and changed using a keyboard, etc. When the create button 1206 is selected, the home screen 608 is set to display the scan-to-chat button 602.

[0070] By clicking the new registration button 1207, it is possible to accept the input of a character string by the user, and to add and register the connection destination and token information.

[0071] Now, returning to the explanation of the flow in Fig. 8, in step S805, the CPU 111 executes a process of transmitting, to the message application server 300, information indicating a request for thread information via HTTP communication, using the token information 1203 and user ID information registered in advance.

[0072] In S806, the CPU 111 determines whether or not channel information and thread information have been received from the message application server 300 in response to the channel acquisition request sent in S804 and the thread acquisition request sent in S805. Specifically, if the status code in the HTTP communication response is an error or if the body information of the response contains a parameter indicating that the information cannot be acquired, it determines that the channel list information or thread list information has not been received. If it is determined that the information has been received, the process proceeds to S809. If not, the process proceeds to S807.

[0073] In S807, the CPU 111 displays information indicating that the channel list information could not be received on the channel selection screen 1119. At this time, the channel selection screen 1119 does not display any channel or user options.

[0074] In S808, the CPU 111 determines whether or not the back button 1115 has been selected. If it is determined that the back button 1115 has been selected, the process returns to S802. If not, the process returns to S808.

[0075] In S809, the CPU 111 determines whether or not the destination selection mode has been selected. If the channel selection mode has been selected, the process proceeds to S810. If the thread selection mode has been selected, the process proceeds to S819.

[0076] In S810, the CPU 111 displays on the touch panel 601 of the operation unit 116 a channel selection screen 1119 on which the channel information received from the message application server 300 and the like are displayed.

[0077] In S811, the CPU 111 detects via the touch panel 601 of the operation unit 116 whether the posting destination (channel, or channel and user) selected on the channel selection screen has been confirmed. If confirmed, the process proceeds to S812, where the posting channel list information is updated. If not confirmed, the process returns to S810. The method for detecting confirmation is whether the back button 1115 has been selected. Note that, in a screen configuration in which the confirm button is displayed on the screen of the operation unit 116, the same transition occurs when the confirm button is selected.

[0078] In step S819, the CPU 111 displays, on the touch panel 601 of the operation unit 116, a thread selection screen 1120 on which thread information received from the message application server 300 and the like are displayed.

[0079] In S820, the CPU 111 detects via the touch panel 601 of the operation unit 116 whether the posting destination (thread, channel, or channel and user) selected on the thread selection screen has been confirmed. If confirmed, the process transitions to S812, where the posting channel list information is updated. If not confirmed, the process returns to S819. The method for detecting confirmation is whether the back button 1115 has been selected. Note that, in a screen configuration in which the confirm button is displayed on the screen of the operation unit 116, the same transition occurs when the confirm button is selected.

[0080] 11 on the operation unit 116, and updates the display of the posting destination field 1102 with the confirmed posting destination. At this time, information about the user to be notified is also displayed along with the posting destination channel. Thread information may also be displayed here.

[0081] In S813, the CPU 111 determines whether the monochrome start button 1109 or the color start button 1110 displayed on the operation unit 116 has been selected. If it is determined that the button has been selected, the process proceeds to S814. If not, the process returns to S813.

[0082] In step S814, the CPU 111 controls the reading unit 118 based on the scan settings to read the image of the document and generate image data. The scan settings are scan settings specified by the user on a scan-to-chat advanced settings screen (not shown), and the scan settings received from the message app server 300 are used.

[0083] In S815, the CPU 111 converts the image data generated in S814 into the file format 1113 set on the transmission setting screen. Note that this process may be omitted.

[0084] In S816, the CPU 111 generates posting parameters. The posting parameters include the channel to which the message is to be posted, thread information, file format, file name, and posted comment. The file format is set to the file format 1113 set in the sending settings. The posted comment is generated by adding an at sign "@" to the beginning of the user information to be notified. The file name is specified as the file name specified in the sending settings.

[0085] In S817, the CPU 111 uses the token information 1203 registered in advance to send the file generated in S815 and the posting parameters to the message app server 300 using the POST method of HTTP communication. By sending this data (the file converted from image data and the posting parameters) to the message app server 300, the message app server 300 posts the data to the specified thread in the specified channel based on the received parameters. At this time, the image data itself may be posted (uploaded) to the thread, or information such as a link for referencing the image data may be added to the thread. The posting of image data and the addition of information are performed by the message app server 300.

[0086] In step S818, the CPU 111 receives the posting result from the message application server 300 and displays it on the touch panel 601 of the operation unit 116. According to this embodiment, the user can easily post a file from the MFP 101 to a channel and thread of the message application server.

[0087] In this embodiment, only one piece of token information is registered, but if multiple pieces of token information are registered, processes related to the token information, such as S804, S806, and S817, are executed for each registered token.

[0088] An example of a screen displayed on the operation panel 201 of the mobile terminal 200 as a result of the file converted from image data and posting parameters being sent to the message application server 300 in the process of S817 will be described with reference to FIG.

[0089] Fig. 10 is a diagram showing an example of a message screen of a message app. A message screen 1001 in Fig. 10 is displayed when the message app is launched on the mobile terminal 200 and the processing of S817 is executed on the MFP 101. The mobile terminal 200 is also in communication with the message app server 300.

[0090] When a user starts the message application on the mobile terminal 200 and logs in by entering the ID and password of the user's account, a screen dedicated to that user is displayed.

[0091] Thread message 1005 is a thread message that is displayed when a user with an account for User 3 sends a message to the message app server 300 with the title of Thread 2 saying, "Can you send me the materials for next week's meeting?"

[0092] Message 1006 is a thread message that is displayed when a user with the account of User 1 posts a reply message to the message of thread message 1005.

[0093] Message 1004 is a thread message that is displayed when a user with an account for User 1 posts a reply message to thread message 1005. This message is displayed (posted) when a user with an account for User 1 uses the MFP 101 with the user ID information of User 1 to scan and generate image data and send posting parameters to the message app server 300. The example in FIG. 10 shows an example in which "Channel 1" is specified as the posting channel in the posting parameters, "Thread 2" is specified as the posting thread in the posting parameters, and "User 3" belonging to Channel 1 is specified as the user. Also, "document.pdf" is specified as the file name in the posting parameters. This is also an example in which "Send." is specified as the comment. The file name and comment are specified by the user on a scan-to-chat advanced settings screen (not shown).

[0094] Thread message 1007 is a thread message that is displayed when a user with an account for User 1 sends a message with the content "Design Drawings" as the title of Thread 3 to the message app server 300. Even if message information is sent to a channel without specifying a thread, a new thread is generated and a similar screen is displayed.

[0095] The message app screen 1001 also displays the channels, groups, and users the logged-in user is participating in. It also displays the recipient information (1002) and message exchanges (1003). By adding a comment with an "@" prefix to the user's name when posting, a notification is sent to specific users in the channel. In the case of FIG. 10, user 3 can notice that the post has been received before other members of the channel, depending on the device on which the message app is viewed. If the mobile device 200 used by user 3 is a smartphone, the user is notified by an icon notification function, vibration, or ringtone. If the mobile device 200 used by user 3 is a desktop device, the user is notified by a desktop notification function or other means. To display this screen, the message app server 300 searches for and displays the necessary information from the data structure shown in FIG. 9. For example, the message 1004 posted corresponds to the "Thread 2 + Message 3 + File 1" in the exchange content 505. The attribute information of file 1, such as the name of file 1, is obtained from 504 and displayed as a file icon on the message. When the user selects this file icon, they can obtain file 1 belonging to file 504. Note that although the files posted to this channel are displayed as icons here, a preview image of the file may also be displayed.

[0096] FIG. 9 shows an example of a file structure in the message app server. This file structure is stored in the HDD 305 of the message app server 300, and the screen in FIG. 10 is displayed based on this file structure. The message app server 300 manages data by dividing it into smaller groups, such as channels, groups, users, and files, within the largest group called a workspace. Channel 501 is a chat room that all members of the workspace can participate in, and all posted content can be searched by anyone. Group 502 is a channel for discussions that should not be open to all members, and requires an invitation to view and participate. User 503 is a user participating in this workspace. File 504 stores attached files. Thread 506 is a conversation thread included in Channel 1. Threads are created by users, and the owner of Thread 1 is User 2. Threads are linked to channels and contain one or more comments. Furthermore, the content 505 of interactions between channels, threads, groups, and users is linked to and stored. For example, Channel 1 stores users who are participating in Channel 1 in association with it, and also stores messages and image data exchanged on Channel 1 in association with Channel 1. By storing information in this manner, when a channel is selected on the channel selection screen 1119, it is possible to display users and threads corresponding to the specified channel information. It is also possible to display users who are participating in that channel.

[0097] Fig. 13 is a diagram showing an example of a thread selection screen. The thread selection screen of Fig. 13 is an example of a different form of the thread selection screen 1120 described in Fig. 11. The thread selection screen of Fig. 13 can be replaced with the thread selection screen 1120 of Fig. 11.

[0098] When the mode change button 1305 is selected, the thread selection screen in FIG. 13 switches between a time mode screen 1301, a user mode screen 1308, and a channel mode screen 1313 in that order, allowing the information to be narrowed down and rearranged according to each element.

[0099] At this time, the current screen mode can be confirmed by screen titles 1302, 1309, and 1314. When sort button 1304 is selected, the displayed content can be rearranged, and each time it is pressed, the order switches between ascending and descending. Update time 1303 displays the date and time when the thread was last updated. When today button 1307 is selected on time mode screen 1301, if today button 1307 is selected on April 1st, only threads whose last update date was April 1st will be displayed. In other words, threads other than those whose last update date was April 1st will not be displayed. User information 1310 displays the username of the owner who created the thread. It is also possible to narrow down the threads to not only today, but also to last week or a period specified by the user.

[0100] When the user button 1312 is selected on the user mode screen 1308, only threads in which the user currently logged in to the MFP 101 is the thread owner or the thread replyer are displayed. For example, only threads in which the user currently logged in to the MFP 101 has posted a message are displayed. At this time, the user information of the user currently logged in to the MFP 101 is associated with the user information of the chat service. Therefore, the user information on the chat service of the user currently logged in to the MFP 101 can be identified.

[0101] By selecting the "Target Owner Button", only threads whose owner is the user 1309 currently logged in to the MFP 101 are displayed. It is also possible to narrow down the threads to a specific user or group.

[0102] When the user presses the My Channel button 1316 on the channel mode screen 1313, only threads for channels for which the user logged in to the MFP 101 is the administrator are displayed. It is also possible to specify a target channel and display only threads related to that channel. This filtering and sorting screen allows the user to more easily select a thread to upload a file to.

[0103] 13, thread information can be displayed in a display format desired by the user. This is because the thread information received by the MFP 101 from the message application server 300 includes the update date and time of the thread, information about the user who posted to the thread, owner information, etc. The MFP 101 interprets the thread information and displays a thread selection screen such as that shown in FIG.

[0104] In this way, by performing the above process, the image data generated by the image processing device reading the image of the document can be easily uploaded to a desired thread by the user.

[0105] In this embodiment, an example has been described in which the MFP 101 directly communicates with the message app server 300, receives channel information and thread information from the message app server 300, and transmits scanned and generated image data to the message app server 300. This is not limiting, and the above processing may be performed via a relay server, which is an information processing device capable of communicating with multiple MFPs. Specifically, upon receiving the request of S701 from the MFP 101, the relay server transmits the request to the message app server 300. The relay server receives channel information and thread information in response to the request from the message app server 300, and transmits the channel information and thread information to the MFP 101 that transmitted the request. The processing of S705 to S709 is performed by the MFP 101, as in FIG. 7 . The relay server then receives the generated file, channel information, thread information, etc. from the MFP 101, and transmits the received information to the message app server 300.

[0106] The relay server can also store a table in which the connection destinations and token information set in Fig. 12 are associated with each other. This allows for centralized management in the relay server without storing a table in which the connection destinations and token information are associated with each other in the MFP 101, thereby reducing the risk of information leakage.

[0107] Furthermore, in this embodiment, image data or information indicating image data (such as a link) is uploaded (added) to a thread selected on the MFP 101, but there is a possibility that the thread in question on the message app may be deleted while selecting a thread or configuring scan settings on the MFP 101. In that case, a new thread may be created and the image data may be uploaded to that thread.

[0108] Specifically, first, the CPU 301 of the message app server 300 determines that the thread indicated by the thread information included in the request sent by the MFP 101 to the message app server 300 in S710 does not exist in the message app server 300. If the thread exists on the chat service, the process of S711 is executed as is. If the thread does not exist, a notification to that effect is sent to the MFP 101. The MFP 101, having received the notification, sends a new command to the message app server 300 requesting that image data be posted to a new thread. This sending process may be executed automatically without receiving any operation from the user, or may notify the screen of the operation unit 116 that the thread does not exist and prompt the user to upload to the new thread or cancel the upload. Then, based on the user's instruction to upload to the new thread, a request to upload image data to the new thread is sent to the message app server 300. If cancel is selected, the process ends.

[0109] <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]

[0110] 101 MFP 300 Message App Server 400 Bot Server 111 CPU 118 Reading unit

Claims

1. An image processing device capable of communicating with an information processing device, a reading means for reading an image of an original and generating image data; A receiving means for receiving a designation of a thread of a channel of the chat service; a transmitting means for transmitting the image data generated by the reading means and identification information of the thread whose designation has been accepted by the accepting means to the information processing device; The image processing device is characterized in that the image data is added to a thread indicated by the identification information by the information processing device.

2. receiving means for receiving information on a plurality of threads from the information processing device; a display unit that displays the information of the plurality of threads received by the receiving unit, 2. The image processing apparatus according to claim 1, wherein the accepting unit accepts selection of a specific thread from the information on the plurality of threads displayed by the display unit.

3. 3. The image processing apparatus according to claim 2, wherein the display means displays the information on the plurality of threads received by the receiving means based on update dates and times.

4. 4. The image processing device according to claim 2, wherein the display means displays information on a plurality of threads included in a channel selected by a user from a plurality of channels of the chat service.

5. The image processing device according to claim 2, characterized in that the display means, based on the acceptance of a date and time specification from the user by the acceptance means, displays the thread that was updated at the date and time specified by the user from among the information of multiple threads received by the receiving means, and does not display information of threads other than the thread in question.

6. The image processing device according to claim 2, characterized in that the display means, based on the reception means receiving an instruction from the user, displays information about the thread to which the user posted a message from the information about the plurality of threads received by the receiving means, and does not display information about threads other than the thread in question.

7. a conveying means for conveying the document; 7. The image processing apparatus according to claim 1, wherein the reading means reads an image of the document conveyed by the conveying means, and generates the image data.

8. An image processing device as described in any one of claims 1 to 7, characterized in that, based on the reception means receiving an execution instruction from a user, a process of reading an image of the original document by the reading means to generate the image data, and a process of transmitting the image data to the information processing device by the transmission means are executed.

9. An image processing device as described in any one of claims 1 to 8, characterized in that if the specified thread does not exist on the chat service, the sending means sends the image data to the information processing device so that information indicating the image data generated by the reading means is added to a new thread.

10. 10. The image processing device according to claim 1, wherein, when the specified thread does not exist on the chat service, a message indicating that the specified thread does not exist is displayed.

11. A control method for an image processing device capable of communicating with an information processing device, comprising: a reading step of reading an image of a document and generating image data; a reception process for receiving a designation of a thread for a channel of the chat service; a transmitting step of transmitting the image data generated in the reading step and the identification information of the thread, the designation of which is accepted in the accepting step, to the information processing device; The method for controlling an image processing device, wherein the image data is added to a thread indicated by the identification information by the information processing device.

12. 11. A program for causing a computer to execute each of the means of the image processing apparatus according to claim 1.

Images