Program, scanning device, and control method thereof.

Abstract

To make it easy for a user to search for a talk room which displays image data generated by an image processing device and to reduce the possibility that authentication information for a chat service flows out when specifying the talk room.SOLUTION: An information processing device that communicates with a chat server for displaying received image data in a talk room of a received chat server on the basis of information indicating the talk room comprises: receiving means for receiving prescribed information corresponding to a user by transmitting authentication information for logging into the chat service by the user to the chat server; storing means for replacing the prescribed information received by the receiving means with the authentication information and storing the authentication information in association with identification information used by the user to log into the image processing device; and displaying means for displaying a talk room corresponding to the prescribed information without displaying a talk room not corresponding to the prescribed information.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 an image processing device that transmits image data generated by scanning an image of a document to a file server on a network in order to share the image data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-126318 Summary of the Invention [Problem to be solved by the invention]

[0004] When a user uses a chat service available on the Internet to display scanned image data in a chat room of the chat service, the following problem occurs: As in Patent Document 1, an image processing device that transmits generated image data to a file server via SMB communication or the like cannot specify a chat room for the chat service, and the image data cannot be displayed in the desired chat room.

[0005] Furthermore, when specifying a talk room for a chat service on an image processing device, if all talk rooms used within an organization are displayed, the user may have to search for and select a desired talk room from among a large number of talk rooms, which can be cumbersome. Therefore, it is conceivable that the image processing device may store user identification information for logging in to the image processing device and user authentication information for the chat service in association with each other.

[0006] When authentication information of users of a chat service is stored in an image processing device used by many users, there is a possibility that the authentication information used in the chat service may be leaked.

[0007] Authentication information used for chat services can also be used for other services, so if login authentication information is leaked, it could be used to illegally log in to services other than chat services.

[0008] The present invention has been made in consideration of the above-mentioned problems, and aims to make it easier for users to find a talk room when specifying a talk room to display image data generated by an image processing device, while reducing the possibility of chat service authentication information being leaked. [Means for solving the problem]

[0009] The image processing device of the present invention is an image processing device that communicates with a chat server and controls to display received image data in a talk room based on received information indicating a talk room of the chat server, a reading means for reading an image of a document and generating image data based on the image; a receiving means for receiving predetermined information corresponding to the user, the predetermined information being generated by the chat server by the user transmitting authentication information for logging in to the chat service to the chat server; a storage means for storing the predetermined information received by the receiving means in place of the authentication information, in association with identification information for a user to log in to the image processing device; The communication device is characterized by having a display means for displaying talk rooms corresponding to the predetermined information, while not displaying talk rooms that do not correspond to the predetermined information. [Effects of the Invention]

[0010] When specifying a talk room in which to display image data generated by an image processing device, the user can easily find the talk room while reducing the possibility of chat service authentication information being leaked. [Brief explanation of the drawings]

[0011] [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. 6 is a diagram showing an example of a table 601 that associates various IDs with token information. [Figure 8] FIG. 8 is a diagram showing an example of a sequence in which the MFP 101 creates the table 601 in FIG. 7. [Figure 9] A flowchart showing the sequence of steps in which the MFP 101 creates the table 601 in FIG. 7. [Figure 10] Figure showing an example of an ID setting registration screen [Figure 11] An example of the screen transition for scan-to-chat processing [Figure 12] 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 13] A flowchart showing an example of scan-to-chat processing executed by the MFP 101. [Figure 14] A diagram showing an example of a message screen in a messaging app [Figure 15] A diagram showing an example of the file structure in the Message App server [Figure 16]FIG. 10 shows an example of a sequence in which a file generated by scanning by the MFP 101 is transmitted to the message application server 300 via the bot server 400. [Figure 17] 1 is a flowchart showing an example of a scan-to-chat process executed via the bot server 400. [Figure 18] 10 is a flowchart showing an example of a process when the bot server 400 transmits image data to the message application server 300. DETAILED DESCRIPTION OF THE INVENTION

[0012] 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. [Example]

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

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

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

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

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

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

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

[0020] 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 102) via wireless communication.

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

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

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

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

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

[0026] 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).

[0027] 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 Low Energy.

[0028] FIG. 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, images, and channel information. Data can be exchanged with 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.

[0029] Here, when a user uses a chat service available on the Internet to display image data generated by scanning in a chat room of the chat service, the following problem arises: As in Patent Document 1, an image processing device that transmits generated image data to a file server via SMB communication or the like does not allow a user to specify a chat room for the chat service, and the user is unable to display the image data in the desired chat room.

[0030] Furthermore, when specifying a talk room for a chat service on an image processing device, if all talk rooms used within an organization are displayed, the user may have to search for and select a desired talk room from among a large number of talk rooms, which can be cumbersome. Therefore, it is conceivable that the image processing device may store user identification information for logging in to the image processing device and user authentication information for the chat service in association with each other.

[0031] When authentication information of users of a chat service is stored in an image processing device used by many users, there is a possibility that the authentication information used in the chat service may be leaked.

[0032] Since the authentication information used for the chat service can also be used for other services, if the authentication information for logging in is leaked, it may be possible to illegally log in to services other than the chat service. In order to solve the above problem, the following process is performed.

[0033] 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 403 stores the control program. The RAM 402 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.

