Scanning device, image processing method, and program

Abstract

To make it easier for a user to check image data generated by scanning a document with a scanning device when the user uploads the image data to a chat service.SOLUTION: A scanning device of the present invention has scanning means for scanning a document and generating image data, and transmitting means for transmitting to a chat server the image data generated by the scanning means and a request to display information indicating that the image data has been posted at a predetermined position on a screen of a talk room, even if a message is posted to the talk room after the image data has been posted to the talk room. The image data transmitted by the transmitting means is posted to the talk room, and the information indicating that the image data has been posted is displayed at the predetermined position on the screen of the talk room.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] The present invention relates to a scanning device, an image processing method, and a program.

Background Art

[0002] Patent Document 1 discloses that image data generated by an image processing device scanning an image of a document is transmitted to a message application server providing a chat service. Thereby, the image data is uploaded and shared on a channel of the chat service.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For example, when message exchanges are performed after uploading image data to a channel (chat room), the image data uploaded from the image processing device is washed away by the messages. Thereby, a user participating in the channel may not notice that the image data has been uploaded.

[0005] The present invention has been made in view of the above problems, and an object thereof is to make it easy for a user to confirm image data when a scanning device uploads image data generated by scanning a document to a chat service.

Means for Solving the Problems

[0006] The present invention provides a scanning device comprising: scanning means for scanning a document and generating image data; and transmitting means for transmitting the image data generated by the scanning means and a request to a chat server to display information indicating that the image data has been transmitted to a chat room at a predetermined position on the chat room screen, even if a message is posted to the chat room after the image data has been transmitted to the chat room; wherein the image data transmitted by the transmitting means is posted to the chat room, and information indicating that the image data has been transmitted is displayed at the predetermined position on the chat room screen. [Effects of the Invention]

[0007] When a scanning device scans a document and uploads the resulting image data to a chat service, it makes it easier for the user to review that image data. [Brief explanation of the drawing]

[0008] [Figure 1] Figure showing an example of the system configuration of the present invention. [Figure 2] A diagram showing an example of the hardware configuration of the image processing device 101. [Figure 3] A diagram showing an example of the hardware configuration of mobile terminal 300. [Figure 4] This diagram shows an example of the hardware configuration of the message application server 400. [Figure 5] A diagram showing an example of the hardware configuration of Bot Server 500. [Figure 6] This figure shows an example of the home screen displayed on the operation unit 207 of the image processing device 101. [Figure 7] This diagram shows an example sequence in which the image processing device 101 scans and generates a file, which is then sent to the message application server 400. [Figure 8] A flowchart illustrating an example of scan-to-chat processing. [Figure 9]This diagram shows an example sequence in which the image processing device 101 scans and generates a file, which is then sent to the message application server 400 via the bot server 500. [Figure 10] A flowchart showing an example of Scan to Chat. [Figure 11] A flowchart showing an example of processing by Bot Server 500. [Figure 12] A diagram showing an example of screen transitions in the scan-to-chat process. [Figure 13] A diagram showing an example of a settings registration screen. [Figure 14] A diagram showing an example of a messaging app's message screen. [Modes for carrying out the invention]

[0009] The embodiments for carrying out the present invention will be described below with reference to the drawings. Note that the configurations shown in the following embodiments are examples, and the present invention is not limited to the illustrated configurations. [Examples]

[0010] An image processing apparatus as one embodiment of the information processing apparatus according to the present invention will be described.

[0011] FIG. 1 is a diagram showing an example of the system configuration of the present invention. The system configuration of this embodiment is composed of an image processing apparatus 101, a message app server 400, and a mobile terminal 300 which is an example of a terminal device and can communicate via a network 100. Also, a bot server 500 is also connected via the network 100 and can communicate. The message app server 400 is a chat server that receives messages and image data transmitted from the image processing apparatus 101 and the mobile terminal 300 and manages and provides a chat service that is displayed on the mobile terminal 300 and a PC (not shown) by a user operation. The bot server 500 associates with information (token information) corresponding to a bot app installed in the message app server 400 connected to the image processing apparatus 101 and transfers a request from the image processing apparatus 101 to the message app server 400. Note that the network 100 of this embodiment may be the Internet or a LAN (Local Area Network). Also, the network 100 may be wired or wireless.

[0012] FIG. 2 is a block diagram for explaining an example of the hardware configuration of the image processing apparatus 101. This example uses a multifunction device having a print function, a scanner function, a data communication function, and the like as an example. Note that the image processing apparatus may be a scanning device.

[0013] The image processing apparatus 101 includes a CPU 202, a ROM 203, a RAM 204, a storage 205, an operation unit I / F 206, an operation unit 207, a reading unit I / F 208, a reading unit 209, a printing unit I / F 210, a printing unit 211, a wireless communication unit I / F 212, and a wireless communication unit 213. Also, the image processing apparatus 101 includes a FAX unit I / F 214, a FAX communication unit 215, a communication unit I / F 216, and a communication unit 217.

[0014] The control unit 201 including the CPU 202 controls the operation of the entire image processing apparatus 101. The CPU 202 reads out the control program stored in the ROM 203 or the storage 205 to the RAM 204, and performs various controls such as reading control and printing control. The ROM 203 stores the control program executable by the CPU 202. Further, the ROM 203 also stores a boot program, font data, and the like. The RAM 204 is a main memory, and is used as a temporary storage area for expanding various control programs stored in the work area, the ROM 203, and the storage 205. The storage 205 stores image data, print data, various programs, and various setting information. In this embodiment, a flash memory is assumed as the storage 205, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may be used. Also, an eMMC (embedded Multi Media Card) may be used.

[0015] Note that, in the image processing apparatus 101 of this embodiment, it is assumed that one CPU 202 uses one memory (RAM 204) to execute each process shown in the flowchart described later, but it is not limited to this. For example, a plurality of CPUs, RAMs, ROMs, and storages may cooperate to execute each process shown in the flowchart described later. Also, some processes may be executed using a hardware circuit such as an ASIC or an FPGA.

[0016] The operation unit I / F 206 connects an operation unit 207 including a display unit such as a touch panel and hard keys to the control unit 201. The operation unit 207 displays information to the user and detects an input from the user.

