Program, scanning device and scanning method

Abstract

To allow a talk room of a chat service for sharing image data which an image processing device has generated by scanning to be designated.SOLUTION: An image processing device of the present invention is an image processing device that communicates with a chat server that performs control, based on received information indicating a talk room of the chat server, to display information indicating received image data in the talk room. The image processing device includes: reading means for reading an image of a document and generating image data based on the image; designation means for designating the talk room of the chat server; and transmission means for transmitting the image data generated by the reading means and information indicating the talk room designated by the designation means to the chat server.SELECTED DRAWING: Figure 6

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 Publication No. 2019-62353 Summary of the Invention [Problem to be solved by the invention]

[0004] When a user uses a chat service available on the Internet to share scanned image data in a chat room of the chat service, the following problems arise: For example, in an image processing device that transmits generated image data to a file server via SMB communication or the like, as in Patent Document 1, it is not possible to specify a chat room for the chat service, and the user cannot share the image data in the desired chat room.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to specify a talk room of a chat service for sharing image data generated by scanning with an image processing device. [Means for solving the problem]

[0006] The image processing device of the present invention is an image processing device that communicates with a chat server and controls the display of information indicating received image data in the talk room based on information indicating the received chat server's talk room, and is characterized in that it has a reading means that reads an image of a document and generates image data based on the image, a designation means that designates the talk room of the chat server, and a transmission means that transmits the image data generated by the reading means and information indicating the talk room designated by the designation means to the chat server. [Effects of the Invention]

[0007] A chat room of a chat service for sharing image data generated by scanning with an image processing device can be specified. [Brief explanation of the drawings]

[0008] [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 sequence in which the MFP 101 transmits a file generated by scanning to the message application server 300. [Figure 7] A flowchart showing an example of scan-to-chat processing executed by the MFP 101. [Figure 8] 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 9] Flowchart showing an example of scan-to-chat processing [Figure 10]10 is a flowchart showing an example of a process when the bot server 400 transmits image data to the message application server 300. [Figure 11] A diagram showing an example of the file structure in the Message App server [Figure 12] A diagram showing an example of a message screen in a messaging app [Figure 13] FIG. 10 is a diagram showing an example of a setting registration screen. [Figure 14] FIG. 10 shows an example of a home screen displayed on an operation unit 116 of the MFP 101. [Figure 15] An example of the screen transition for scan-to-chat processing [Figure 16] FIG. 10 is a diagram showing an example of association between ID and token information. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0024] The mobile terminal 200 can exchange data with various peripheral devices via an NFC communication unit 205, a Bluetooth (registered trademark) communication unit 206, and a wireless LAN communication unit 211. The Bluetooth communication unit 206 of the mobile terminal 200 may be compatible with Bluetooth (registered trademark) Low Energy.

[0025] 4 is a diagram showing an example of the hardware configuration of the message application server 300. The CPU 301 reads out a control program stored in the ROM 302 and executes various processes for controlling the operation of the message application server 300. The ROM 302 stores the control program. The RAM 303 is used as a temporary storage area such as the main memory and work area of ​​the CPU 301. The HDD 305 stores various data such as messages, image data, and channel information. Data can be transmitted and received to and from various devices such as the mobile terminal 200 and MFP 101 via the communication unit 304. The communication unit 304 may perform wired communication using Ethernet (registered trademark) or wireless communication such as Wi-Fi.

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

[0027] 14 is a diagram showing an example of a home screen displayed on operation unit 116 of MFP 101. Operation unit 116 is made up of touch panel 601 that displays the operation screen, and LEDs 610 and 611. Touch panel 601 is an instruction means, and functions 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 601 with an object such as a finger or a stylus to instruct the execution of each function based on the displayed screen.

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

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

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

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

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

[0033] Fig. 6 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. 6 is started in response to selection of the channel selection button 713 on the setting screen 704 in Fig. 15 .

[0034] In S901, 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 inputted thereto and information indicating a request for a channel list in the workspace indicated by the token information. An example of the command transmitted here 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 to this URL, the message app server 300 searches for a workspace and a bot app corresponding to the token information. The token information is inputted by the user via the setting registration screen 1501 of FIG. 13 displayed on the operation unit 116 of the MFP 101.

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

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