[0034] 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 501 that displays the operation screen, and LEDs 510 and 511. Touch panel 501 is an instruction means, and functions as both an acceptance means that accepts instructions from the user and a display means that displays the screen. The user directly touches the screen displayed on touch panel 501 with an object such as a finger or a stylus to instruct the execution of each function based on the displayed screen.

[0035] 6 displays a home screen 508. The home screen 508 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.

[0036] A status check button 505 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).

[0037] The scan-to-chat button 502 is an object for displaying a settings screen for the scan-to-chat process. When the scan-to-chat button 502 is selected by the user, the settings screen 1004 in Fig. 11 is displayed on the operation unit 116. The scan-to-chat process will be described in detail with reference to Figs. 12 and 13.

[0038] The chat registration button 509 is an object for displaying a screen for setting up a link between authentication information used by the MFP 101 and authentication information used by the message app server 300. Here, the authentication information used by the MFP 101 is, for example, information input by a user to log in to the MFP 101, and is made up of a combination of a user ID (or a user name) and a password. Also, the authentication information used by the message app server 300 is information input by a user to log in to a message service, and is made up of a combination of a user ID (or a user name) and a password.

[0039] When the chat registration button 509 is selected by the user, a setting screen 901 in Fig. 10 is displayed on the operation unit 116. The chat registration process will be described in detail with reference to Figs.

[0040] The scan button 503 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 (Email), 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.

[0041] An address book button 504 is an object for displaying an address book screen of the MFP 101 when selected by the user. LEDs 510 and 511 notify the user of the status of the MFP 101. LED 510 lights up while an e-mail or a print job is being received or executed, and LED 511 lights up when an error occurs in the MFP 101. A stop button 506 is an object for canceling various operations and is an object that is always displayed on the operation unit 116. A home button 507 is an object for displaying a home screen 508 and is an object that is always displayed on the operation unit 116. A menu button 512 is an object for displaying a screen for setting environment settings such as the language to be used and for setting each function.

[0042] 7 is a diagram showing an example of a table 601 that stores the association between authentication information used in the MFP 101 and authentication information used in the message service. In this embodiment, the table is held in the storage 114 in the MFP 101 by the sequence shown in FIG.

[0043] The MFP-userID 602 ​​is part of the authentication information (user ID) required when a user logs in to the MFP 101. The APP-userID 603 is information corresponding to an account on the message service, and an individual APP-userID is associated with each user. The token information 604 is information for specifying a workspace managed by the message application server 300. For example, when the MFP 101 transmits this token information 604 to the message application server 300, the MFP 101 can obtain information about the workspace corresponding to the token information 604. In the table of FIG. 7, the MFP-userID 602, the APP-userID 603, and the token information 604 are stored in association with each other.

[0044] 8 is a diagram showing an example of a sequence in which MFP 101 generates table 601. This sequence is started when chat registration button 509 displayed on home screen 508 is selected. This sequence is also executed when CPU 111 of MFP 101 reads a program stored in ROM 112 into RAM 113.

[0045] In S701, the CPU 111 of the MFP 101 inputs the MFP-user ID 602 ​​and password via the input screen 901 in Fig. 10 displayed on the operation unit 116. Note that if the MFP 101 is configured to require login using the MFP-user ID 602 ​​input when it is used, S701 can be omitted by storing the input MFP-user ID 602 ​​in the RAM 113. When the login button 902 on the input screen 901 is selected, the process proceeds to S702.

[0046] In S702, the CPU 111 of the MFP 101 accepts an input operation from the user via the input screen 903 in FIG. 10 displayed on the operation unit 116, inputs a login ID and password for the message application server 300, and stores them in the RAM 113. The login ID input here is information separate from the APP-userID 603. When the confirm button 904 on the input screen 903 is selected, the process proceeds to S703.

[0047] In addition, the login ID and password for a messaging service may also be used for other services, such as webmail services, cloud storage services, and other messaging services, so it is not desirable for the login ID and password for this messaging service to be leaked.

[0048] In S703, the CPU 111 of the MFP 101 requests the message app server 300 to acquire token information 604 via HTTP communication. Specifically, the CPU 111 transmits information indicating a request to generate and return token information from the login ID and password entered in S702 to the message app server 300. An example of the command transmitted here is "HTTP GET https: / / message.com / api / oath.access". The URL "https: / / message.com / api / oath.access" described in this command is a URL for accessing the message app server 300, and is a URL registered in advance in the MFP 101 by the user. By transmitting the login ID and password entered in S702 to this URL, the message app server 300 executes S704, which is a token generation process.

[0049] In S704, the CPU 301 of the message application server 300 generates token information 604 using the login ID and password received via the communication unit 304. The token information 604 generated here is stored in the message application server 300 in association with the APP-user ID 603 and the workspace. Therefore, when the message application server 300 receives the token information 604 from the MFP 101, it is possible to identify the APP-user ID 603 and the workspace.

[0050] In step S705, the CPU 301 of the message application server 300 controls the communication unit 304 to transmit the token information 604 to the MFP 101 as response information of the HTTP communication.

[0051] In S706, the CPU 111 of the MFP 101 makes a request to the message application server 300 via HTTP communication to acquire the APP-userID 603. Specifically, information indicating a request for the APP-userID 603 corresponding to the token information 604 acquired in S705 is sent to the message application server 300. An example of the command to be sent here is "HTTP GET https: / / message.com / api / users.identity". The URL described in this command is a URL for accessing the message application server 300, similar to the command used in S703. By sending the token information to this URL, the message application server 300 executes S707, which is a process of searching for the APP-userID 603 corresponding to the token information.