[0017] The reading unit interface 208 connects the reading unit 209, such as a scanner, to the control unit 201. The reading unit 209 reads the image of the document, and the CPU 202 converts the image into image data such as binary data. The image data generated based on the image read by the reading unit 209 is transmitted to an external device or printed on recording paper. The reading unit included in the scanning means can scan multiple documents placed on an ADF (not shown) and generate multiple image data. In this case, the documents placed on the ADF are transported and scanned by the ADF.

[0018] The printing interface 210 connects the printing unit 211, such as a printer, to the control unit 201. The CPU 202 transfers image data (print data) stored in the RAM 204 to the printing unit 211 via the printing interface 210. The printing unit 211 prints the image based on the transferred image data onto recording paper fed from the paper cassette.

[0019] The wireless communication interface 212 is an interface for controlling the wireless communication unit 213 and connects to the control unit 201 and an external wireless device (in this case, a mobile terminal 300) via wireless communication.

[0020] The control unit 201 connects to the public telephone network 107 by controlling the fax communication unit 215, which is similar to a facsimile machine, via the fax unit interface 214. The fax unit interface 214 is an interface for controlling the fax communication unit 215, and by controlling a modem or NCU for facsimile communication, it is possible to connect to the public telephone network 107 and control the facsimile communication protocol.

[0021] The communication interface 216 connects the control unit 201 to the network 100. The communication interface 216 allows the communication unit 217 to transmit image data and various internal 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. Transmission and reception via the network 100 can be done using email or by sending files using other protocols (e.g., FTP, SMB, WebDAV, etc.). Furthermore, image data and various configuration data can also be transmitted and received over the network 100 via HTTP communication from mobile terminals 300, message application servers 400, and bot servers 500.

[0022] Figure 3 shows an example of the hardware configuration of the mobile terminal 300. In this embodiment, the mobile terminal 300 is assumed to be a device such as a smartphone or tablet PC, but it may be any other information processing device that is capable of Wi-Fi communication.

[0023] The CPU 307 reads the control program stored in the ROM 308 and executes various processes to control the operation of the mobile terminal 300. The ROM 308 stores the control program. The RAM 309 is used as the main memory and temporary storage area for the CPU 307, such as the work area. The HDD 310 stores various data such as photographs and electronic documents.

[0024] The control panel 301 has a touch panel function that can detect user touch operations and displays various screens provided by the OS and email sending application. The control panel 301 is also used to check information stored in the message application server 400. The user can input desired operation instructions to the mobile terminal 300 by inputting touch operations on the control panel 301. The mobile terminal 300 is equipped with hardware keys (not shown), and the user can input operation instructions to the mobile terminal 300 using these hardware keys.

[0025] Camera 304 takes images according to the user's imaging instructions. The images taken by camera 304 are stored in a designated area of ​​HDD 310. It is also possible to obtain information from QR codes read by camera 304 using a program capable of analyzing QR codes (registered trademark).

[0026] The mobile terminal 300 can exchange data with various peripheral devices via the NFC communication unit 305, the Bluetooth® communication unit 306, and the wireless LAN communication unit 311. The Bluetooth communication unit 306 of the mobile terminal 300 may also support Bluetooth® Low Energy.

[0027] Figure 4 shows an example of the hardware configuration of the message application server 400. The CPU 401 reads the control program stored in the ROM 402 and executes various processes to control the operation of the message application server 400. The ROM 402 stores the control program. The RAM 403 is used as the main memory and temporary storage area for the CPU 401, such as the work area. The HDD 405 stores various data such as messages, image data, and channel information. Data can be sent and received with various devices such as the mobile terminal 300, the image processing device 101, and the bot server 500 via the communication unit 404. The communication unit 404 may perform wired communication using Ethernet® or wireless communication such as Wi-Fi.

[0028] Figure 5 shows an example of the hardware configuration of the bot server 500. The CPU 501 reads the control program stored in the ROM 502 to control the operation of the bot server 500 and performs various processes to mediate with the message application server 400 in response to requests from the image processing device 101. The ROM 502 stores the control program. The RAM 503 is used as the main memory and temporary storage area for the CPU 501, such as the work area. The HDD 505 stores various data such as messages, image data, and channel information. Data can be sent and received with various devices such as the mobile terminal 300, the image processing device 101, and the message application server 400 via the communication unit 504.

[0029] Figure 6 shows an example of the home screen displayed on the operation unit 207 of the image processing device 101. The operation unit 207 consists of a touch panel 601 that displays the operation screen and LEDs 610 and 611. The touch panel 601 is an instruction means, and functions as both a receiving means for receiving instructions from the user and a display means for displaying the screen. The user directly touches the screen displayed on the touch panel 601 with an object such as a finger or stylus to instruct the execution of various functions based on the displayed screen.

[0030] The touch panel 601 shown in Figure 6 displays the home screen 608. The home screen 608 is the initial screen for instructing the execution of each function of the image processing device 101, and is a screen for selecting the display of various settings for each function that the image processing device 101 performs, such as copy, fax, scan, and media print.

[0031] The status confirmation button 605 is an object for displaying a screen (status confirmation screen) that allows you to check the status of the image processing device 101. The transmission history and job execution history can be displayed from the status confirmation screen (not shown).

[0032] The scan-to-chat button 602 is an object for displaying the settings screen for the scan-to-chat process. When the scan-to-chat button 602 is selected by the user, the scan-to-chat screen 1201 shown in Figure 12 is displayed on the operation unit 207. The scan-to-chat process is explained in detail in Figures 7 and 8.

[0033] The scan button 603 is an object used by the image processing device 101 to display the scan selection screen (not shown). The scan selection screen is for selecting transmission functions such as email, SMB, FTP, HTTP file transmission, and Internet fax (I-fax) transmission. Touching the object indicating the displayed transmission function will display the settings screen for each transmission function.

[0034] The address book button 604 is an object that, when selected by the user, displays the address book screen of the image processing device 101. LEDs 610 and 611 notify the user of the status of the image processing device 101. LED 610 lights up when receiving or executing emails or print jobs, and LED 611 lights up when any error occurs in the image processing device 101. The stop button 606 is an object that cancels various operations and is always displayed on the operation unit 207. The HOME button 607 is an object that displays the home screen 608 and is always displayed on the operation unit 207. The menu button 612 is an object that displays a screen for configuring environment settings such as the language used and settings for various functions.

