Image processing apparatus, control method thereof, and program
The image processing device addresses the challenge of accurately posting scanned data to the intended chat room by incorporating selection and confirmation mechanisms, ensuring precise and user-controlled image data transmission.
Patent Information
- Application Number
- JP2023085180
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-24
- Publication Date
- 2024-12-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing image processing devices face challenges in accurately selecting and posting scanned image data to the desired chat room, especially when chat room names are ambiguous or similar, leading to unintended postings.
The image processing device includes a first reception means for selecting a chat room, a second reception means for scanning instructions, and a display control means for confirming the selected chat room before transmitting image data, allowing cancellation of the transmission if necessary.
Ensures that scanned image data is appropriately posted to the user's desired chat room, reducing the likelihood of unintended postings and enhancing user control over the posting process.
Smart Images

Figure 2024168469000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an image processing apparatus, a control method thereof, and a program. [Background technology]
[0002] Patent Document 1 discloses that an image processing device transmits image data obtained by scanning an original to a chat server that provides a chat service. A user can select a chat room to which the image data is to be posted. The image data obtained by scanning is transmitted to the chat server and posted to the chat room selected by the user. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2021-78084 Summary of the Invention [Problem to be solved by the invention]
[0004] In Patent Document 1, a user selects a chat room to which he or she wants to post image data while looking at the chat room names. However, for example, when the chat room name makes it difficult to guess the chat contents or when there are similar chat room names, there is a possibility that the user may specify an unintended chat room and post the image data as it is.
[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to enable image data obtained by an image processing device scanning a document to be appropriately posted to a user's desired chat room. [Means for solving the problem]
[0006] The image processing device of the present invention is an image processing device having a function of transmitting image data obtained by scanning a document to a chat server that provides a chat service, and has a first reception means for receiving a selection of a chat room of the chat service as a posting destination to which the image data obtained by scanning the document will be posted, a second reception means for receiving an instruction to scan the document, and a display control means for displaying information within the chat room selected by the first reception means after receiving the instruction, and is capable of canceling the transmission of the image data to the chat server after displaying the information within the chat room. Effect of the Invention
[0007] Image data obtained by scanning an original with an image processing device can be appropriately posted to a user's desired chat room. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration of the present invention. [Diagram 2] A diagram showing an example of the hardware configuration of the MFP101. [Diagram 3] FIG. 2 is a diagram showing an example of a hardware configuration of a mobile terminal 200. [Figure 4] FIG. 2 is a diagram showing an example of a hardware configuration of a message application server 300. [Diagram 5] FIG. 4 shows an example of the hardware configuration of the bot server 400. [Figure 6] FIG. 1 shows an example of a home screen displayed on an operation unit 116 of the MFP 101. [Figure 7] FIG. 13 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. [Figure 8] A flowchart showing an example of scan-to-chat processing executed by the MFP101. [Figure 9] A diagram showing an example of the file structure in a message app server [Figure 10]A diagram showing an example of a message screen of a message app [Figure 11] A diagram showing an example of the screen transition for scan-to-chat processing [Figure 12] FIG. 13 is a diagram showing an example of a setting registration screen. [Figure 13] FIG. 13 is a diagram showing an example of a preview screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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.
[0010] FIG. 1 is a diagram showing 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) by 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 transfers a request from the MFP 101 to the message app server 300. The network 100 of this embodiment may be the Internet or a LAN (Local Area Network). The network 100 may be wired or wireless.
[0011] 2 is a diagram showing an example of the hardware configuration of the MFP 101. The MFP 101 includes a CPU 111, a ROM 112, a RAM 113, a storage 114, an operation unit I / F 115, an operation unit 116, a reading unit I / F 117, a reading unit 118, a printing unit I / F 119, a printing unit 120, a wireless communication unit I / F 121, and a wireless communication unit 122. The MFP 101 also includes a FAX unit I / F 123, a FAX communication unit 124, a communication unit I / F 125, and a communication unit 126.
[0012] The control unit 110 including the CPU 111 controls the operation of the entire MFP 101. The CPU 111 reads out a control program stored in the ROM 112 or the storage 114 to the RAM 113, and performs various controls such as reading control and printing control. The ROM 112 stores a control program 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 developing 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 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 later using one memory (RAM 113), but this is not limited to this. For example, each process shown in the flowcharts described later can be executed by using multiple CPUs, RAMs, ROMs, and storages in cooperation. Also, some of the processes can be executed using hardware circuits such as ASICs and FPGAs.
[0014] An operation unit I / F 115 connects an operation unit 116 including a display unit such as a touch panel and hard keys to the control unit 110. The operation unit 116 displays 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 an original document, and the CPU 111 converts the image into image data such as binary data. Image data generated based on the image read by the reading unit 118 is sent to an external device or printed on recording paper. The reading unit also has an ADF, and can transport an original document placed on an original document tray provided in the MFP 101, read the image of the transported original document, and generate image data.
[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 to the control unit 110 via wireless communication with an external wireless device (here, the mobile terminal 200).
[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 an 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 and the network 100. The communication unit I / F 125 allows the communication unit 126 to transmit image data and various information inside the device to an external device on the network 100, and receives print data and information on the network 100 from an information processing device on the network 100. As a method of transmission and reception via the network 100, transmission and reception using e-mail and file transmission using other protocols (for example, FTP, SMB, WEBDAV, etc.) can be performed. Furthermore, image data and various setting data can be transmitted and received over the network 100 by accessing from the mobile terminal 200, the message application server 300, and the bot server 400 via HTTP communication.
[0020] 3 is a diagram showing an example of a hardware configuration of the mobile terminal 200. Note that the mobile terminal 200 of the present embodiment is assumed to be a device such as a smartphone or a tablet PC, but 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 a main memory and a work area for 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 an e-mail sending application. The operation panel 201 is also used to check information stored in the message application server 300. The user can input a desired operation instruction to the mobile terminal 200 by inputting a touch operation to the operation panel 201. The mobile terminal 200 has a hardware key (not shown), and the user can input an operation instruction to the mobile terminal 200 using this hardware key.
[0023] The camera 204 captures an image in response to an image capture instruction from the user. The photograph captured by the camera 204 is stored in a predetermined area of the HDD 210. It is also possible to obtain information from a QR code read by the camera 204 using a program capable of analyzing QR codes (registered trademark).
[0024] The mobile terminal 200 can transmit and receive data to and from various peripheral devices via an NFC communication unit 205, a Bluetooth (registered trademark) communication unit 206, and a wireless LAN communication unit 211. The Bluetooth communication unit 206 of the mobile terminal 200 may be compatible with Bluetooth (registered trademark) Low Energy.
[0025] 4 is a diagram showing an example of a 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 the 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] 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 app server. The ROM 402 stores the control program. The RAM 403 is used as a temporary storage area such as the main memory and work area of the CPU 401. The HDD 405 stores various data such as messages, image data, and channel information. Data can be transmitted and received via the communication unit 404 to and from various models such as the mobile terminal 200, the MFP 101, and the message app server 300.
[0027] 6 is a diagram showing an example of a home screen displayed on operation unit 116 of MFP 101. Operation unit 116 is made up of touch panel 601 that displays an operation screen, and LEDs 610 and 611. Touch panel 601 is an instruction means, and functions as a receiving means that receives instructions from a user, and also functions as a display means that displays a screen. A user directly touches the screen displayed on touch panel 601 with a finger, a stylus, or other object, and instructs the execution of each function based on the displayed screen.
[0028] 6 displays a home screen 608. The home screen 608 is the first screen for instructing the execution of each function of the MFP 101, and is a screen for selecting a screen display for making various settings for each function executed by the MFP 101, such as copy, fax, scan, and media print.
[0029] A status check button 605 is an object for displaying a screen (status check screen) for checking the status of the MFP 101. It is possible to display a transmission history or a job execution history from the status check screen (not shown).
[0030] The scan-to-chat button 602 is an object for displaying a setting screen for the scan-to-chat process. When the scan-to-chat button 602 is selected by the user, a scan-to-chat screen 1101 in Fig. 11 is displayed on the operation unit 116. The scan-to-chat process will be described in detail with reference to Figs.
[0031] A 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 electronic mail transmission (E-mail), file transmission via SMB, FTP, or HTTP, and Internet fax (I-fax) transmission. Touching an object indicating a displayed transmission function displays a setting screen for each transmission function.
[0032] An address book button 604 is an object for displaying an address book screen of the MFP 101 when selected by the user. LEDs 610 and 611 notify the user of the status of the MFP 101. The LED 610 lights up when 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 constantly 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 constantly 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. 7 is a diagram showing an example of a sequence in which the MFP 101 transmits a file generated by scanning to the message app server 300. Although Fig. 7 shows a case in which the MFP 101 and the message app server communicate directly with each other, this is not limiting. For example, communication may be performed via a cloud server (not shown), and the cloud server may generate a preview screen displayed in S710 and transmit it to the MFP 101. The sequence in Fig. 7 is started in response to selection of a destination setting button 1114 on the scan-to-chat screen 1101 in Fig. 11.
[0034] In S701, the CPU 111 of the MFP 101 controls the communication unit 126 to request channel list information and thread list information from the message app server 300 by HTTP communication. Specifically, the MFP 101 transmits to the message app server 300 token information inputted by the MFP 101 and information indicating a request for a channel list in the workspace indicated by the token information. Here, the MFP 101 transmits user ID information inputted by the MFP 101 to the message app server 300 to identify information related to the user ID in the workspace. Furthermore, in the case where only the individual user is allowed to read and write user information in the workspace, this authority is acquired by transmitting password information corresponding to the user ID information inputted by the MFP 101 to the message app server 300.
[0035] Here, an example of the command to be sent is "HTTP GET https: / / message.com / api / channels.list". The URL "https: / / message.com / api / channels.list" described in this command is a URL for accessing the message app server 300. By sending token information to this URL, the message app server 300 searches for a workspace corresponding to the token information and a channel associated with the user. Similarly, by sending token information and a user ID to the URL "https: / / message.com / api / thread.list", the message app server 300 searches for a workspace corresponding to the token information and a thread associated with the user. The token information is input by the user via the setting registration screen 1201 of FIG. 12 displayed on the operation unit 116 of the MFP 101.
[0036] Here, a workspace is like an organization to which multiple users belong in a messaging app, and may also be called a team. A channel is synonymous with a chat room in a workspace. A chat room here is a mechanism for multiple users participating in a chat room to send and receive messages to each other and exchange messages like a conversation. 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 for multiple users to send and receive messages and exchange messages like a conversation. For example, it may be something like a group chat, a room, a talk room, or a group.
[0037] Here, the bot application is an application for registering the MFP 101 as a user in the message application and posting messages and image data, and is installed in the message application server 300. By specifying the bot application and transmitting image data to the message application server 300, the bot application posts the transmitted image data in the message application. In addition, the HDD 305 of the message application server 300 stores the bot application and a token in association with each other, and also associates the bot application with a workspace. Therefore, by receiving token information from the MFP 101, the message application server 300 can return information on the workspace associated with the bot application associated with the token information. Note that the token information, the bot application, and the workspace may be directly associated with each other. This allows a workspace (a workspace to which the user wants to send image data) corresponding to the token information registered in advance to be selected from among a large number of workspaces.
[0038] In S702, the CPU 301 of the message application server 300 checks whether access to the URL is permitted based on the token information and user ID received from the MFP 101 via the communication unit 304. If permitted, channel list information included in the workspace corresponding to the token information is generated. The channel list information is array information indicating channel information. The channel information includes the channel ID, the name of the channel, information indicating users participating in the channel, and a channel setting value indicating settings such as whether the channel is an archive channel.
[0039] In S703, the CPU 301 of the message application server 300 checks whether access to the URL is permitted based on the token information and user ID received from the MFP 101 via the communication unit 304. If access is permitted, thread list information included in the workspace corresponding to the token information is generated. The thread list information is array information indicating thread information. The thread information includes a thread ID, the posted content of the thread, information indicating the posting user ID of the thread, and thread setting values indicating information such as the thread update time.
[0040] In S704, the CPU 301 of the message application server 300 controls the communication unit 304 to transmit the channel list information and thread list information generated in S702 and S703 to the MFP 101 as response information of the HTTP communication.
[0041] In S705, CPU 111 of MFP 101 generates channel selection screen 1115 based on the channel information included in the received channel list information. Then, when destination setting button 1114 is selected by the user, CPU 111 of MFP 101 performs display control to display channel selection screen 1115 on touch panel 601 of operation unit 116, and waits for a user operation. Channel selection screen 1115 will be described later in the description of FIG. 11.
[0042] In S706, the CPU 111 of the MFP 101 confirms the information of the channel to which the submission is to be made by selecting at least a channel on the channel selection screen 1115 and selecting the back button.
[0043] In step S707, the CPU 111 of the MFP 101 receives a scan execution instruction via the operation unit 116.
[0044] In S708, the CPU 111 of the MFP 101 scans an image of a document based on a scan execution instruction and scan settings set by the user.
[0045] In S709, the CPU 111 of the MFP 101 generates image data of the scanned image in a format set by the scan settings. Note that the scan settings are those specified by the user on a detailed setting screen for scan-to-chat (not shown). Note that the scan settings may be displayed and set together with the transmission settings on the transmission setting screen 1112 in FIG. 11.
[0046] In S710, the CPU 111 of the MFP 101 displays a preview screen 1301 together with information on the channel selected by the destination selection button, the title to be sent to the channel, the message, and the scanned image to be sent. The preview screen 1301 will be described later in the description of Fig. 13. The title, message, and scanned image to be sent to the channel will hereinafter be referred to as transmission information.
[0047] In S711, the CPU 111 of the MFP 101 transmits the same token information as in S701 and information on the posting destination channel selected in S706 to the message app server 300 by HTTP communication via the communication unit 126. The file format and the image data generated in S709 are also transmitted by HTTP communication. Note that the file format used is the file format specified by the user on the scan-to-chat transmission setting screen 1112.
[0048] In S712, the CPU 301 of the message app server 300 searches for workspace information and app information registered in the token information received in S710, and stores the received image data in association with the channel specified by the channel information. The user starts the message app on the mobile terminal 200, and a screen in which the image data is posted to the specified channel is displayed. If a destination user is specified, the received image data, the channel, and the destination user are further associated and stored. As a result, when the user starts the message app on the mobile terminal 200 and specifies a channel to check the contents of the conversation in the previous channel, the screen in which the received image data is posted is displayed. This screen is displayed on the display unit of the terminal that accessed the message app server 300.
[0049] In S713, the CPU 301 of the message application server 300 transmits a result corresponding to whether or not the posting was successful to the MFP 101 as response information of the HTTP communication. If the posting is successful, the CPU 111 of the MFP 101 may display a notification 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 that the posting was unsuccessful on the operation unit 116. Alternatively, no notification may be displayed when the posting is successful, and a notification that the posting was unsuccessful may be displayed only when the posting is unsuccessful.
[0050] Fig. 8 is a flowchart showing an example of scan-to-chat processing executed by MFP 101. CPU 111 reads a program stored in ROM 112 into RAM 113 and executes it to execute the processing of the flowchart in Fig. 8. The flow in Fig. 8 is started when MFP 101 is powered on.
[0051] In S801, the CPU 111 determines whether or not the scan-to-chat button 602 has been selected. If it is determined that the button has been selected, the process proceeds to S802. If not, the process returns to S801.
[0052] In S802, the CPU 111 displays a scan-to-chat screen 1101 on the touch panel 601 of the operation unit 116. Here, the screen transition when the scan-to-chat button 602 is selected will be described with reference to FIG.
[0053] 11 is a diagram showing an example of screen transitions in the scan-to-chat process. When the scan-to-chat button 602 displayed on the home screen 608 is selected, a scan-to-chat screen 1101 is displayed on the touch panel 601 of the operation unit 116.
[0054] A destination confirmation button 1105 is displayed on the scan to chat screen 1101. The destination confirmation button 1105 displays the number of destinations set as destinations for posting image data generated by scanning. In the example of FIG. 11, an example will be described in which one channel is selected as a posting destination. When multiple destinations are selected, the number of set posting destinations is displayed as the number of destinations.
[0055] When the confirm destination button 1105 is selected, a scan-to-chat destination confirmation screen 1106 is displayed. The send setting posting destinations set by selecting the set destination button 1114 are displayed on the scan-to-chat destination confirmation screen 1106. The number of posting destinations set at that time is displayed on the posting destination button 1107, and when selected by the user, a details screen (not shown) is displayed, and details of the set posting destinations are displayed.
[0056] In this embodiment, only one posting destination is displayed on the scan-to-chat destination confirmation screen 1106, but this is not limited to this. For example, the MFP 101 can set multiple posting destinations from the message application server 300 to display multiple posting destination buttons on the scan-to-chat destination confirmation screen 1106.
[0057] When the reset button 1108 is selected on the scan-to-chat screen 1101, the set information is cleared. At this time, the set destination information is also cleared. When the black and white start button 1109 and the color start button 1110 are selected on the scan-to-chat screen 1101, the scan and send process is started.
[0058] When the transmission setting button 1111 is selected, a transmission setting screen 1112 is displayed. On this screen, it is possible to change and confirm transmission settings such as a file format 1113. In addition, it is possible to change and confirm the settings of preview display conditions by using a preview setting 1117 that sets the conditions for displaying a preview screen 1301. The details of the preview setting 1117 will be described later.
[0059] When the destination setting button 1114 is selected, a channel selection screen 1115 is displayed. The channels and users displayed on this channel selection screen 1115 are displayed based on the channel list information that the MFP 101 has received 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 person to mention. When the channel button is selected, the users belonging to that channel are displayed in a pull-down menu. On this screen, both the channel and the user may be selected, or only the channel may be selected to post to all users belonging to that channel. Also, multiple channels may be selected, or one channel may be selected and multiple users within that channel may be selected. Also, multiple channels may be selected and different users belonging to each channel may be selected.
[0060] When the back button 1116 is selected, the channel selection is maintained, and the scan-to-chat screen 1101 is displayed again. At this time, the destination column 1102 displays the selected channel name as the destination 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 based on the channel and user set at this time in the RAM 113 or storage 114.
[0061] Now, returning to the description of the flow in Fig. 8, in S802, the CPU 111 displays the scan-to-chat screen 1101 in Fig. 11 on the operation unit 116. In S803, the CPU 111 detects that the destination setting button 1114 has been selected.
[0062] In S804, the CPU 111 executes a process of transmitting request information for channel information to the message application server 300 by HTTP communication using the token information 1203 and the user ID registered in advance in accordance with the user's selection of the channel selection button.
[0063] Here, the setting registration screen in Fig. 12 will be described. Fig. 12 is a diagram showing an example of the setting registration screen. The setting registration screen 1201 is a screen displayed on the operation unit 116 of the MFP 101. Note that the setting registration screen 1201 may also be displayed as a Web page on the operation unit of an information processing device such as a PC connected to the MFP 101 via a network. The contents registered on the setting registration screen 1201 are stored.
[0064] Destination 1202 is a column showing organization information of the destination. Token information 1203 is a column of registered token information. Operation buttons 1204 is a column of operation buttons. In this item, an edit button 1205 and a generate button 1206 are displayed.
[0065] When an edit button 1205 is selected, character strings such as token information, connection destination information, etc. can be input and changed using a keyboard, etc. When a create button 1206 is selected, a setting is made so that the scan-to-chat button 602 is displayed on the home screen 608.
[0066] By clicking the new registration button 1207, it is possible to accept a character string input by the user and to add and register the connection destination and token information.
[0067] Now, returning to the description of the flow in Fig. 8, in S805, the CPU 111 executes a process of transmitting information indicating a request for thread information by HTTP communication to the message application server 300, using the token information 1203 and user ID information registered in advance.
[0068] In S806, the CPU 111 determines whether or not channel information and thread information have been received from the message application server 300 in response to the channel acquisition request sent in S804 and the thread acquisition request sent in S805. Specifically, if the status code in the HTTP communication response is an error, or if the body information of the response includes a parameter indicating that the information cannot be acquired, it determines that the channel list information or thread list information has not been received. If it is determined that the information has been received, the process proceeds to S809. If not, the process proceeds to S807.
[0069] In S807, the CPU 111 displays information indicating that the channel list information could not be received on the channel selection screen 1115. At this time, the channel selection screen 1115 does not display any channel or user options.
[0070] In S808, the CPU 111 judges whether or not the back button 1116 has been selected. If it is judged that the back button 1116 has been selected, the process returns to S802. If not, the process returns to S808.
[0071] In S809, the CPU 111 displays, on the touch panel 601 of the operation unit 116, a channel selection screen 1115 on which the channel information and the like received from the message application server 300 are displayed.
[0072] In S810, 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 601 of the operation unit 116. If it has been confirmed, the process transitions to S811, and the posting channel list information is updated. If it has not been confirmed, the process returns to S809. The method for detecting confirmation is whether the back button 1116 has been selected. Note that, in the case of a screen configuration in which the Confirm button is displayed on the screen of the operation unit 116, a similar transition is made when the Confirm button is selected.
[0073] 11 on the operation unit 116, and updates the display of the posting destination field 1102 with the confirmed posting destination. At this time, information on the user to be notified is also displayed together with the posting destination channel.
[0074] In S812, the CPU 111 determines whether or not the black and white start button 1109 or the color start button 1110 displayed on the operation unit 116 has been selected. If it is determined that the button has been selected, the process proceeds to S813. If not, the process returns to S812.
[0075] In S813, the CPU 111 controls the reading unit 118 based on the scan settings to read the image of the document and generate image data. The scan settings are scan settings designated by the user on a detailed setting screen of the scan-to-chat function (not shown), and the scan settings received from the message app server 300 are used.
[0076] In S814, the CPU 111 converts the image data generated in S813 into the file format 1113 set on the transmission setting screen. Note that this process may be omitted.
[0077] In S815, CPU 111 generates posting parameters. The posting parameters include the channel to which the message is to be posted, the file format, the file name, and the posted comment. The file format is set to one that corresponds to the file format 1113 set in the transmission settings. For the posted comment, characters are generated with an @ sign added to the beginning of the user information to be notified. The file name is specified as the file name specified in the transmission settings.
[0078] In S816, the CPU 111 determines whether to display the preview screen 1301 in FIG. 13 by combining the channel information of the posting destination and the transmission information. This determination is made according to the value set in the preview setting 1117. The preview setting can be "display when the destination is not manually set" or "always display". "display when the destination is not manually set" is the case when the destination is determined by default when scanning is used and scanning is performed without manually setting the channel on the channel selection screen. The MFP 101 allows the posting destination to be used in the scan to chat function to be set in advance. If the posting destination is set in advance, the scan to chat screen 1101 is displayed with the previously set posting destination automatically applied. When this setting is used, there is a possibility that the posting destination will not be set or confirmed on the destination selection screen, so it is effective to check on the preview screen whether the posting destination is an appropriate channel. "Always display" always displays the preview in either case, whether the posting destination is manually selected on the destination selection screen or sent to the default destination without being manually selected.
[0079] In S817, the CPU 111 displays a preview screen 1301 together with the destination channel information and the transmission information. The preview screen 1301 in FIG. 13 is a diagram showing an example of a preview screen displayed before transmission to the message app server 300. The preview screen 1301 is a screen displayed on the operation unit 116 of the MFP 101. It is composed of a destination channel name display 1302, a thread display area 1303 in the channel, and a new post display area 1304. The thread display area 1303 in the channel displays the latest thread of the channel. The new post display area 1304 displays the content of the scanned document newly posted under the latest thread, and the content of the thread in the channel, i.e., in the chat room, and the content of the new post are confirmed. This makes it possible to confirm whether the transmission is to an appropriate channel. FIG. 13 shows an example of a case where the message is posted to channel 1. When the CPU 111 detects the pressing of the cancel button 1305 in S820, it cancels the transmission process, returns to S802, and displays the scan-to-chat screen 1101. If pressing of the cancel button 1305 is not detected, the process proceeds to S821. Then, if pressing of the send button 1306 is detected in S821, the process proceeds to S818 and executes the sending process. If pressing of the send button 1306 is not detected, the process returns to S820 and waits for detection of pressing of the cancel button 1305 or the send button 1306. In the flowchart, the preview screen 1301 is displayed after scanning is performed, but the preview screen 1301 may be displayed before or during scanning.
[0080] In S818, the CPU 111 uses the token information 1203 registered in advance to send the file generated in S814 and the posting parameters to the message app server 300 by the POST method of HTTP communication. By sending this data (the file converted from image data and the posting parameters) to the message app server 300, the message app server 300 posts the data to a new thread in the specified channel based on the received parameters. At this time, the image data itself may be posted (uploaded) to the new thread, or information such as a link for referencing the image data may be added to the new thread. The posting of image data and the addition of information are performed by the message app server 300.
[0081] In step S819, 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.
[0082] In this embodiment, it is assumed that only one piece of token information is registered, but if multiple pieces of token information are registered, the processes related to the token information, such as S804, S806, and S818, are executed for each registered token.
[0083] An example of a screen displayed on the operation panel 201 of the mobile terminal 200 as a result of the file obtained by converting the image data and the posting parameters being sent to the message application server 300 in the process of S818 will be described with reference to FIG.
[0084] Fig. 10 is a diagram showing an example of a message screen of a message application. A message screen 1001 in Fig. 10 is displayed when the message application is started on the mobile terminal 200 and the process of S881 is executed on the MFP 101. In addition, the mobile terminal 200 is in communication with the message application server 300.
[0085] When a user starts a message application on the mobile terminal 200 and logs in by inputting the ID and password of the user's account, a screen dedicated to that user is displayed.
[0086] Thread message 1005 is a thread message that is displayed when a user having an account of User 3 sends a message to the message application server 300 with the subject of Thread 2, "Can you send me the materials for next week's meeting?"
[0087] Message 1006 is a thread message that is displayed when a user having an account of User 1 posts a reply message to the message of thread message 1005.
[0088] The message 1004 is a thread message that is displayed when a user having an account of user 1 posts a reply message to the message of the thread message 1005. The message 1004 is displayed (posted) when a user having an account of user 1 uses the MFP 101 to transmit image data generated by scanning using the user ID information of user 1 and posting parameters to the message app server 300. In the example of FIG. 10, "Channel 1" is specified as the channel of the post in the posting parameters, "Thread 2" is specified as the thread of the post 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. This is also an example in which "I will send it." is specified as the comment. The file name and the comment are specified by the user on a detailed setting screen of the scan to chat (not shown).
[0089] A thread message 1007 is a thread message that is displayed when a user having an account of User 1 sends a thread 3 with the title "Design Drawings" to the message application server 300.
[0090] The thread message 1008 is also a thread message displayed when a user having an account of User 1 sends a message with the title of Thread 4 and the content "Scan Transmission Data" to the message app server 300. This is the result of the new post 1304 displayed on the preview screen 1301 in FIG. 13 being posted.
[0091] In addition, the message application screen 1001 displays the channel, group, and user in which the logged-in user participates. In addition, the other party information (1002) and the message exchange are displayed (1003). When posting, a comment with "@" at the beginning of the user's name is added, and a notification is sent to a specific user in the channel. In the case of FIG. 10, the user 3 can notice that the post has been received earlier than other members belonging to the channel, depending on the viewing terminal of the message application. If the mobile terminal 200 used by the user 3 is a smartphone, the user is notified by an icon notification function, vibration, or ringtone. If the mobile terminal 200 used by the user 3 is a desktop terminal, the user is notified by a desktop notification function or the like. In addition, when displaying this screen, the message application server 300 searches for and displays necessary information from the data structure shown in FIG. 9. For example, the posting of the message 1004 corresponds to "thread 2 + comment 3 + file 1" in the exchange content 505, and attribute information such as the name of the file 1 is obtained from 504 and displayed on the message in the form of a file icon. When the user selects this file icon, it is possible to obtain file 1 belonging to file 504. Note that although the files posted to this channel are displayed as icons here, a preview image of the file may also be displayed.
[0092] FIG. 9 is a diagram showing 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 of FIG. 10 is displayed based on this file structure. The message app server 300 manages data by having smaller groups such as channels, groups, users, and files in the largest group called workspace. The channel 501 is a type of chat room in which all members of the workspace can participate and all posted content can be searched by anyone. The group 502 is a channel for discussion that should not be made public to all members, and requires an invitation to view and participate. The user 503 is a user who participates in this workspace. The file 504 stores an attached file. The thread 506 is a conversation thread included in the channel 1. The thread is created by a user, and the owner of the thread 1 is the user 2. The thread is linked to a channel, and one or more comments are included in the thread. Furthermore, the contents 505 of the exchange between the channel, thread, group, and user are linked to each other and stored. For example, users participating in channel 1 are linked and stored in channel 1, and messages and image data exchanged on channel 1 are also linked and stored in channel 1. By storing in this manner, when a channel is selected on channel selection screen 1115, users corresponding to the specified channel information can be displayed. Users participating in that channel can be displayed.
[0093] In this embodiment, an example has been described in which the MFP 101 directly communicates with the message app server 300, receives channel information and thread information from the message app server 300, and transmits scanned and generated image data to the message app server 300. The present invention is not limited to this, and the above process may be performed via a relay server that is an information processing device capable of communicating with a plurality of MFPs. Specifically, when the relay server receives the request of S701 from the MFP 101, the relay server transmits the request to the message app server 300. The relay server receives the channel information and thread information, which are the response, from the message app server 300, and transmits the channel information and thread information to the MFP 101 that transmitted the request. The processes of S705 to S709 are performed by the MFP 101 in the same manner as in FIG. 7. The relay server then receives the generated file, channel information, thread information, and the like from the MFP 101, and transmits the received information to the message app server 300.
[0094] The relay server can also store a table in which the connection destinations and token information set in Fig. 12 are associated with each other. This allows centralized management in the relay server without storing a table in which the connection destinations and token information are associated with each other in the MFP 101, thereby reducing the risk of information leakage.
[0095] <Other embodiments> The present invention can be realized by supplying a program that realizes one or more functions of the above-mentioned embodiments to a system or device via a network or a storage medium. Then, one or more processors in the computer of the system or device can 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]
[0096] 101 MFP 300 Message App Server 400 Bot Server 111 CPU 118 Reading unit
Claims
1. An image processing device having a function of transmitting image data obtained by scanning an original to a chat server that provides a chat service, a first reception means for receiving a selection of a chat room of the chat service as a destination to which image data obtained by scanning a document is to be posted; a second receiving means for receiving an instruction to scan a document; a display control means for displaying information within the chat room selected by the first reception means after receiving the instruction; having An image processing device capable of canceling transmission of the image data to the chat server after displaying information in the chat room.
2. A setting means for setting in advance a chat room to which image data obtained by scanning a document is to be posted as a default posting destination; a selection means for automatically selecting a chat room in the first reception means when a chat room is set as a default posting destination in the setting means; The image processing apparatus according to claim 1 , further comprising:
3. When a chat room is set as a default posting destination in the setting means, information in the chat room is displayed; 3. The image processing device according to claim 2, wherein when a chat room is set as a default posting destination in the setting means, information in the chat room is not displayed.
4. 1. A method for controlling an image processing device having a function of transmitting image data obtained by scanning an original to a chat server that provides a chat service, comprising: a first reception step of receiving a selection of a chat room of the chat service as a posting destination to which image data obtained by scanning a document is posted; a second receiving step of receiving an instruction to scan the document; a display control step of displaying information in the chat room selected in the first reception step after receiving the instruction; having A control method capable of canceling transmission of the image data to the chat server after displaying information in the chat room.
5. On the computer, 1. A method for controlling an image processing device having a function of transmitting image data obtained by scanning an original to a chat server that provides a chat service, comprising: A first reception step of receiving a selection of a chat room of the chat service as a posting destination to which image data obtained by scanning a document is posted; a second receiving step of receiving an instruction to scan the document; a display control step of displaying information in the chat room selected in the first reception step after receiving the instruction; A program for executing A program capable of canceling transmission of the image data to the chat server after displaying information within the chat room.
Citation Information
Patent Citations
Image processing device, control method thereof, and program
JP2021078084A