[0052] In S707, the CPU 301 of the message application server 300 refers to the token information received via the communication unit 304, and searches the HDD 305 for the APP-user ID 603 included in the token information.

[0053] In step S708, the CPU 301 of the message application server 300 controls the communication unit 304 to transmit the APP-userID 603 to the MFP 101 as response information of the HTTP communication.

[0054] In S709, the CPU 111 of the MFP 101 associates the received token information 604 and APP-user ID 603 with the MFP-user ID 602 ​​input in S701, as shown in table 601, and stores them in the storage 114. When the processing in S709 ends, the login ID and password for the message service input in S702 are deleted from the RAM 113.

[0055] 9 is a diagram showing an example of a flow in which MFP 101 generates table 601. This flow is started when chat registration button 509 is pressed on home screen 508. The flow in FIG. 9 is executed when CPU 111 of MFP 101 reads a program stored in ROM 112 into RAM 113.

[0056] In step S801, the CPU 111 of the MFP 101 displays an input screen 901 on the touch panel 501, which is a screen for accepting the MFP-user ID 602.

[0057] In S802, when the CPU 111 of the MFP 101 detects selection of the login button 902 on the input screen 901 via the operation unit 116, the CPU 111 stores the input MFP-user ID 602 ​​in the RAM 113. The CPU 111 also displays on the touch panel 501 a screen S903 for accepting the login ID and password for the message application server 300.

[0058] In S803, when the CPU 111 of the MFP 101 detects selection of the confirm button 904 via the operation unit 116, it stores the input login ID and password information in the RAM 113, and proceeds to processing in S804.

[0059] In step S804, the CPU 111 of the MFP 101 uses the input login ID and password to request the message application server to obtain the APP-userID 603.

[0060] In S805, the CPU 111 of the MFP 101 determines whether or not the acquisition of the APP-userID 603 from the message application server was successful. If it is determined that the acquisition was successful, the process proceeds to S808. If it is determined that the acquisition was unsuccessful, the process proceeds to S806.

[0061] In step S806, the CPU 111 of the MFP 101 displays a message indicating that acquisition has failed on the touch panel 501. Although the completion screen 905 shows a message indicating successful acquisition, the message displayed on this screen is changed to indicate that acquisition has failed.

[0062] In S807, when the CPU 111 of the MFP 101 detects that a back button (not shown) displayed on the touch panel 501 has been pressed, it changes the displayed screen to the input screen 901, which is the initial screen, and returns to S801.

[0063] In step S808, the CPU 111 of the MFP 101 creates a table using the MFP-userID 602 ​​and APP-userID 603 stored in the RAM 113, and stores the table in the storage 114. The MFP 101 also displays a completion screen 905 on the touch panel 501.

[0064] In S809, the CPU 111 of the MFP 101 detects the pressing of the button 906 via the operation unit 116, and thereby transitions the display screen to the home screen 508, and ends the processing.

[0065] 11 is a diagram showing an example of screen transitions during scan-to-chat processing. When the scan-to-chat button 502 displayed on the home screen 508 is selected, a scan-to-chat screen 1004 is displayed on the touch panel 501.

[0066] A destination confirmation button 1005 is displayed on the scan to chat screen 1004. The destination confirmation button 1005 displays the number of destinations set as destinations for posting image data generated by scanning. In this embodiment, the destination confirmation button 1005 will be used to explain an example in which one channel, which is the posting destination, is selected. If multiple destinations are selected, the number of set posting destinations is displayed as the number of destinations.

[0067] When the destination confirmation button 1005 is selected, a scan-to-chat destination confirmation screen 1006 is displayed. The scan-to-chat destination confirmation screen 1006 displays the transmission setting posting destinations that were set when the channel selection button 1013 was selected. Post destination buttons 1007 are displayed as many times as the number of posting destinations that are set at that time, and when selected by the user, the destination confirmation screen 1006 is displayed, displaying the set posting destinations (destinations). Furthermore, when the post destination button 1007 is set, a details screen (not shown) is displayed, and details of the set posting destinations are displayed.

[0068] In this embodiment, only one posting destination is displayed on the scan-to-chat destination confirmation screen 1006, but this is not limited to this. 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 1006.

[0069] When the reset button 1008 is selected on the scan-to-chat screen 1004, the set information is cleared. At this time, the set destination information is also cleared. When the black and white start button 1009 or the color start button 1010 is selected on the scan-to-chat screen 1004, the scan and send process is started.

[0070] When the transmission setting button 1011 is selected, a transmission setting screen 1012 is displayed. On this screen, transmission settings such as transmission file settings 1017 can be changed and confirmed.

[0071] When the channel selection button 1013 is selected, a channel selection screen 1014 is displayed. The channels and users displayed on this channel selection screen 1014 are displayed based on the channel list information that the MFP 101 receives from the message application server 300. In this embodiment, not all channels included in the received channel list information are displayed, but only channels to which the account used on the message service by the user logged in to the MFP 101 belongs.

[0072] On this channel selection screen 1014, 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 in order to post to all users belonging to that channel. It is also possible to select multiple channels, or to select one channel and then be able to select multiple users within that channel. It is also possible to select multiple channels and then be able to select different users belonging to each channel.