[0035] Figure 7 shows an example sequence in which the image processing device 101 scans and generates a file, which is then sent to the message application server 400. The sequence in Figure 7 begins when the channel selection button 1210 on the scan-to-chat screen 1201 in Figure 12 is selected.

[0036] In S701, the CPU 202 of the image processing device 101 controls the communication unit 217 to request channel list information from the message application server 400 via HTTP communication. Specifically, the image processing device 101 sends the token information it has entered and information indicating that it is requesting the channel list in the workspace indicated by that token information to the message application server 400. An example of the command sent here is "HTTP GET https: / / message.com / api / channels.list". The URL "https: / / message.com / api / channels.list" in this command is the URL for accessing the message application server 400. By sending the token information to this URL, the message application server 400 searches for the workspace and bot application corresponding to the token information. The token information is entered by the user via the setting registration screen 1301 shown in Figure 13 on the operation unit 207 of the image processing device 101.

[0037] Here, a workspace is like an organization to which multiple users belong within a messaging app. A channel is like a chat room within a workspace. In this context, a chat room is a mechanism for multiple users participating in the chat room to send and receive messages and communicate in a conversational manner. In this embodiment, channels are described as chat rooms, but this is not limited to this, as long as it is a mechanism for multiple users to send and receive messages and communicate in a conversational manner. For example, it could be a group chat, room, talk room, or group.

[0038] Here, a bot application is an application that registers the image processing device 101 as a user within the messaging application and is used to post messages and image data. It is installed on the messaging application server 400. By specifying a bot application and sending image data to the messaging application server 400, the bot application posts the received image data in the messaging application. The HDD 405 of the messaging application server 400 stores bot applications and tokens in association, and also associates bot applications with workspaces. Therefore, by receiving token information from the image processing device 101, the messaging application server 400 can return information about the workspace associated with the bot application associated with that token information. Alternatively, the token information, bot application, and workspace may be directly associated. This allows the user to select a workspace (the workspace to which they want to send image data) from among many workspaces that corresponds to the pre-registered token information.

[0039] In S702, the CPU 401 of the message application server 400 checks whether access to the URL is permitted based on the token information received from the image processing device 101 via the communication unit 404. If permitted, it generates channel list information included in the workspace corresponding to the token information. The channel list information is an array of information indicating channel information. The channel information includes the channel ID, the channel name, information indicating the users participating in that channel, and channel setting values ​​indicating settings such as whether or not it is an archive channel.

[0040] In S703, the CPU 401 of the message application server 400 controls the communication unit 404 and sends channel list information to the image processing device 101 as HTTP communication response information.

[0041] In S704, the CPU 202 of the image processing device 101 generates a channel selection screen 1211 based on the channel information contained in the received channel list information. Then, when the channel selection button 1210 is selected by the user, the CPU 202 of the image processing device 101 displays the channel selection screen 1211 on the touch panel 601 of the operation unit 207 and waits for user input. The channel selection screen 1211 will be described later in the explanation of Figure 12.

[0042] In S705, the CPU 202 of the image processing device 101 confirms the information of the target channel for posting when at least one channel is selected on the channel selection screen 1211 and the back button 1212 is selected.

[0043] In S706, the CPU 202 of the image processing device 101 receives a scan execution command via the operation unit 207.

[0044] In S707, the CPU 202 of the image processing device 101 performs a scan using the scan settings at the time it receives a scan execution command.

[0045] In S708, the CPU 202 of the image processing device 101 generates image data in the format set in the scan settings for the scanned image. The scan settings used are those specified by the user on the detailed settings screen for scan-to-chat (not shown). The scan settings may also be displayed and set together with the transmission settings on the transmission settings screen 1209 in Figure 12.

[0046] In S709, the CPU 202 sends the same token information as in S701, the destination channel information selected in S705, the file format, and the image data generated in S708 to the message application server 400 via HTTP communication through the communication unit 217. The file format used is the one specified by the user on the Scan to Chat sending settings screen 1209. On the sending settings screen 1209, the user can enable or disable pinning of the image data to be posted using button 1215. Furthermore, if pin replacement is enabled, and there is already a pinned post in the selected channel, that post will be unpinned and the image data post to be sent will be pinned. If pin replacement is disabled, and there is already a pinned post in the selected channel, it will not be replaced by the new post. In other words, the image data post to be sent will not be pinned. It is also possible to pin multiple posts if there are already pinned posts.

[0047] In S710, the CPU 401 of the message application server 400 searches for the workspace information and application information registered using the token information received in S709, and stores the received image data associated with the channel specified by the channel information. Furthermore, if a recipient user is specified, the CPU 401 also stores the received image data, channel, and recipient user in association. As a result, when a user launches the message application on their mobile device 300 and selects a channel to check the content of the conversation in that channel, the screen showing the received image data has been posted is displayed.

[0048] In S711, the CPU 401 of the message application server 400 sends a result corresponding to whether the posting was successful or not, and if successful, a timestamp that uniquely identifies the posted image data, as HTTP communication response information to the image processing device 101. Here, a timestamp is added to the response information as a response in the case of success, but any information that uniquely identifies the image data posted as a message could be used, such as a message ID. If the posting is successful, the CPU 202 of the image processing device 101 may display a notification on the operation unit 207 indicating that the posting was successful. If the posting fails, the CPU 202 of the image processing device 101 may display a notification on the operation unit 207 indicating that the posting failed. Alternatively, no notification may be displayed when the posting is successful, and a notification indicating that the posting failed may only be displayed when the posting fails.

[0049] If the image processing device 101 receives a timestamp in the response information that uniquely identifies the image data post, which was received from the message application server 400 when the post was successful, in S711 the processing in S712 to S714 is performed.

[0050] In S712, the CPU 202 of the image processing device 101 transmits the same token information as in S701, the information of the posting destination channel selected in S705, and the timestamp information received in S711 to the message application server 400 via the communication unit 217. Furthermore, it sends a pinning request via HTTP communication to notify users in the channel of the posted image data. Here, pinning is a function that fixes information indicating that a specific post has been made in a predetermined position, such as at the top of the channel screen. This function ensures that the specific post remains displayed in its predetermined position even if messages are posted after the specific post has been made. Alternatively, instead of displaying it in a fixed position such as at the top of the channel screen, notification methods such as changing the background color of the message or adding an icon and comment to indicate that it is pinned may be used, allowing users to check it from the pinned message list on the menu screen. It may also have a function that moves to the post displayed on the timeline when the pinned post is selected. In other words, when the image data post is not displayed in the chat room, the image data post will be displayed in the chat room when the object corresponding to the information indicating that the image data has been posted is selected. A specific example is explained in Figure 14. In this embodiment, the method of notifying users within a channel of a message is called "pinning," but it is not limited to this; for example, it could also be called an announcement function.