[0037] In S902, 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 a bot application corresponding to the token information.

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

[0039] In step S904, 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.

[0040] In S905, CPU 111 of MFP 101 generates channel selection screen 714 based on the channel information included in the received channel list information. Then, when the user selects channel selection button 713, CPU 111 of MFP 101 displays channel selection screen 714 on touch panel 601 of operation unit 116 and waits for a user operation. Channel selection screen 715 will be described later in the description of FIG. 15.

[0041] In S906, the CPU 111 of the MFP 101 confirms the information of the channel to which the user is to post by selecting at least a channel on the channel selection screen 714 and selecting the back button 715.

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

[0043] In step S908, the CPU 111 of the MFP 101 performs scanning using the scan settings set when the scan execution instruction is received.

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

[0045] In S910, the CPU 111 of the MFP 101 transmits the same token information as in S901, information about the destination channel selected in S906, the file format, and the image data generated in S909 to the message app server 300 by HTTP communication via the communication unit 126. Note that the file format used is the file format specified by the user on the scan-to-chat transmission setting screen 712.

[0046] In S911, the CPU 301 of the message app server 300 searches for the workspace information and app information registered in the token information received in S910, and stores the received image data in association with the channel specified in the channel information. Furthermore, 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 launches 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.

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

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

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

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

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

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

[0053] When the destination confirmation button 705 is selected, a scan-to-chat destination confirmation screen 706 is displayed. The scan-to-chat destination confirmation screen 706 displays the transmission setting posting destinations that were set when the channel selection button 713 was selected. The posting destination button 707 displays the number of posting destinations that are set at that time, and when selected by the user, the destination confirmation screen 706 is displayed, displaying the set posting destinations (destinations). Furthermore, when the posting destination button 707 is selected, a details screen (not shown) is displayed, displaying details of the set posting destinations.

[0054] In this embodiment, only one posting destination is displayed on the scan-to-chat destination confirmation screen 706, but this is not limiting. For example, if the MFP 101 sets multiple posting destinations from the message application server 300, multiple posting destination buttons can be displayed on the scan-to-chat destination confirmation screen 706.

[0055] When reset 708 is selected on scan-to-chat screen 704, the set information is cleared. At this time, the set destination information is cleared. When black and white start button 709 and color start button 710 are selected on scan-to-chat screen 704, the scan and send process is started.

[0056] When the transmission settings button 711 is selected, a transmission settings screen 712 is displayed. On this screen, transmission settings such as transmission file settings 717 can be changed and confirmed.

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

[0058] When the back button 715 is selected, the channel selection is maintained and the scan-to-chat screen 704 is displayed again. At this time, the destination field 716 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.

[0059] Now, returning to the explanation of the flow in Fig. 7, in S1002, the CPU 111 displays the scan to chat screen 704 in Fig. 15 on the operation unit 116. In S1003, the CPU 111 detects that the channel selection button 713 has been selected.

[0060] In S1004, in response to the selection of the channel selection button, the CPU 111 executes a process of transmitting information indicating a request for channel information via HTTP communication to the message application server 300 using the token information 1503 registered in advance.

[0061] Here, the setting registration screen in Fig. 13 will be described. Fig. 13 is a diagram showing an example of the setting registration screen. The setting registration screen 1501 is a screen displayed on the operation unit 116 of the MFP 101. Note that the setting registration screen 1501 may also be displayed as a web page on the operation unit of an information processing device such as a PC connected to the MFP 101 via a network. The content registered on the setting registration screen 1501 is recorded in the storage 114 in the first embodiment, and in the HDD 405 in the second embodiment.

[0062] Connection destination 1502 is a column showing organizational information of the connection destination. Token information 1503 is a column of registered token information. Operation buttons 1504 is a column of operation buttons. In this item, an edit button 1505 and a generate button 1506 are displayed.

[0063] When the edit button 1505 is selected, character strings such as token information and connection destination information can be input and changed using a keyboard, etc. When the generate button 1506 is selected, the scan-to-chat button 602 is set to be displayed on the home screen 608. The contents registered on the setting registration screen 1501 are stored in the storage 114 in the first embodiment.

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

[0065] Now, returning to the explanation of the flow in Fig. 7, in S1005, 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 S1004. 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 information has been received, the process proceeds to S1008. If not, the process proceeds to S1006.

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