[0073] When the back button 1015 is selected, the channel selection is maintained and the scan-to-chat screen 1004 is displayed again. At this time, the destination field 1016 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 the storage 114.

[0074] Fig. 12 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. 12 is started in response to selection of the channel selection button 1013 on the scan-to-chat screen 1004 in Fig. 11. Note that this sequence starts in a state in which the user's MFP-user ID 602 ​​and token information 604 are previously stored in association with each other in the storage 114, and a certain user is logged in to the MFP 101.

[0075] In S1101, the CPU 111 of the MFP 101 controls the communication unit 126 to request channel list information from the message app server 300 via HTTP communication. Specifically, the MFP 101 transmits to the message app server 300 token information 604, which has been stored in advance in association with the user, and information indicating a request for a channel list in the workspace indicated by the token information 604. An example of the command to be transmitted 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 transmitting the token information 604 to this URL, the message app server 300 searches for the workspace and bot app corresponding to the token information 604. The token information 604 is stored in association with the MFP-userID 602 ​​of the user using the MFP 101.

[0076] Here, a workspace is like an organization to which multiple users belong within a messaging app. Also, a channel is like a chat room within a workspace. The 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, a room, a talk room, or a group.

[0077] 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 604 to be selected from a large number of workspaces.

[0078] In S1102, the CPU 301 of the message app server 300 refers to the token information 604 received via the communication unit 304, and searches the HDD 305 for workspace information and a bot app included in the token information.

[0079] In S1103, the CPU 301 of the message application server 300 checks whether access to the URL is permitted based on the token information 604 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 a channel ID, the name of the channel, an APP-user ID indicating the users participating in the channel, and a channel setting value indicating settings such as whether the channel is an archived channel.

[0080] In step S1104, the CPU 301 of the message application server 300 controls the communication unit 304 to transmit the channel list information to the MFP 101 as response information of the HTTP communication.

[0081] In step S1105, the CPU 111 of the MFP 101 displays, on the channel selection screen 1014, only channels associated with the APP-userID 603 linked to the MFP-userID 602 ​​of the currently logged-in user from the received channel list information.

[0082] In S1106, the CPU 111 of the MFP 101 generates a channel selection screen 1014 based on the channel list information newly generated in S1105. Then, upon detecting a press of the channel selection button 1013 via the operation unit 116, the CPU 111 of the MFP 101 displays the channel selection screen 1014 on the touch panel 501 and waits for a user operation.

[0083] In S1107, the CPU 111 of the MFP 101 detects that at least a channel has been selected on the channel selection screen 1014 and that the back button 1015 has been pressed via the operation unit 116, thereby finalizing the information on the channel to which the message is to be posted.

[0084] In step S1108, the CPU 111 of the MFP 101 receives a scan execution instruction via the operation unit .

[0085] In step S1109, the CPU 111 of the MFP 101 performs scanning according to the scan settings when the scan execution instruction is received.

[0086] In step S1110, the CPU 111 of the MFP 101 generates the scanned image as image data in the 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 also be displayed and set together with the transmission settings on the transmission settings screen 1012 in FIG. 11.

[0087] In S1111, the CPU 111 of the MFP 101 transmits the following information to the message app server 300 via the communication unit 126. The transmitted information includes the same token information 604 as in S1101, information about the destination channel selected in S1107, the file format, and the image data generated in S1110, all transmitted via HTTP. Note that the file format used is the file format specified by the user on the scan-to-chat transmission settings screen 1012.

[0088] In S1112, the CPU 301 of the message app server 300 searches for the workspace information and app information registered in the token information 604 received in S1111, and stores the received image data in association with the channel specified in the channel information. If a destination user is specified, the CPU 301 also stores the received image data in association with the channel and the destination user. As a result, when the user starts the message app on the mobile terminal 200 and specifies a channel to check the content of the conversation on the channel, a screen on which the received image data has been posted is displayed.

[0089] In S1113, 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 touch panel 501. If the posting is unsuccessful, the CPU 111 of the MFP 101 may display a notification indicating that the posting was unsuccessful on the touch panel 501. 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.

[0090] Fig. 13 is a flowchart showing an example of scan-to-chat processing executed by MFP 101. This flowchart starts when MFP 101 is powered on, and CPU 111 reads a program stored in ROM 112 into RAM 113 and executes it, thereby executing the processing of the flowchart in Fig. 13. Note that a condition for starting this flowchart is that MFP-userID 602 ​​has been stored in storage 114 in advance by means of a login authentication flow or the like.

[0091] In S1201, the CPU 111 determines whether or not the scan-to-chat button 502 has been selected. If it is determined that the scan-to-chat button 502 has been selected, the process proceeds to S1202. If not, the process returns to S1201.

[0092] In step S1202 , the CPU 111 displays the scan-to-chat screen 1004 on the touch panel 501 .

[0093] In S1203, the CPU 111 detects that the channel selection button 1013 has been selected.

[0094] In step S1204, the CPU 111 executes the following process in response to the selection of the channel selection button 1013. The process that is executed is to send information indicating a request for channel information via HTTP communication to the message application server 300, using the token information 604 associated with the MFP-user ID 602 ​​stored in the RAM 113.