[0051] In S713, the CPU 401 of the message application server 400 identifies a post containing image data from the timestamp information received in S712 and enables the pinning function for that post. In other words, the scanned and generated image data is posted to the chat room, and information indicating that the image data has been posted is displayed in a designated location on the chat room screen. As a result, when a user launches the message application on their mobile device 300 and selects a channel to check the content of the previous channel's conversation, the image data posted in S709 is displayed on the screen in a pinned state.

[0052] In S714, the CPU 401 of the message application server 400 sends a result corresponding to whether or not pinning was successful to the image processing device 101 as HTTP communication response information. If pinning is successful, the CPU 202 of the image processing device 101 may display a notification to the operation unit 207 indicating that pinning was successful. If pinning fails, the CPU 202 of the image processing device 101 may display a notification to the operation unit 207 indicating that pinning failed. Alternatively, no notification may be displayed when pinning is successful, and a notification indicating that pinning failed may only be displayed when it fails.

[0053] In this embodiment, the processes S712 to S714 may be performed if the user has enabled pinning using button 1215 in Figure 12.

[0054] Figure 8 is a flowchart illustrating an example of the scan-to-chat process. The flow in Figure 8 is initiated when the image processing device 101 is powered on.

[0055] In S801, CPU202 determines whether the scan-to-chat button 602 is selected. If it is selected, proceed to S802. Otherwise, return to S801.

[0056] In S802, the CPU 202 displays the scan-to-chat screen 1201 on the touch panel 601 of the operation unit 207. Here, Figure 12 will be used to explain the screen transition when the scan-to-chat button 602 is selected.

[0057] Figure 12 shows an example of the screen transitions for the scan-to-chat process. When the scan-to-chat button 602 displayed on the home screen 608 is selected, the scan-to-chat screen 1201 is displayed on the touch panel 601 of the operation unit 207.

[0058] The Scan to Chat screen 1201 displays a destination confirmation button 1202. The destination confirmation button 1202 displays the number of destinations set as the recipients for the scanned and generated image data. The example in Figure 12 illustrates a case where one channel is selected as the recipient. If multiple destinations are selected, the number of set destinations will be displayed as the number of destinations.

[0059] When the destination confirmation button 1202 is selected, the scan-to-chat destination confirmation screen 1203 is displayed. The scan-to-chat destination confirmation screen 1203 displays the destination settings configured by selecting the channel selection button 1210. The destination button 1204 displays the destination currently set, and when selected by the user, the destination confirmation screen 1203 displaying the set destination (recipient) is displayed. In addition, when the destination button 1204 is set, a details screen (not shown) is displayed, showing the details of the set destination.

[0060] In this embodiment, only one destination is displayed on the scan-to-chat destination confirmation screen 1203, but this is not the only option. For example, the image processing device 101 can set multiple destinations from the message application server 400, allowing multiple destination buttons to be displayed on the scan-to-chat destination confirmation screen 1203.

[0061] If Reset 1205 is selected on the Scan-to-Chat screen 1201, the configured information will be cleared. In this case, the configured destination information will be cleared. Also, if the Black and White Start button 1206 or Color Start button 1207 is selected on the Scan-to-Chat screen 1201, the scanning and sending process will begin.

[0062] When the Send Settings button 1208 is selected, the Send Settings screen 1209 is displayed. On this screen, you can change and check send settings such as File Settings 1214. Button 1215 allows you to set whether to enable or disable pinning. Button 1216 can only be selected when pinning is enabled, and cannot be selected if pinning is disabled using button 1215.

[0063] When the channel selection button 1210 is selected, the channel selection screen 1211 is displayed. The channels and users displayed on this channel selection screen 1211 are displayed based on the channel list information received by the image processing device 101 from the message application server 400. On this screen, it is possible to select the destination channel for posting and which users belonging to that channel should be notified. 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 dropdown menu. On this screen, both a channel and users can be selected, or only the channel can be selected to post to all users belonging to that channel. Furthermore, multiple channels can be selected, and different users belonging to each channel can be selected.

[0064] When the back button 1212 is selected, the channel selection is retained, and the scan-to-chat screen 1201 is displayed again. At this time, the destination field 1213 displays the name of the selected channel to which the message will be posted and the name of the user to whom the notification will be sent, which is "Destination: Channel 3 @ User 1". The CPU 202 of the image processing device 101 also stores the destination based on the channel and user set at this time in RAM 204 or storage 205.

[0065] Now, let's return to the explanation of the flow in Figure 8. In S802, the CPU 202 displays the scan-to-chat screen 1201 shown in Figure 12 on the operation unit 207. In S803, the CPU 202 detects that the channel selection button 1210 has been selected.

[0066] In S804, CPU202, upon selection of the channel selection button, uses pre-registered token information 1303 to send information to the message application server 400 indicating that channel information is requested via HTTP communication.

[0067] Here, we will explain the settings registration screen shown in Figure 13. Figure 13 is a diagram showing an example of the settings registration screen. The settings registration screen 1301 is a screen displayed on the operation unit 207 of the image processing device 101. The settings registration screen 1301 may also be displayed as a web page on the operation unit of an information processing device such as a PC connected to the image processing device 101 via a network. The contents registered on the settings registration screen 1301 are recorded on the storage 205 in Embodiment 1, and on the HDD 505 in Embodiment 2.

[0068] The "Connection Destination 1302" column shows the organization information of the connection destination. The "Token Information 1303" column shows the registered token information. The "Operation Buttons 1304" column shows the operation buttons. This item displays the edit button 1305 and the generate button 1306.

[0069] When the edit button 1305 is selected, strings such as token information and connection destination information can be entered and modified using the keyboard. When the generate button 1306 is selected, the home screen 608 is set to display the scan to chat button 602. In Example 1, the contents registered on the settings registration screen 1301 are stored in the storage 205.