[0067] In S1007, the CPU 111 determines whether or not the back button 715 has been selected. If it is determined that the back button 715 has been selected, the process returns to S1002. If not, the process returns to S1006.

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

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

[0070] 15 on the operation unit 116, and updates the display of the posting destination field 716 with the posting destination confirmed in S1009. At this time, information about the user to be notified is also displayed along with the posting destination channel.

[0071] In S1011, the CPU 111 determines whether the monochrome start key 709 or the color start key 710 displayed on the operation unit 116 has been selected. If it is determined that the key has been selected, the process proceeds to S1012. If not, the process returns to S1011.

[0072] In step S1012, 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).

[0073] In S1013, the CPU 111 converts the image data generated in S1012 into the file format 717 set on the transmission setting screen.

[0074] In S1014, the 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 717 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.

[0075] In S1015, the CPU 111 uses the pre-registered token information 1503 to send the file generated in S1013 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.

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

[0077] In this embodiment, only one piece of token information is registered, but if multiple pieces of token information are registered, processes related to the token information, such as S1004, S1005, and S1015, are executed for each registered token.

[0078] 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 S1015 will be described with reference to FIG.

[0079] Fig. 12 is a diagram showing an example of a message screen of a message app. A message screen 1201 in Fig. 12 is displayed when the message app is launched on the mobile terminal 200 and the processing of S1015 is executed on the MFP 101. The mobile terminal 200 is in communication with the message app server 300.

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

[0081] Message 1204 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. The example in FIG. 12 shows an example in which "Channel 1" is specified as the posting channel in the posting parameters, and "User 3" belonging to Channel 1 is specified as the user. Also, "document.pdf" is specified as the file name in the posting parameters, 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).

[0082] The message app screen 1201 also displays the channels, groups, and users in which the logged-in user is participating. It also displays the other party's information (1202) and the message exchange (1203). When posting, the other party can indicate that they want to notify a specific user in the channel by adding a comment with "@" at the beginning of the user's name (1204). In the case of FIG. 12, 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. To display this screen, the message app server 300 searches for and displays the necessary information from the data structure shown in FIG. 11. For example, the posting of message 1204 corresponds to "Comment 3 + File 1" in exchange content 505, and attribute information such as the name of File 1 is obtained from 504 and displayed in the form of a file icon on the message. When the user selects this file icon, File 1 belonging to File 504 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.

[0083] FIG. 11 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. 12 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 known as a workspace. Channel 501 is a chat room that all members of the workspace can participate in, and all posted content can be searched by anyone. Group 502 is a channel for discussions that should not be open to all members, and requires an invitation to view and participate. User 503 is a user participating in this workspace. File 504 stores attached files. Furthermore, content 505 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 each other, 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 714. Users participating in that channel can be displayed. [Example]

[0084] In the first embodiment, an example has been 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.

[0085] FIG. 8 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. In FIG.

[0086] In step S1101, the CPU 111 of the MFP 101 requests the bot server 400 for channel list information via HTTP communication, using the device ID or user ID as a parameter.

[0087] In S1102, the CPU 401 of the bot server 400 uses the token information corresponding to the received device ID or user ID to send information indicating a request for channel list information via HTTP communication to the message application server 300. This token information is obtained corresponding to the device ID or user ID received in S1101.

[0088] FIG. 16 is a diagram showing an example of the correspondence between IDs and token information. In the table of FIG. 16, user IDs or device IDs are registered in association with authentication information (token information). This table is stored in HDD 405 of bot server 400. Here, the user ID and device ID are information stored in MFP 101, and the user ID is user identification information set for each user who uses MFP 101. The device ID is device identification information set for each MFP. The user ID is identification information set by the user when creating a user account for logging in to MFP 101, and the device ID is identification information unique to MFP 101 set at the time of shipment from the factory.

[0089] In S1103, the CPU 301 of the message app server 300 searches for registered workspace information and bot app from the token information.

[0090] In S1104, the CPU 301 of the message app server 300 checks whether the executed URL is permitted based on the app 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 the channel ID, the channel name, a list of member IDs belonging to the channel, and setting values ​​such as whether the channel is an archived channel.

[0091] In S1105, 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.