[0095] In S1205, the CPU 111 determines whether or not channel information has been received from the message application server 300 in response to the channel acquisition request sent in S1204. Specifically, if the status code in the HTTP communication response is an error or if the body information of the response includes a parameter indicating that the information cannot be acquired, it determines that the channel list information has not been received. If it is determined that the channel list information has been received, the process proceeds to S1208. If not, the process proceeds to S1206.

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

[0097] In S1207, the CPU 111 determines whether or not the back button 1015 has been selected. If it is determined that the back button 1015 has been selected, the process returns to S1202. If not, the process returns to S1206.

[0098] In S1208, the CPU 111 selects only the channel associated with the APP-user ID 603 linked to the MFP-user ID 602 ​​stored in the RAM 113 from the channel information acquired in S1204.

[0099] In S1209, the CPU 111 displays on the touch panel 501 a channel selection screen 1014 on which information about the channel selected in S1208 and the like is displayed.

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

[0101] In S1211, the CPU 111 displays the scan-to-chat screen 1004 on the touch panel 501, and updates the display of the posting destination field 1016 with the posting destination confirmed in S1210. At this time, information about the user to be notified is also displayed along with the posting destination channel.

[0102] In S1212, the CPU 111 determines whether or not the monochrome start key 1009 or color start key 1010 displayed on the touch panel 501 has been selected. If it is determined that the key has been selected, the process proceeds to S1213. If not, the process returns to S1212.

[0103] In step S1213, 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 those specified by the user on a scan-to-chat advanced settings screen (not shown).

[0104] In S1214, the CPU 111 converts the image data generated in S1213 into the file format 1017 set on the transmission setting screen.

[0105] In S1215, CPU 111 generates posting parameters. The posting parameters include the posting destination channel, file format, file name, and posted comment. The file format is set to one corresponding to the file format 1017 set in the transmission 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 transmission settings.

[0106] In S1216, the CPU 111 uses the pre-registered token information 604 to send the file generated in S1214 and the posting parameters by the POST method of HTTP communication to the message app server 300. 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 controls the received file to be posted to the user who received it on the channel that received it.

[0107] In step S1217 , the CPU 111 receives the posting result from the message application server 300 and displays it on the touch panel 501 .

[0108] The above process allows the user to easily post a file from the MFP 101 to a channel in the server with which the user is associated.

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

[0110] Fig. 14 is a diagram showing an example of a message screen of a message application. A message screen 1301 in Fig. 14 is displayed when the message application is started on the mobile terminal 200 and the processing of S1015 is executed on the MFP 101. In addition, the mobile terminal 200 is in communication with the message application server 300.

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

[0112] Message 1304 is a message that is displayed (posted) by a user having an account for User 1 using MFP 101 to send image data generated by scanning and posting parameters to message app server 300. In the example of FIG. 14, "Channel 1" is specified as the posting channel in the posting parameters, and "User 3" belonging to Channel 1 is specified as the user. In addition, "document.pdf" is specified as the file name in the posting parameters, and "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).

[0113] The message app screen 1301 also displays the channels, groups, and users that the logged-in user is participating in. It also displays the other party's information (1302) and the message exchange (1303). By adding a comment with "@" at the beginning of the user's name when posting, the recipient of the post indicates that they want to notify a specific user in the channel (1304). In the case of FIG. 14, 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 the like.

[0114] To display the message app screen 1301, the message app server 300 searches for and displays the necessary information from the data structure shown in Fig. 15. For example, the posting of message 1304 corresponds to "Message 3 + File 1" in the exchange content 1405, and attribute information such as the name of File 1 is obtained from 1404 and displayed in the form of a file icon on the message. When the user selects this file icon, File 1 belonging to File 1404 can be obtained. Note that, although the files posted to this channel are displayed as icons here, a preview image of the file may also be displayed.

[0115] FIG. 15 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. 14 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 1401 is a chat room that all members of the workspace can participate in, and all posted content can be searched by anyone. Group 1402 is a channel for discussions that should not be open to all members, and requires an invitation to view and participate. User 1403 is a user participating in this workspace. File 1404 stores attached files. Furthermore, content 1405 of exchanges between channels, groups, and users is stored in association with each other. For example, Channel 1 stores users participating in Channel 1 in association with Channel 1, and messages and image data exchanged on Channel 1 are also stored in association with Channel 1. This storage allows users corresponding to the specified channel information to be displayed when a channel is selected on the channel selection screen 1014.

[0116] By performing the above processing, when specifying a talk room in which to display image data generated by an image processing device, it is possible to make it easier for users to find a talk room while reducing the possibility of chat service authentication information being leaked.

[0117] In this embodiment, the channel selection screen 1014 displays only the channels to which the account used by the user logged in to the MFP 101 in the chat service belongs, but the present invention is not limited to this. For example, a setting may be made to switch whether or not to display only the channels to which the account used by the user logged in to the MFP 101 in the chat service belongs. If the setting is not made to display only the channels to which the account used by the user logged in to the MFP 101 in the chat service belongs, all channels corresponding to the workspace corresponding to the token information transmitted in S1101 are displayed. Note that the channels corresponding to the workspace corresponding to the token information transmitted in S1101 include the channels to which the account used by the user in the chat service belongs. [Example]