[0070] When the new registration button 1307 is pressed, it accepts text input from the user, allowing them to add connection destination and token information and register.

[0071] Now, let's return to explaining the flow in Figure 8. In S805, CPU 202 determines whether or not it has received channel information from the message application server 400 in response to the channel acquisition request sent in S804. Specifically, it determines that it has not received channel list information if the status code in the HTTP communication response is an error, or if the response body information contains a parameter indicating that the information could not be acquired. If it determines that it has been received, it proceeds to S808. Otherwise, it proceeds to S806.

[0072] In S806, CPU202 displays information on channel selection screen 1211 indicating that it could not receive channel list information. At this time, no channel or user options are displayed on channel selection screen 1211.

[0073] In S807, CPU202 determines whether the back button 1212 is selected or not. If it is selected, it returns to S802. Otherwise, it returns to S806.

[0074] In S808, the CPU 202 displays a channel selection screen 1211 on the touch panel 601 of the operation unit 207, which displays channel information received from the message application server 400.

[0075] In S809, the CPU 202 detects, via the touch panel 601 of the operation unit 207, whether the posting destination (channel, or channel and user) selected on the channel selection screen has been confirmed. If confirmed, the process transitions to S810 and updates the posting channel list information. If not confirmed, the process transitions to S808. Confirmation is detected by whether the back button 1212 has been selected. Note that if the screen configuration displays a confirmation button on the screen of the operation unit 207, the same transition occurs when the confirmation button is selected.

[0076] In S810, the CPU 202 displays the scan-to-chat screen 1201 shown in Figure 12 on the operation unit 207 and updates the display in the destination field 1213 with the destination confirmed in S809. At this time, along with the destination channel, the information of the user to be notified is also displayed.

[0077] In S811, the CPU 202 determines whether the monochrome start button 1206 or the color start button 1207 displayed on the control panel 207 has been selected. If it is determined that it has been selected, the process proceeds to S812. Otherwise, the process returns to S811.

[0078] In S812, the CPU 202 controls the reading unit 209 based on the scan settings to read the image of the document and generate image data. The scan settings used are those specified by the user in the detailed settings screen for scan-to-chat (not shown).

[0079] In S813, CPU202 converts the image data generated by S812 into file format 1214, which is set on the transmission settings screen.

[0080] In S814, CPU202 generates posting parameters. These parameters include the destination channel, file format, file name, and post comment. The file format is set to the file format 1214 specified in the sending settings. The post comment is generated by adding an "@" symbol to the beginning of the user information to be notified. The file name is the file name specified in the sending settings.

[0081] In S815, CPU202 uses pre-registered token information 1303 to send the file generated in S813 and posting parameters to the message application server 400 via the POST method of HTTP communication. By sending this data (the converted image data file and posting parameters) to the message application server 400, the message application server 400 controls the posting of the received file to the receiving user in the receiving channel.

[0082] In S816, the CPU 202 receives the posting result and, if successful, timestamp information that uniquely identifies the posted file from the message application server 400, and displays the posting result on the touch panel 601 of the operation unit 207.

[0083] In S817, it is determined whether the file posting to the message application server 400 in S815 was successful. If it is determined to be successful, proceed to S818. Otherwise, terminate the flow.

[0084] In S818, CPU202 uses the pre-registered token information 1303 and a timestamp that uniquely identifies the posted file to send a request to the message application server 400 to pin the posted file. Pinning will be explained in Figure 14 below.

[0085] In S819, CPU202 determines whether pinning was successful based on the result information received from message application server400. If pinning is successful, proceed to S820. Otherwise, proceed to S821.

[0086] In S820, the CPU 202 receives the posting results from the message application server 400 and displays them on the touch panel 601 of the operation unit 207.

[0087] In S821, the CPU 202 determines whether pin replacement is enabled using button 1216 on the transmission settings screen 1209 in Figure 12. If it is determined to be enabled, the process proceeds to S822. If it is determined not to be enabled, the process proceeds to S820.

[0088] In S822, CPU202 enables the function to replace the originally pinned message via the POST method of HTTP communication to the message application server 400, and then pins the message again.

[0089] This embodiment allows users to easily post files from the image processing device 101 to a channel on the message application server 400 and pin the posted files. Furthermore, even if the pinning process fails because a pinned message already exists, it is possible to replace the already pinned message.

[0090] Then, depending on whether the user selects the start buttons 1206 or 1207, the reading unit 209 scans the document and generates image data, and the communication unit 217 sends the image data and a pinning request to the message application server 400. This allows the user to have the document scanned and the image data and pinning request sent with a single execution command.

[0091] In this embodiment, it is assumed that only one token is registered. However, if multiple tokens are registered, the processes involving the token information, such as S804, S815, and S818, will be executed for each registered token.

[0092] The image data converted in S815 and the posting parameters are sent to the message application server 400, and pinned to the posted file in S818, so that the screen is displayed on the operation panel 301 of the mobile terminal 300. An example of that screen is explained using Figure 14.

[0093] Figure 14 shows an example of a message screen in a messaging application. The message screen 1401 in Figure 14(a) is displayed when the messaging application is launched on the mobile terminal 300 and the processing S815 and S818 are executed in the image processing device 101. The mobile terminal 300 is also communicating with the messaging application server 400.

[0094] The message screen 1401 displays the channels, groups, and users that the logged-in user is a part of. It also displays channel information (1402) and message exchanges (1403). When posting, adding an "@" symbol to the beginning of the username indicates that the recipient of the post specifically wants to inform that user within the channel (1404). In Figure 14, user 3 can notice the post earlier than other members of the channel through a notification received on the messaging app's viewing device. If user 3's viewing mobile device 300 is a smartphone, the user is notified via icon notification, vibration, or ringtone. If user 3's viewing mobile device 300 is a desktop device, the user is notified via desktop notification or similar methods.

[0095] When a user launches the messaging app on their mobile device 300 and logs in using their account ID and password, a screen specific to that user is displayed.