[0092] In S1106, the CPU 401 of the bot server 400 transmits the channel list information received in S1105 to the MFP 101 as a response to the HTTP communication.

[0093] The processing in steps S1107 to S1111 is similar to the processing in steps S905 to S909 in FIG. 6, and therefore a description thereof will be omitted.

[0094] In S1112, the CPU 111 of the MFP 101 transmits the device ID or user ID, information on the destination channel, information indicating the file format, etc., and image data to the bot server 400 via HTTP communication.

[0095] In S1113, the CPU 401 of the bot server 400 executes a process of transmitting the received destination channel information, information indicating the file format, image data, and token information corresponding to the received device ID or user ID to the message app server 300. Here, the CPU 401 determines the token information to be transmitted by referring to a table stored in the HDD 405 in which device IDs or user IDs are associated with token information.

[0096] The processing in S1114 is the same as the processing in S911, and therefore the explanation will be omitted.

[0097] In S1115, 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.

[0098] In S1116, 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 operation unit 116. If the posting is unsuccessful, CPU 111 of MFP 101 may display a notification indicating that the posting was unsuccessful on operation unit 116. Alternatively, if the posting is successful, no notification may be displayed, and only if the posting is unsuccessful, a notification indicating that the posting was unsuccessful may be displayed.

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

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

[0101] The processing in steps S1301 to S1303 is the same as the processing in steps S1001 to S1003, and therefore the description thereof will be omitted.

[0102] In S1304, the CPU 111 acquires the user ID of the user who is logged in to the MFP 101 or the device ID of the MFP 101, and transmits a channel information acquisition request and the user ID or device ID to the bot server 400 by HTTP communication.

[0103] The processing in steps S1305 to S1314 is the same as the processing in steps S1005 to S1014, and therefore the description thereof will be omitted.

[0104] In S1315, the CPU 111 transmits the user ID of the user logged in to the MFP 101 or the device ID of the MFP 101, the file generated in S1313, 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 1503 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 the user ID or device ID in Fig. 16 in association with the token information, and transmit a request or a file using the token information corresponding to the user ID or device ID of the logged-in user.

[0105] In this embodiment, the logged-in user ID and device ID are used for communication with the bot server 400, but a tenant ID or other unique identifier can also be used.

[0106] Fig. 10 is a flowchart showing an example of processing when the bot server 400 transmits image data to the message application server 300. The CPU 401 reads a program stored in the ROM 112 into the RAM 113 and executes it, thereby executing the processing of the flowchart in Fig. 10. The flow in Fig. 10 is started when the MFP 101 is powered on.

[0107] In S1401, the CPU 401 determines whether or not an information acquisition request for acquiring a device ID or a user ID and channel information has been received from the MFP 101. If it is determined that the request has been received, the process proceeds to S1402. If not, the process returns to S1401.

[0108] In step S1402 , the CPU 401 acquires token information corresponding to the device ID or user ID received from the MFP 101 .

[0109] In S1403, the CPU 401 determines whether or not there is token information corresponding to the received device ID or user ID, using the table in Fig. 16. If it is determined that there is, the process proceeds to S1404. If not, the process proceeds to S1405. If it is determined that there is, the RAM 403 stores the token information corresponding to the received device ID or user ID.

[0110] In S1404, the CPU 401 uses the token information identified in S1403 to transmit the information acquisition request received from the MFP 101 in S1401 to the message application server 300. The information returned from the message application server 300 in response to the transmission is transmitted to the MFP 101.

[0111] In step S1405, the CPU 401 transmits information indicating an execution error to the MFP 101 as a response to the request received in step S1401.

[0112] 10 illustrates an example of when the user ID or device ID and information acquisition request transmitted in S1101 of the sequence in Fig. 8 are received. The same process as in Fig. 10 is performed when the user ID or device ID, file (image data), and destination channel information transmitted in the process of S1112 are received. That is, if there is token information corresponding to the received device ID or user ID, the token information, destination channel information, and file (image data) are transmitted to the message app server 300. If there is no token information corresponding to the received device ID or user ID, information indicating an error is transmitted to the MFP 101.

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

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

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

Claims