[0118] In the first embodiment, an example was described in which the MFP 101 directly transmits image data and posting parameters to the message application server 300. In the present embodiment, an example will be described in which the MFP 101 transmits image data and posting parameters to the message application server 300 via the bot server 400. In the present embodiment, an example will be described in which the HDD 405 of the bot server 400 stores the table 601 described in the first embodiment. The table 601 generation flow in the first embodiment shown in FIGS. 8 and 9 can be applied as is by replacing the MFP 101 with the bot server 400 and the CPU 111 of the MFP 101 with the CPU 401 of the bot server 400, and therefore a description thereof will be omitted.

[0119] 16 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 via the bot server 400. The sequence in FIG. 16 is started in response to selection of the channel selection button 1013 on the scan-to-chat screen 1004 in FIG.

[0120] In S1501, the CPU 111 of the MFP 101 transmits to the bot server 400 the MFP-user ID 602 ​​and information indicating that channel list information is being requested via HTTP communication.

[0121] In S1502, the CPU 401 of the bot server 400 selects the token information 604 corresponding to the received MFP-user ID 602 ​​from the table 601. Then, the CPU 401 transmits, to the message application server 300 via HTTP communication, information indicating a request for channel list information, together with the token information 604.

[0122] In S1503, the CPU 301 of the message application server 300 searches the token information 604 for registered workspace information and bot applications.

[0123] In S1504, the CPU 301 of the message application server 300 checks whether the executed URL is permitted based on the application information, and if it is permitted, generates list information of channels belonging to the workspace. The channel list information is array information of channel information. The channel information includes setting values ​​such as the channel ID, the channel name, the APP-user ID list of members belonging to the channel, and whether it is an archive channel.

[0124] In S1505, the CPU 301 of the message application server 300 controls the communication unit 304 to transmit the channel list information to the bot server 400 as response information of the HTTP communication.

[0125] In S1506, the CPU 401 of the bot server 400 selects, from the received channel list information, a channel associated with the APP-user ID 603 linked to the MFP-user ID 602 ​​received in S1501, and creates a channel list for transmission to the MFP 101.

[0126] In S1507, the CPU 401 of the bot server 400 transmits the channel list information created in S1506 as a response to the HTTP communication to the MFP 101. In addition, the CPU 111 of the MFP 101 displays the channels included in the received channel list information on the channel selection screen 1014.

[0127] The processing in steps S1508 to S1512 is similar to the processing in steps S1106 to S1110 in FIG. 12, and therefore a description thereof will be omitted.

[0128] In S1513, the CPU 111 of the MFP 101 transmits the MFP-user ID 602, information about the posting channel, information indicating the file format, etc., and image data to the bot server 400 via HTTP communication.

[0129] In S1514, the CPU 401 of the bot server 400 executes the following process: The process that is executed is to transmit the received destination channel information, information indicating the file format, image data, and token information 604 corresponding to the received MFP-userID 602 ​​to the message app server 300.

[0130] The processing in S1515 is the same as the processing in S1112, and therefore the explanation will be omitted.

[0131] In S1516, the CPU 301 of the message application server 300 transmits a result indicating whether the posting was successful or not to the bot server 400 as response information of the HTTP communication.

[0132] In S1517, CPU 401 of bot server 400 transmits a result indicating whether or not the posting was successful to MFP 101 as HTTP communication response information. If the posting is successful, CPU 111 of MFP 101 may display a notification indicating that the posting was successful on touch panel 501. If the posting is unsuccessful, CPU 111 of MFP 101 may display a notification indicating that the posting was unsuccessful on touch panel 501. 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.

[0133] Furthermore, in this embodiment, a channel list is acquired, but a group list with access restrictions and a user list for individual posting can also be posted in the same way.

[0134] Fig. 17 is a flowchart showing an example of scan-to-chat processing. The processing of the flowchart in Fig. 17 is performed by CPU 111 reading a program stored in ROM 112 into RAM 113 and executing it. The flow in Fig. 17 starts when MFP 101 is powered on.

[0135] The processing in steps S1701 to S1703 is the same as the processing in steps S1201 to S1203, and therefore the description thereof will be omitted.

[0136] In S1704, the CPU 111 acquires the MFP-user ID 602 ​​and transmits a channel information acquisition request and the MFP-user ID 602 ​​to the bot server 400 via HTTP communication.

[0137] The processing of S1705 to S1707 is the same as the processing of S1205 to S1207, and therefore a description thereof will be omitted. In addition, the processing equivalent to S1208 is processed on the bot server 400 side and is therefore not performed by the MFP 101 in this embodiment, and the subsequent processing of S1708 to S1714 is the same as the processing of S1209 to S1215, and therefore a description thereof will be omitted.

[0138] In S1715, the CPU 111 transmits the MFP-user ID 602, the file generated in S1713, and the posting parameters. Note that, although the example in which a file is transmitted to the message application server 300 using pre-registered token information 604 has been described in the first embodiment, the present invention is not limited to this. For example, the storage 114 of the MFP 101 may store only token information, and the request or file transmission may be executed using token information selected by the user.

[0139] In S1716 , the CPU 111 receives the posting result from the message application server 300 and displays it on the touch panel 501 .

[0140] In this embodiment, the MFP-user ID 602 ​​is used for communication with the bot server 400, but a tenant ID or the like can also be used as long as it is a unique identifier.