[0096] Message 1404 is displayed (posted) when a user with the user 1 account sends image data generated by scanning with the image processing device 101 and posting parameters to the message application server 400, and pins it in S818. In the example in Figure 14(a), "Channel 1" is specified as the posting channel in the posting parameters, and "User 3," who belongs to Channel 1, is specified as the user. Also, "Document.pdf" is specified as the file name in the posting parameters, and "Sending." is specified as the comment. The file name and comment are specified by the user in the detailed settings screen of Scan to Chat (not shown). Furthermore, to indicate that the image processing device 101 has pinned the message, the background color of the message is changed, and a pin icon and the comment "Image processing device has pinned" are displayed at the top of the message. In this example, when the channel menu button 1405 is selected, the channel details screen 1406 is opened, and the pinned message 1407 is displayed on that screen. By selecting the message from this list, it is possible to refer to the original message. Here, message 1404 was pinned via the POST method of HTTP communication from the image processing device 101 at S818 in Figure 8, but pinning can be done in other ways. For example, one can open the message screen 1401 from the mobile terminal 300, hover the mouse pointer over the message to be pinned, and select "Pin" from the message's menu screen. Alternatively, the message can be pinned by long-pressing the message and selecting "Pin".

[0097] Furthermore, Figure 14(b) shows another example of pinning, displaying a comment 1408 indicating that the message has been pinned in a location separate from the message itself, and a list of pinned messages 1409 at the top of the channel. The pinned messages 1407 and 1409 also display identifying information such as the username of the user who posted the message.

[0098] Figures 14(a) and 14(b) describe the message screen when a message is pinned. This screen is displayed when the message application server 400 enables the pinning function for a message in S713 of Figure 7. [Examples]

[0099] In Example 1, an example was described in which the image processing device 101 directly sends image data and posting parameters to the message application server 400. In this example, an example is described in which the image processing device 101 sends image data and posting parameters to the message application server 400 via the bot server 500.

[0100] Figure 9 shows an example of a sequence in which the image processing device 101 scans and generates a file, which is then sent to the message application server 400 via the bot server 500.

[0101] In S901, the CPU 202 of the image processing device 101 requests channel list information from the bot server 500 via HTTP communication, using the device ID or user ID as a parameter.

[0102] In S902, the CPU 501 of the bot server 500 sends information to the message application server 400 indicating a request for channel list information via HTTP communication, using token information corresponding to the received device ID or user ID. This token information is obtained in S901 and corresponds to the device ID or user ID received.

[0103] In S903, the CPU 401 of the message application server 400 checks whether access to the URL is permitted based on the token information. If permitted, it generates channel list information included in the workspace corresponding to the token information. Channel list information is an array of information that represents channel information. Channel information includes the channel ID, the channel name, information indicating the users participating in that channel, and channel setting values ​​indicating settings such as whether or not it is an archive channel.

[0104] In S904, the CPU 401 of the message application server 400 controls the communication unit 404 to send channel list information to the bot server 500 as HTTP communication response information.

[0105] In S905, the CPU 501 of the bot server 500 sends the channel list information received in S905 to the image processing device 101 as an HTTP communication response.

[0106] The processing in S906-S910 is similar to the processing in S704-S708 in Figure 7, so we will omit the explanation.

[0107] In S911, the CPU 202 of the image processing device 101 sends information such as the device ID or user ID, information about the posting channel, file format, and image data to the bot server 500 via HTTP communication.

[0108] In S912, the CPU 501 of the bot server 500 executes the process of sending the received destination channel information, file format information, image data, and token information corresponding to the received device ID or user ID to the message application server 400. Here, the CPU 501 refers to a table stored in the HDD 505 that associates device IDs or user IDs with token information to determine the token information to send.

[0109] The process in S913 is the same as that in S710, so its explanation will be omitted.

[0110] In S914, the CPU 401 of the message application server 400 sends a result corresponding to whether the post was successful or not, and if successful, a timestamp that uniquely identifies the posted image data, as HTTP communication response information to the bot server 500.

[0111] If, in S914, the bot server 500 successfully posts from the message application server 400, and the response information contains a timestamp that uniquely identifies the image data posted as a message, then the processes in S915 to S917 are performed. If, in S914, the bot server 500 receives response information from the message application server 400 indicating a failed post, the process proceeds to S918.

[0112] In S915, the CPU 501 sends information about the destination channel, token information, and a timestamp information that uniquely identifies the image data posted as a message to the target channel in S914 to the message application server 400 via the communication unit 504.

[0113] The processing in S916 is the same as that in S713, so it will be omitted.

[0114] In S917, the CPU 401 of the message application server 400 sends a result corresponding to whether or not the pinning was successful to the bot server 500 as HTTP communication response information.

[0115] In S918, the CPU 501 of the bot server 500 sends the result corresponding to whether the post received in S914 failed, or whether the pinning received in S917 was successful, to the image processing unit as HTTP communication response information. If the post and pinning are successful, the CPU 202 of the image processing unit 101 may display a notification on the operation unit 207 indicating that the post was successful. If the post or pinning fails, the CPU 202 of the image processing unit 101 may display a notification on the operation unit 207 indicating that the post or pinning failed. Alternatively, no notification may be displayed when the post and pinning are successful, and a notification indicating that the post failed may only be displayed when the post or pinning fails.

[0116] Furthermore, while this embodiment uses channel lists for acquisition, group lists with access restrictions and user lists for individual posts can also be posted using the same method.

[0117] Figure 10 is a flowchart showing an example of scan-to-chat processing. The process in the flowchart in Figure 10 is executed when the CPU 202 reads the program stored in ROM 203 into RAM 204 and executes it. The flow in Figure 10 also starts when the power to the image processing device 101 is turned on.

[0118] Since the processes in S1001 to S1003 are the same as those in S801 to S803, their explanation will be omitted.

[0119] In S1004, CPU202 obtains the user ID of the user logged into image processing device 101 or the device ID of image processing device 101, and sends a request to the bot server 500 via HTTP communication, along with the user ID or device ID.

[0120] Since the processing in S1005-S1014 is the same as that in S805-S814, the explanation will be omitted.

[0121] In S1015, the CPU 202 sends the user ID of the user logged into the image processing device 101 or the device ID of the image processing device 101, along with the file generated in S1013 and the posting parameters. In Example 1, an example was described in which a file is sent to the message application server 400 using pre-registered token information 1303, but this is not the only example. For example, the storage 205 of the image processing device 101 may store the user ID or device ID in association with the token information, and the request or file transmission may be executed using the token information corresponding to the user ID or device ID of the logged-in user.

[0122] In this embodiment, the logged-in user ID and device ID are used for communication with the bot server 500, but any uniquely determined identifier, such as a tenant ID, can also be used.