1. a display step of displaying a plurality of channels of the chat service; a first receiving step of receiving a channel selection by a user from the displayed plurality of channels; a second receiving step of receiving an execution instruction from a user; a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are both executed by the scanning device based on a single execution instruction received in the second receiving step while the channel is selected; The program is characterized in that the image data transmitted by the transmission process being executed based on the one execution instruction is stored in association with the selected channel.

2. causing the scanning device to further execute a second display step of displaying a key for receiving the execution instruction on an operation unit of the scanning device; 2. The program according to claim 1, wherein both the scanning process and the transmission process are executed based on a single selection of the displayed key.

3. The program according to claim 2, characterized in that in the second display step, a reset key for resetting the set information, a file format specified by the user, and an object for checking the job execution history by the scanning device are displayed, while a key for accepting the execution instruction is displayed.

4. a display step of displaying a plurality of channels of the chat service; a first receiving step of receiving a channel selection by a user from the displayed plurality of channels; a second receiving step of receiving an execution instruction from a user; a scanning process of scanning an original to generate image data and a transmission process of transmitting the generated image data are executed by the scanning device in response to a single execution instruction received in the second receiving step with the channel selected; The image data transmitted in the transmission process is stored in association with the selected channel.

5. causing the scanning device to further execute a second display step of displaying a key for receiving the execution instruction on an operation unit of the scanning device; 5. The program according to claim 4, wherein the scanning process through the transmission process are executed by the scanning device by a single selection of the displayed key.

6. The program according to claim 5, characterized in that in the second display step, a key for accepting the execution instruction is displayed while a reset key for resetting the set information, a file format specified by the user, and an object for checking the job execution history by the scanning device are displayed.

7. A program according to any one of claims 1 to 6, characterized in that, when the transmission process is executed, the image data and information on the selected channel are transmitted to a server, and the image data is stored in correspondence with the selected channel.

8. causing the scanning device to further execute a third receiving step of receiving scan settings; 8. The program according to claim 1, wherein the document is scanned based on the scan settings in the scan process, and image data is generated.

9. 9. The program according to claim 1, further causing the scanning device to execute a printing step of printing an image on a sheet of paper.

10. causing the scanning device to further perform a receiving step of receiving information on the plurality of channels; 10. The program according to claim 1, wherein in the display step, the plurality of channels are displayed based on the received channel information.

11. causing the scanning device to further perform a transmitting step of transmitting token information; 11. The program according to claim 10, wherein said receiving step receives information on said plurality of channels based on said transmitted token information.

12. 12. The program according to claim 1, wherein in the transmission process, the image data is transmitted by HTTP communication.

13. 13. The program according to claim 1, further causing the scanning device to execute an execution step of executing the scanning process and the transmission process.

14. causing the scanning device to further execute a fourth receiving step of receiving a file name from a user; 14. The program according to claim 1, wherein the image data having the accepted file name is transmitted in the transmission process.

15. a display means for displaying a plurality of channels of the chat service; a first receiving means for receiving a channel selection by a user from the displayed plurality of channels; a second receiving means for receiving an execution instruction from a user; executes both a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data based on a single execution instruction received by the second receiving means while the channel is selected; The scanning device is characterized in that the image data transmitted by the transmission process being executed based on the one execution instruction is stored in association with the selected channel.

16. a second display unit for displaying a key for receiving the execution instruction on the operation unit of the scanning device; 16. The scanning device of claim 15, wherein both the scanning process and the sending process are performed based on a single selection of the displayed key.

17. 17. The scanning device according to claim 16, wherein the second display means displays a key for accepting the execution instruction while displaying a reset key for resetting set information, a file format specified by the user, and an object for checking the job execution history by the scanning device.

18. a display means for displaying a plurality of channels of the chat service; a first receiving means for receiving a channel selection by a user from the displayed plurality of channels; a second receiving means for receiving an execution instruction from a user; executes a process from a scan process of scanning an original to generate image data to a transmission process of transmitting the generated image data in response to a single execution instruction received by the second receiving means while the channel is selected; The scanning device according to claim 1, wherein the image data transmitted in the transmission process is stored in association with the selected channel.

19. a second display unit for displaying a key for receiving the execution instruction on the operation unit of the scanning device; 19. The scanning device according to claim 18, wherein the scanning process through the transmission process are executed by a single selection of the displayed key.