[0141] Fig. 18 is a flowchart showing an example of the processing when the bot server 400 transmits image data to the message application server 300. The processing of the flowchart in Fig. 18 is executed by the CPU 401 reading a program stored in the ROM 402 into the RAM 403 and executing it. The flow in Fig. 18 is started when the power of the bot server 400 is turned on.

[0142] In S1801, the CPU 401 determines whether or not an information acquisition request for acquiring the MFP-user ID 602 ​​and channel information has been received from the MFP 101. If it is determined that the request has been received, the process proceeds to S1802. If not, the process returns to S1801.

[0143] In step S1802 , the CPU 401 acquires token information corresponding to the MFP-user ID 602 ​​received from the MFP 101 .

[0144] In S1803, the CPU 401 determines from the table 601 whether or not there is token information 604 corresponding to the received MFP-user ID 602. If it is determined that there is, the process proceeds to S1804. If not, the process proceeds to S1807. If it is determined that there is, the RAM 403 stores the received MFP-user ID 602.

[0145] In S1804, the CPU 401 transmits the information acquisition request received from the MFP 101 in S1801 to the message application server 300 using the token information 604 identified in S1803.

[0146] In S1805, the CPU 401 determines whether or not channel list information has been returned from the message application server 300. If it has been returned, the process proceeds to S1806. If it has not been returned, the process returns to S1805.

[0147] In S1806, the CPU 401 transmits channel list information including channels corresponding to the APP-userID 603 linked to the MFP-userID 602 ​​from the received channel list information to the MFP 101, and ends the process. Note that the channel list does not include channels that do not correspond to the APP-userID 603.

[0148] In step S1807, the CPU 401 transmits information indicating an execution error to the MFP 101 as a response to the request received in step S1801, and ends the process.

[0149] 18 has been described as an example of when the MFP-userID 602 ​​and information acquisition request transmitted in S1501 of the sequence in Fig. 16 are received. The same process as in Fig. 18 is performed when the MFP-userID 602, file (image data), and destination channel information transmitted in the processing of S1513 are received. That is, if there is token information 604 corresponding to the received MFP-userID 602, the token information 604, destination channel information, and file (image data) are transmitted to the message application server 300. If there is no token information 604 corresponding to the received MFP-userID 602, information indicating an error is transmitted to the MFP 101.

[0150] According to this embodiment, even if the interface specifications of the message application server 300 are changed, this can be realized by simply updating the program of the bot server without uploading the program of the MFP 101. Furthermore, in a workplace with multiple MFPs, file posting can be performed without having to set a token individually for each MFP.

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

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

Claims

1. A program executed by a scanning device, After the scanning device receives authentication information, a display step is performed in which multiple channels of the chat service are displayed on the display unit of the scanning device. A first reception step that accepts the user's selection of a channel from the multiple channels displayed, The scanning device is instructed to perform a second reception step, which involves receiving a user's selection of a key for receiving an execution instruction displayed on the display unit, Both the scanning process, which involves scanning a document to generate image data, and the transmission process, which involves transmitting the generated image data, are performed by the scanning device based on a single key selection received in the second reception step while the channel is selected. The image data transmitted by the transmission process, which is executed based on a single key selection, is stored in association with the selected channel. A program characterized by the following features.

2. The scanning device further performs a third receiving step of receiving instructions from the user, In the display step, upon receiving the instruction, multiple channels of the chat service are displayed on the display unit of the scanning device. The program according to feature 1.

3. The program according to claim 2, characterized in that in the third reception step, the authentication information is received by the scanning device, and the instruction is received after authentication is performed using the authentication information.

4. The program according to claim 1, characterized in that the authentication information is stored in association with the user using the scanning device.

5. The program according to claim 1, characterized in that in the display step, the channel of the chat service to which the first account corresponding to the authentication information belongs is displayed on the display unit.

6. The program according to claim 5, characterized in that, in the display step, channels to which the first account does not belong are not displayed on the display unit.

7. The program according to claim 1, characterized in that the scanning device further causes the scanning device to perform a second display step of displaying the key on the display unit.

8. The program according to claim 7, characterized in that in the second display step, a reset key for resetting the set information, information indicating a file format specified by the user, a key for checking the job execution history by the scanning device, and a key for accepting the execution instruction are all displayed on the same screen.

9. The program according to claim 7, characterized in that in the second display step, the key, the selected channel, and information indicating the file format specified by the user are displayed on the same screen.

10. The program according to claim 7, characterized in that in the second display step, the selected channel and the scan settings are displayed on the same screen.

11. The program according to claim 10, characterized in that in the second display step, the key, the selected channel, and the scan settings are displayed on the same screen.

12. The program according to claim 7, characterized in that the screen on which the keys are displayed is different from the screen on which the user selects a channel from the plurality of channels.

13. The program according to any one of claims 1 to 12, characterized in that when the transmission process is executed, the image data and the information of the selected channel are transmitted to the server, and the image data is stored in association with the selected channel.

14. The scanning device further performs a fourth receiving step of receiving scan settings, In the aforementioned scanning process, the document is scanned based on the scan settings, and image data is generated. The program according to any one of claims 1 to 13.

15. The program according to any one of claims 1 to 14, characterized in that the scanning device further performs a printing step of printing an image onto paper.

16. The scanning device is further made to perform a receiving step of receiving information from the plurality of channels, In the display step, the multiple channels are displayed based on the information of the received channels. The program according to any one of claims 1 to 15.