[0123] Figure 11 is a flowchart illustrating an example of the processing performed by the bot server 500. Figure 11(a) is a flowchart illustrating an example of the processing performed when the bot server 500 obtains the message application server 400 ID and channel information. Figure 11(b) is a flowchart illustrating an example of the processing performed when the bot server 500 sends image data to the message application server 400. The processing in Figures 11(a) and (b) is performed when the CPU 501 reads the program stored in ROM 502 into RAM 503 and executes it.

[0124] First, let's explain Figure 11(a). In S1101, the CPU 501 determines whether or not it has received an information acquisition request from the image processing device 101 to obtain the device ID or user ID and channel information. If it determines that it has received the information, it proceeds to S1102. Otherwise, it returns to S1101.

[0125] In S1102, the CPU 501 obtains token information corresponding to the device ID or user ID received from the image processing device 101.

[0126] In S1103, the CPU 501 determines whether or not there is token information corresponding to the received device ID or user ID. If it is determined that there is, the process proceeds to S1104. Otherwise, the process proceeds to S1105. Also, if it is determined that there is token information, the RAM 503 stores the token information corresponding to the received device ID or user ID.

[0127] In S1104, the CPU 501 sends the information acquisition request received from the image processing device 101 in S1101 to the message application server 400 using the token information identified in S1103. The information returned from the message application server 400 in response to the transmission is sent to the image processing device 101.

[0128] In S1105, CPU 501 sends information indicating an execution error to image processing device 101 as a response to the request received in S1101.

[0129] Next, we will describe an example of the process when the bot server 500 sends image data to the message application server 400, as shown in Figure 11(b).

[0130] In S1106, the CPU 501 determines whether or not it has received a request to post image data from the image processing device 101. If it determines that it has received a request, it proceeds to S1107. Otherwise, it returns to S1106.

[0131] In S1107, the CPU 501 sends the information of the destination channel received from the image processing device 101, the ID of the user logged into the image processing device 101 or the ID of the image processing device 101, image data, and posting parameters to the message application server 400.

[0132] In S1108, CPU 501 receives a result from the message application server 400 indicating whether the post was successful or not, and if successful, a timestamp that uniquely identifies the image data posted as a message, and determines whether the post was successful or not. If it is determined to be successful, proceed to S1109. Otherwise, proceed to S1110.

[0133] In S1109, CPU 501 sends information about the target channel, token information, and a timestamp information that uniquely identifies the image data posted to the target channel in S1107 to the message application server 400.

[0134] In S1110, the CPU 501 sends to the image processing device 101 the result of the failed post to the message application server 400 in S1107, or the result of whether or not the image data was successfully pinned in S1109.

[0135] This embodiment makes it possible to update the bot server 500 program without uploading the image processing device 101 program, even if the interface specifications of the message application server 400 are changed. Furthermore, in workplaces with multiple image processing devices, file posting can be performed without individually configuring tokens for each image processing device.

[0136] <Other embodiments> The present invention provides a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium. It can also be implemented by a process in which one or more processors in the computer of the system or device read and execute the program. Furthermore, it can also be implemented by a circuit (e.g., an ASIC) that implements one or more functions.

[0137] Furthermore, the disclosure of this embodiment includes the following configuration.

[0138] (Composition 1) A scanning method that scans a document and generates image data, The system includes a transmission means that sends to a chat server the image data generated by the scanning means, and a request to display information indicating that the image data has been posted at a predetermined location on the chat room screen, even if a message is posted to the chat room after the image data has been posted to the chat room. A scanning device characterized in that the image data transmitted by the transmitting means is posted to the talk room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the talk room.

[0139] (Configuration 2) It also has a means of receiving requests from users to specify a chat room, The transmitting means transmits to the chat server the image data generated by the scanning means, the information of the talk room, and the request to display information indicating that the image data has been posted at a predetermined position on the screen of the designated talk room, even if a message is posted to the talk room after the image data has been posted to the designated talk room. The scanning device according to Configuration 1, characterized in that the image data transmitted by the transmitting means is posted to the designated chat room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the designated chat room.

[0140] (Composition 3) The system further includes a receiving means for receiving information from multiple talk rooms from the aforementioned chat server, The scanning device according to configuration 2, characterized in that the receiving means accepts the designation of a talk room from among the multiple talk rooms indicated by the information of the multiple talk rooms received by the receiving means.

[0141] (Composition 4) The aforementioned request is a request for pinning, The scanning device according to Configuration 1, characterized in that, if there is a post that is pinned in the chat room before the image data is posted, the sending means sends the request, which unpins the post and pins the post containing the image data.

[0142] (Composition 5) The scanning device according to configuration 4, further comprising setting means for determining whether or not to unpin posts in the chat room before the image data is posted, by sending the request.

[0143] (Composition 6) The scanning device according to configuration 1, characterized in that the information indicating that the image data has been posted includes the identification information of the user who posted the image data.

[0144] (Composition 7) The scanning device according to Configuration 1, characterized in that, when the posted image data is not displayed in the chat room, the posting of the image data is displayed in the chat room when an object corresponding to the information indicating that the image data has been posted is selected.

[0145] (Composition 8) The scanning apparatus according to configuration 1, characterized in that the scanning means scans multiple documents that have been transported and generates multiple image data.

[0146] (Composition 9) It further includes a means for receiving execution instructions from the user, The scanning device according to Configuration 1, characterized in that, upon receiving the instruction receiving means, the scanning means scans the document to generate image data, and the transmission means transmits the generated image data and the request to the chat server.

[0147] (Composition 10) The scanning process involves scanning the original document to generate image data, The process includes sending the image data generated in the scanning process and a request to the chat server to display information indicating that the image data has been posted, even if a message is posted to the chat room after the image data has been posted to the chat room, at a predetermined location on the chat room screen. An image processing method characterized in that the image data transmitted in the transmission step is posted to the talk room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the talk room.

[0148] (Composition 11) The system further includes a process for receiving user requests for chat rooms. In the transmission step, the image data generated in the scanning step, the information of the talk room, and the request to display information indicating that the image data has been posted at a predetermined position on the screen of the designated talk room, even if a message is posted to the talk room after the image data has been posted to the designated talk room, are sent to the chat server. The image processing method according to configuration 10, characterized in that the image data transmitted in the transmission step is posted to the designated chat room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the designated chat room.