20. 20. The scanning device according to claim 19, wherein the second display means displays a key for accepting the execution instruction while displaying a reset key for resetting set information, a file format specified by the user, and an object for checking the job execution history by the scanning device.

21. A scanning device as described in any one of claims 15 to 20, characterized in that when the transmission process is executed, the image data and information on the selected channel are transmitted to a server, and the image data is stored in correspondence with the selected channel.

22. The apparatus further includes a third receiving unit for receiving scan settings, 22. The scanning device according to claim 15, wherein the document is scanned based on the scan settings in the scanning process, and image data is generated.

23. 23. The scanning device according to claim 15, further comprising a printing means for printing an image on a sheet of paper.

24. further comprising receiving means for receiving information on the plurality of channels; 24. The scanning device according to claim 15, wherein the display means displays the plurality of channels based on the received channel information.

25. further comprising a transmitting means for transmitting token information; 25. The scanning device according to claim 24, wherein said receiving means receives information on said plurality of channels based on said transmitted token information.

26. 26. The scanning device according to claim 15, wherein in the transmission process, the image data is transmitted by HTTP communication.

27. 27. The scanning device according to claim 15, further comprising an execution unit for executing the scanning process and the transmission process.

28. a fourth receiving means for receiving a file name from a user; 28. The scanning device according to claim 15, wherein the image data having the accepted file name is transmitted in the transmission process.

29. a display step of displaying a plurality of channels of the chat service; a first receiving step of receiving a channel selection by a user from the displayed plurality of channels; a second receiving step of receiving an execution instruction from a user; a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are both executed by a scanning device based on a single execution instruction received in the second receiving step while the channel is selected; The scanning method according to claim 1, wherein the image data transmitted by the transmission process being executed based on the single execution instruction is stored in association with the selected channel.

30. a second display step of displaying a key for receiving the execution instruction on an operation unit of the scanning device; 30. The method of claim 29, wherein both the scanning process and the sending process are performed based on a single selection of the displayed key.

31. The scanning method according to claim 30, characterized in that in the second display step, a key for accepting the execution instruction is displayed while a reset key for resetting the set information, a file format specified by the user, and an object for checking the job execution history by the scanning device are displayed.

32. a display step of displaying a plurality of channels of the chat service; a first receiving step of receiving a channel selection by a user from the displayed plurality of channels; a second receiving step of receiving an execution instruction from a user; a scanning process for scanning an original to generate image data and a transmission process for transmitting the generated image data are executed by the scanning device in response to a single execution instruction received in the second receiving step while the channel is selected; The scanning method according to claim 1, wherein the image data transmitted in the transmission process is stored in association with the selected channel.

33. a second display step of displaying a key for receiving the execution instruction on an operation unit of the scanning device; 33. The scanning method according to claim 32, wherein the steps from the scanning process to the sending process are performed by the scanning device by a single selection of the displayed key.

34. The scanning method according to claim 33, wherein in the second display step, a key for accepting the execution instruction is displayed while a reset key for resetting the set information, a file format specified by the user, and an object for checking the job execution history by the scanning device are displayed.

35. A scanning method according to any one of claims 29 to 34, characterized in that, when the transmission process is executed, the image data and information on the selected channel are transmitted to a server, and the image data is stored in correspondence with the selected channel.

36. a third receiving step of receiving a scan setting; 36. The scanning method according to claim 29, wherein the document is scanned based on the scan settings in the scanning process, and image data is generated.

37. 37. A scanning method according to any one of claims 29 to 36, further comprising the step of printing the image onto paper.

38. further comprising a receiving step of receiving information on the plurality of channels; 38. The scanning method according to claim 29, wherein in the display step, the plurality of channels are displayed based on the received channel information.

39. a transmitting step of transmitting the token information; 39. The scanning method according to claim 38, wherein said receiving step receives information on said plurality of channels based on said transmitted token information.

40. 40. The scanning method according to claim 29, wherein in the transmission process, the image data is transmitted by HTTP communication.

41. 41. The scanning method according to claim 29, further comprising an execution step of executing the scanning process and the transmission process.

42. a fourth receiving step of receiving a file name from a user; 42. The scanning method according to claim 29, wherein the image data having the accepted file name is transmitted in the transmission process.

Images