17. The scanning device further performs a transmission step of transmitting token information, In the receiving step, information from the multiple channels based on the transmitted token information is received. L according to feature 16.

18. The program according to any one of claims 1 to 17, characterized in that the image data is transmitted by HTTP communication during the transmission process.

19. The program according to any one of claims 1 to 18, characterized in that the scanning device further performs an execution step of performing the scanning process and the transmission process.

20. The scanning device further performs a fifth receiving step of receiving a file name from the user, The program according to any one of claims 1 to 19, characterized in that the transmission process transmits the image data having the received file name.

21. The program according to any one of claims 1 to 20, characterized in that the image data is in PDF format.

22. The program according to any one of claims 1 to 21, characterized in that the channel is a chat room.

23. The program according to any one of claims 1 to 22, characterized in that the channel name of the channel is displayed in the display step.

24. The program according to any one of claims 1 to 23, characterized in that the key for receiving execution instructions is a start button.

25. A scanning device having a display unit, A display means that, after receiving authentication information, displays multiple channels of the chat service on the display unit, A first receiving means that accepts a channel selection by the user from the multiple channels displayed, It has a second receiving means for receiving the user's selection of a key for receiving the execution instruction displayed on the display unit, Both the scanning process, which involves scanning a document to generate image data, and the transmission process, which involves transmitting the generated image data, are performed based on a single key selection received by the second receiving means while the channel is selected. The image data transmitted by the transmission process, which is executed based on a single key selection, is stored in association with the selected channel. A scanning device characterized by the following features.

26. Further comprising a third receiving means for receiving instructions from a user, Upon receiving the instruction, the display means displays multiple channels of the chat service on the display unit. The scanning device according to claim 25.

27. ​​The scanning device according to claim 26, wherein the third receiving means receives the instruction after the authentication information has been received by the scanning device and authentication has been performed using the authentication information.

28. The scanning device according to claim 25, characterized in that the authentication information is stored in association with the user using the scanning device.

29. The scanning device according to claim 25, wherein the display means displays on the display unit the channel of the chat service to which the first account corresponding to the authentication information belongs.

30. The scanning device according to claim 29, characterized in that the display means does not display channels to which the first account does not belong on the display unit.

31. The scanning device according to claim 25, further comprising a second display means for displaying the key on the display unit.

32. The scanning device according to claim 31, characterized in that the second display means displays on the same screen a reset key for resetting set information, information indicating a file format specified by the user, a key for checking the job execution history by the scanning device, and a key for receiving the execution instruction.

33. The scanning device according to claim 31, characterized in that the second display means displays the key, the selected channel, and information indicating the file format specified by the user on the same screen.

34. The scanning device according to claim 31, characterized in that the second display means displays the selected channel and the scan settings on the same screen.

35. The scanning device according to claim 34, characterized in that the second display means displays the key, the selected channel, and the scan settings on the same screen.

36. The scanning device according to claim 34, characterized in that the screen on which the keys are displayed is a different screen from the screen on which the user selects a channel from the plurality of channels.

37. The scanning device according to any one of claims 25 to 36, characterized in that when the transmission process is executed, the image data and the information of the selected channel are transmitted to the server, and the image data is stored in association with the selected channel.

38. Further comprising a fourth receiving means for receiving scan settings, In the aforementioned scanning process, the document is scanned based on the scan settings, and image data is generated. The scanning apparatus according to any one of claims 25 to 37, characterized by the features described herein.

39. The scanning device according to any one of claims 25 to 38, further comprising a printing means for printing an image onto paper.

40. The receiving means for receiving information from the plurality of channels, The display means displays the plurality of channels based on the information of the received channels. The scanning apparatus according to any one of claims 25 to 39, characterized in that it is the same as described in the previous claim.

41. The invention further comprises a transmission means for transmitting token information, The receiving means receives information from the plurality of channels based on the transmitted token information. The scanning device according to feature 40.

42. The scanning device according to any one of claims 25 to 41, characterized in that the image data is transmitted by HTTP communication during the transmission process.

43. The scanning device according to any one of claims 25 to 42, further comprising execution means for performing the scanning process and the transmission process.

44. Further comprising a fifth receiving means for receiving a file name from a user, In the aforementioned transmission process, the image data having the received file name is transmitted. The scanning apparatus according to any one of claims 25 to 43, characterized by the features described herein.

45. The scanning device according to any one of claims 25 to 44, characterized in that the image data is in PDF format.

46. The scanning device according to any one of claims 25 to 45, characterized in that the channel is a chat room.

47. The scanning device according to any one of claims 25 to 46, characterized in that the display means displays the channel name of the channel.

48. The scanning device according to any one of claims 25 to 47, characterized in that the key for receiving execution instructions is a start button.

49. A method for controlling a scanning device, After the scanning device receives authentication information, a display step is performed in which multiple channels of the chat service are displayed on the display unit of the scanning device. A first reception step that accepts the user's selection of a channel from the multiple channels displayed, The system includes a second receiving step which accepts the user's selection of a key for receiving the execution instruction displayed on the display unit, Both the scanning process, which involves scanning a document to generate image data, and the transmission process, which involves transmitting the generated image data, are performed by the scanning device based on a single key selection received in the second reception step while the channel is selected. The image data transmitted by the transmission process, which is executed based on a single key selection, is stored in association with the selected channel. A control method characterized by the following:

Images