[0149] (Composition 12) The system further includes a receiving step of receiving information from multiple talk rooms from the aforementioned chat server, The image processing method according to configuration 11, characterized in that the reception step accepts the designation of a talk room from among the multiple talk rooms indicated by the information of the multiple talk rooms received in the reception step.

[0150] (Composition 13) The aforementioned request is a request for pinning, The image processing method according to configuration 10, characterized in that, if there is a post that is pinned in the chat room before the image data is posted, the pinning is released and the post containing the image data is pinned when the request is sent in the transmission step.

[0151] (Composition 14) The image processing method according to configuration 13, further comprising a setting step to determine whether or not to unpin a post in the chat room before the image data is posted, based on the transmission of the request in the transmission step.

[0152] (Composition 15) The image processing method according to configuration 10, characterized in that the information indicating that the image data has been posted includes the identification information of the user who posted the image data.

[0153] (Composition 16) The image processing method according to configuration 10, characterized in that, when the posted image data is not displayed in the chat room, the posted image data is displayed in the chat room by selecting an object corresponding to the information indicating that the image data has been posted.

[0154] (Composition 17) The image processing method according to configuration 10, characterized in that in the scanning step, multiple documents that have been transported are scanned and multiple image data are generated.

[0155] (Composition 18) It further includes an instruction receiving process that receives execution instructions from the user, The image processing method according to configuration 10, characterized in that, in response to receiving the execution instruction in the instruction receiving step, the document is scanned in the scanning step to generate image data, and the generated image data and the request are sent to the chat server in the transmission step.

[0156] (Composition 19) A program for causing a computer to execute each of the means of the scanning device described in Configuration 1. [Explanation of symbols]

[0157] 101 Image Processing Device 400 Message application servers 500 bot servers 202 CPU 209 Reading Unit

Claims

1. A scanning method that scans a document and generates image data, The system includes a transmission means that sends to a chat server the image data generated by the scanning means, and a request to display information indicating that the image data has been posted at a predetermined location on the chat room screen, even if a message is posted to the chat room after the image data has been posted to the chat room. A scanning device characterized in that the image data transmitted by the transmitting means is posted to the talk room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the talk room.

2. It also has a means of receiving requests from users to specify a chat room, The transmitting means transmits to the chat server the image data generated by the scanning means, the information of the talk room, and the request to display information indicating that the image data has been posted at a predetermined position on the screen of the designated talk room, even if a message is posted to the talk room after the image data has been posted to the designated talk room. The scanning device according to claim 1, characterized in that the image data transmitted by the transmitting means is posted to the designated talk room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the designated talk room.

3. The system further includes a receiving means for receiving information from multiple talk rooms from the aforementioned chat server, The scanning device according to claim 2, characterized in that the receiving means accepts the designation of a talk room from among the multiple talk rooms indicated by the information of the multiple talk rooms received by the receiving means.

4. The aforementioned request is a request for pinning, The scanning device according to claim 1, characterized in that, if there is a post that is pinned in the chat room before the image data is posted, the sending means sends the request, thereby unpinning the post and pinning the post containing the image data.

5. The scanning device according to claim 4, further comprising setting means for determining whether or not to unpin posts in the chat room before the image data is posted, by sending the request.

6. The scanning device according to claim 1, characterized in that the information indicating that the image data has been posted includes the identification information of the user who posted the image data.

7. The scanning device according to claim 1, characterized in that, when the posted image data is not displayed in the chat room, the posting of the image data is displayed in the chat room by selecting an object corresponding to the information indicating that the image data has been posted.

8. The scanning apparatus according to claim 1, characterized in that the scanning means scans a plurality of transported documents and generates a plurality of image data.

9. It further includes a means for receiving execution instructions from the user, The scanning apparatus according to claim 1, characterized in that, in response to the instruction receiving means receiving the execution instruction, the scanning means scans the document to generate image data, and the transmission means transmits the generated image data and the request to the chat server.

10. The scanning process involves scanning the original document to generate image data, The process includes sending the image data generated in the scanning process and a request to the chat server to display information indicating that the image data has been posted, even if a message is posted to the chat room after the image data has been posted to the chat room, at a predetermined location on the chat room screen. An image processing method characterized in that the image data transmitted in the transmission step is posted to the talk room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the talk room.

11. The system further includes a process for receiving user requests for chat rooms. In the transmission step, the image data generated in the scanning step, the information of the talk room, and the request to display information indicating that the image data has been posted at a predetermined position on the screen of the designated talk room, even if a message is posted to the talk room after the image data has been posted to the designated talk room, are sent to the chat server. The image processing method according to claim 10, characterized in that the image data transmitted in the transmission step is posted to the designated chat room, and information indicating that the image data has been posted is displayed at the predetermined position on the screen of the designated chat room.

12. The system further includes a receiving step of receiving information from multiple talk rooms from the aforementioned chat server, The image processing method according to claim 11, characterized in that the reception step accepts the designation of a talk room from among the multiple talk rooms indicated by the information of the multiple talk rooms received in the reception step.

13. The aforementioned request is a request for pinning, The image processing method according to claim 10, characterized in that, if there is a post that is pinned in the chat room before the image data is posted, the pinning is released and the post containing the image data is pinned when the request is sent in the transmission step.

14. The image processing method according to claim 13, further comprising a setting step to determine whether or not to unpin posts in the chat room before the image data is posted, based on the transmission of the request in the transmission step.

15. The image processing method according to claim 10, characterized in that the information indicating that the image data has been posted includes the identification information of the user who posted the image data.

16. The image processing method according to claim 10, characterized in that, when the posted image data is not displayed in the chat room, the posted image data is displayed in the chat room by selecting an object corresponding to the information indicating that the image data has been posted.

17. The image processing method according to claim 10, characterized in that in the scanning step, multiple documents that have been transported are scanned and multiple image data are generated.

18. It further includes an instruction receiving process that receives execution instructions from the user, The image processing method according to claim 10, characterized in that, in response to receiving the execution instruction in the instruction receiving step, the document is scanned in the scanning step and image data is generated, and the generated image data and the request are transmitted to the chat server in the transmission step.

19. A program for causing a computer to execute each of the means of the scanning apparatus described in claim 1.

Images