Image processing device, image processing method and program

Abstract

To allow a user to easily upload, to a desired thread, image data generated by an image processing apparatus reading an image of a document.SOLUTION: An image processing apparatus of the present invention has: reading means that reads an image of a document and generates image data; receiving means that receives, from an information processing apparatus, thread information indicating a thread of a talk room of a chat service, the thread designated by a user in a terminal device; and transmission means that transmits the image data to the information processing apparatus so that the image data generated by the reading means is uploaded to the thread indicated by the thread information received by the receiving means.SELECTED DRAWING: Figure 16

Description

[Technical Field]

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

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

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

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

[0005] In Patent Document 1, since it is not known to which thread in a chat room image data generated by scanning an image of a document using an image processing device will be uploaded, there is a possibility that the image data will be uploaded to a thread that the user does not intend. Also, when a user specifies a thread, it is desirable that the user be able to do so as an extension of the chat operation.

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

[0007] The image processing device of the present invention is an image processing device capable of communicating with an information processing device, and includes: a reading unit that reads an image of a document and generates image data; and thread information indicating a thread designated by a user on a terminal device, the thread being a thread in a talk room of a chat service. and a reading setting designated by the user on the terminal device. a receiving means for receiving the information from the information processing device; and Scanning the image based on the received scanning settings The generated image data and the thread information and a transmitting means for transmitting the information to the information processing device. The transmitted image data is uploaded to the thread indicated by the thread information. It is characterized by: [Effects of the Invention]

[0008] This allows a user to easily upload image data generated by an image processing device reading an image of a document to a desired thread. [Brief explanation of the drawings]

[0009] [Figure 1] A diagram showing an example of the system configuration of a chat service. [Figure 2] A diagram showing an example of the hardware configuration of the MFP400 [Figure 3] FIG. 1 shows an example of the hardware configuration of a chat server 100. [Figure 4] FIG. 2 is a diagram showing an example of the hardware configuration of each terminal such as a mobile terminal 200 and an information processing terminal 300. [Figure 5] A diagram showing the software configuration related to chat that runs on the chat server 100 and the mobile terminal 200. [Figure 6] FIG. 10 is a diagram showing an example of information corresponding to user A stored in a chat server. [Figure 7] A diagram showing an example of a chat screen [Figure 8] An example of a BOT selection screen [Figure 9] A diagram showing an example of a scan setting screen [Figure 10] A diagram showing an example of a chat screen [Figure 11] A sequence diagram showing an example of processing in response to a user's chat start operation. [Figure 12] A sequence diagram showing an example of chat message exchange processing. [Figure 13] A sequence diagram showing an example of a process for replying to a specific chat message. [Figure 14] A sequence diagram showing an example of the process of selecting a thread and replying to it [Figure 15] A sequence diagram showing an example of creating a new thread and sending a chat message [Figure 16] Sequence diagram showing an example of Scan To Chat processing [Figure 17] FIG. 10 is a diagram showing an example of information included in setting information. [Figure 18] Flowchart showing an example of a process for acquiring an associated ID [Figure 19] Flowchart showing an example of Scan To Chat processing [Figure 20] Flowchart showing an example of a process for obtaining each unique ID [Figure 21] Flowchart showing an example of authentication URL generation processing [Figure 22] 10 is a flowchart showing an example of a process for issuing an associated ID. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Note that the configurations shown in the following embodiments are merely examples of the present invention, and the present invention is not limited to the configurations shown in the drawings.

[0011] FIG. 1 is a diagram showing an example of a system configuration of a chat service. The chat service of the present invention is composed of a chat server 100, a mobile terminal 200, an information processing terminal 300, and an MFP (Multi Function Peripheral) 400, all of which are connected to a network 500. Chat server 100, which is an information processing device providing the chat service, communicates with multiple terminals via network 500 and transmits and receives chat information. Mobile terminal 200 and information processing terminal 300, which are terminal devices, access chat server 100 via the network, display a UI for using the chat service, and upload messages, image data, and the like to chat server 100. MFP 400, which is an image processing device, can receive print jobs from the chat server and execute the print jobs, or transmit scanned image data generated by scanning to chat server 100.

[0012] 2 is a diagram showing an example of the hardware configuration of the MFP 400. The MFP 400 includes a CPU 1, a ROM 2, a RAM 3, a storage 4, an operation unit I / F 5, an operation unit 6, a reading unit I / F 7, a reading unit 8, a printing unit I / F 9, a printing unit 10, a communication unit I / F 11, and a communication unit 12. Each component is controlled by the CPU 1 via a system bus 13.

[0013] CPU 1 loads control programs stored in ROM 2 or storage 4 into RAM 3 to perform various controls such as reading control and printing control. ROM 2 stores control programs executable by CPU 1. ROM 2 also stores boot programs, font data, etc. RAM 3 is the main memory and is used as a work area and a temporary storage area for expanding the various control programs stored in ROM 2 and storage 4. Storage 4 stores image data, print data, various programs, various addresses, and various setting information. Possible media for use as storage 4 include auxiliary storage devices such as SSDs (Solid State Drives) and HDDs (Hard Disc Drives), and eMMCs (Embedded Multi Media Cards).

[0014] In the MFP 400 of this embodiment, one CPU 1 executes each process shown in the flowcharts described below using one memory (RAM 3), but this is not limited to this. For example, each process can be executed by multiple CPUs, RAMs, ROMs, and storages working together. Also, some processes can be executed using hardware circuits such as ASICs and FPGAs.

[0015] The operation unit I / F 5 connects the CPU 1 to an operation unit 6, which includes a display unit such as a touch panel and hard keys. The operation unit 6 is both a display unit that displays information to the user and an operation unit that detects input from the user.

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

[0017] The printing unit I / F 9 connects the CPU 1 to a printing unit 10, such as a printer. The CPU 1 transfers image data (print data) stored in the RAM 3 to the printing unit 10 via the printing unit I / F 9. The printing unit 10 prints an image based on the transferred image data on recording paper fed from a paper feed cassette.

[0018] The communication unit I / F 11 connects the CPU 1 to the network 500. The communication unit I / F 11 allows the communication unit 12 to transmit image data and various internal device information to external devices on the network 500, and to receive print data and information on the network 500 from information processing devices on the network 500. Methods for transmitting and receiving data via the network 500 include transmission and reception using electronic mail (E-mail) 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 500 by accessing via HTTP communication from the mobile terminal 200 and chat server 100.

[0019] 3 is a diagram showing an example of the hardware configuration of chat server 100. CPU 21 reads out a control program stored in ROM 22 and executes various processes for controlling the operation of chat server 100. ROM 22 stores the control program. RAM 23 is used as a temporary storage area such as the main memory and work area of ​​CPU 21. Storage 24 stores chat messages, image data, and various chat-related information.

[0020] The operation unit I / F 25 controls an operation unit 26 including a display unit such as a touch panel and hard keys. The operation unit 26 displays information to the server administrator and inputs various settings from the server administrator, for example.

[0021] The communication unit I / F 27 controls the communication unit 28 to perform data communication with the network 500 .

[0022] The communication unit 28 transmits and receives data to and from various devices such as the mobile terminal 200, the information processing terminal 300, and the MFP 400 via the network 500.

[0023] FIG. 4 is a diagram showing an example of the hardware configuration of each terminal such as the mobile terminal 200 and the information processing terminal 300. As shown in FIG.

[0024] The CPU 41 reads out the control programs stored in the ROM 42 and executes various processes for controlling the operation of each terminal. The ROM 42 stores various control programs necessary for terminal control. The RAM 43 is used as a temporary storage area such as the main memory and work area of ​​the CPU 41. The storage 44 stores application programs that run on the terminal and various data generated by each application.

[0025] The operation unit I / F 45 includes an operation unit 46 including a display unit such as a touch panel and hard keys. The operation unit 46 displays information to the user operating the terminal and inputs instructions from the user, and in this embodiment, is also used to display chat messages and attached files between the chat server 100.

[0026] The communication unit I / F 47 controls the communication unit 48 to perform data communication with the network 500. The communication unit 48 transmits and receives data to and from various devices such as the chat server 100 and the MFP 400 via the network 500.

[0027] In this embodiment, the communication unit 48 uses Wi-Fi, which connects to the network wirelessly, and communicates with the network 500 via a wireless access point 50, but it may also be a method using other wireless methods such as LTE.

[0028] FIG. 5 is a diagram showing the software configuration related to chat that runs on chat server 100 and mobile terminal 200. As shown in FIG.

[0029] As an example, it is assumed that three services, a storage service 61, a chat service 62, and a BOT service 63, are running in the RAM 23 of the chat server 100.

[0030] It is assumed that the information in the RAM 23 is also read / written to the storage 24 as appropriate, and that no data difference occurs between the RAM 23 and the storage 24.

[0031] The storage service 61 is configured such that a storage area is allocated to each subscriber of the chat service provided by the chat server 100. In this figure, areas are allocated for user A 64, user B, user C, user D, ... up to user ZZ.

[0032] The chat service 62 has an application for each of the various services provided by the chat server 100, and the application performs various controls necessary to provide the various services.

[0033] In this embodiment, each application of the chat service 62 is controlled by an application control unit 71 of a terminal (the mobile terminal 200 or the information processing terminal 300 in FIG. 1) and processes input and output from the user.

[0034] In this embodiment, the chat application 65 controls one-on-one chats for individuals and group chats with multiple people, and each message is managed on a thread basis. The application also controls the creation of new threads and the separation of messages in a thread into separate threads. A thread is a collection of multiple chats organized into a series of conversations. By managing messages in this way, users can easily identify the topic to which a message belongs, view only the topics of interest, and efficiently communicate.

[0035] The conferencing app in the diagram is an application for conducting web conferences, and performs various controls necessary for online meetings, such as arranging meeting times, screen sharing, and file sharing.

[0036] The live event app in the diagram is an application that performs the various controls necessary for presenters to transmit information in a one-way manner.

[0037] The settings app in the figure is an application that controls various settings related to the chat service, such as personalization and other personal information settings.

[0038] The BOT service 63 cooperates with the chat service 62 and provides robots (programs) = BOTs that automate specific tasks. Each BOT in the BOT service 63 is activated by an application in the chat service 62, selected by the user, and performs various controls. In this embodiment, each BOT in the BOT service 63 cooperates with a BOT control unit 73 of a terminal (the mobile terminal 200 or the information processing terminal 300 in FIG. 1) and performs various controls required for automation.

[0039] In the diagram, Scan To Chat BOT66 is a BOT that automates the process from scanning (reading) documents to sending chat messages on the MFP400, and controls the input and output of information required to automate a series of tasks, such as the various scan settings required for scanning, the format of the digital file after digitization, and the destination for chat replies.

[0040] Also, in the figure, the Chat Print BOT is a BOT that automates the process of printing information exchanged within a chat to the MFP 400. It controls input and output, from selecting the messages, attachments, and shared files to be printed, to setting the number of copies to print and print settings such as single-sided or double-sided printing.

[0041] Also, in the figure, the MFP management BOT is a BOT that manages the operating status of the MFP 400, and controls the issuing of work instructions for recovering from problems that occur in the MFP 400 and the automation of work for when consumables run out.

[0042] The RAM 43 of the mobile terminal 200 operates two control units, an application control unit 71 and a BOT control unit 72, and these control units cooperate to provide the chat service according to the present invention. The application control unit 71 downloads the corresponding program from the chat service 62 of the chat server 100 and performs various controls to provide each function to the user.

[0043] Similarly, the BOT control unit 72 downloads the corresponding program from the BOT service 63 of the chat server 100 and performs various controls related to the provision of each BOT function to the user.

[0044] In this embodiment, each downloaded program realizes its function by controlling the WebAPI provided by the chat service 62 and BOT service 63 of the chat server 100 via REST (Representational State Transfer), which will be described later.

[0045] FIG. 6 is a diagram showing an example of information corresponding to user A stored in the chat server.

[0046] Information corresponding to user A64 is first stored separately for each chat service 62 used. In this figure, it is shown that there are branches into 1:1 chat (A_64_1), group chat (A_64_2), and others (the part marked with ... (A_64_3)).

[0047] The 1:1 chat (A_64_1) is stored separately for each user (A_64_10) with whom user A is chatting individually. This figure shows that user A is chatting individually with each of users Z to N.

[0048] In addition, the interaction of user Z in the 1:1 chat (A_64_1) branches into threads (A_64_11), and it is shown that there are interactions in threads A, B, and C.

[0049] Thread A of thread (A_64_11) shows that chat message (A_64_12) is stored in the order in which it was exchanged, indicating that there are three chat messages exchanged. Similarly, thread B shows that it consists of four chat messages, and thread C shows that it consists of three chat messages.

[0050] Next, in the group chat (A_64_2) of user A64, there are branches for groups called channels (A_64_20) for multiple users to communicate simultaneously. Channel (A_64_20) indicates that there is interaction with multiple groups.

[0051] Here, a channel is a talk room (chat room) in which multiple users participate, and messages and files can be exchanged between the multiple participating users.

[0052] Each channel has a structure including a thread (A_64_21) and a chat message (A_64_22), similar to the 1:1 chat (A_64_1).

[0053] Details of A_64_3 are omitted, but information on conferences, live events, settings, etc. corresponding to the chat service 62 in FIG. 5 is configured in the same format as users (A_64_10) and channels (A_64_20).

[0054] Each of the channels A_64_10 and A_64_20 has a unique chat ID (Channel-id), each of the threads A_64_11 and A_64_21 has a unique thread ID (Thread-id), and each of the messages A_64_12 and A_64_22 has a unique message ID (Message-id).

[0055] This unique ID is a uniquely identifiable value and is managed by the storage service 61. When data is returned in response to the content request 1003 in FIG. 11, the unique ID is sent from the chat server 100 to each terminal as additional information for the message and thread information.

[0056] Fig. 7 is a diagram showing an example of a chat screen. Note that the information displayed in this diagram is obtained by mobile terminal 200 from chat server 100 by processing the sequence shown in Fig. 10, which will be described later. This information is obtained through cooperation between chat application 65 and application control unit 71.

[0057] The chat screen D1 shows an example of chat messages and threads exchanged between user A64 and user Z in a one-on-one chat (A_64_1). In other words, this chat screen D1 is a screen for displaying a chat room.

[0058] D10 in the chat screen D1 is a section that displays a list of services provided by the chat service 62, and is a section where you can select which chat service to use from 1:1 chat, group chat, etc. D10 shows that 1:1 chat (A_64_1) has been selected.

[0059] D11 in the chat screen D1 is a section that displays a list of users (A_64_10) in Fig. 6. In this figure, it is shown that user Z is selected from users (A_64_10).

[0060] Thread D12 in chat screen D1 is the section that displays a list of threads (A_64_11) in FIG. 6, and in this figure, chat messages exchanged in thread A are displayed, while chat messages in threads B and C are omitted. The reply button D20 in chat screen D1 is a button that is operated when replying to an individual chat message. In this embodiment, when the reply button D20 is operated, the corresponding chat message for which the reply was pressed becomes the starting point, and a thread is automatically branched (a new thread is created).

[0061] The reply button D21 on the chat screen D1 is a button that can be operated when replying to the thread itself. This button can be operated whether chat messages are displayed, such as in thread A, or when no chat messages are displayed, such as in threads B and C.

[0062] The create new thread button D40 on the chat screen D1 is a button for instructing the creation of a new thread. When the create new thread button D40 is selected, a new thread is created, and a chat message can be entered. Note that when any of the reply button D20, reply button D21, and create new thread button D40 is operated, an edit field D30 for entering a chat message is displayed. When the close button D22 is selected, the edit field D30 is no longer displayed. In the example of FIG. 7, the reply button D21 of the thread D12 is selected, and the edit field D30 is displayed. The edit field D30 displays a file attachment button, a stamp input button, a bot selection button, and a send button. When the attach file button is selected, a file stored in the mobile terminal 200 can be referenced and uploaded. When the stamp input button is selected, the selected stamp is posted. When the bot selection button is selected, a screen for selecting a bot app installed on the chat server 100 is displayed. When the send button is selected, the entered characters can be posted as a message.

[0063] 8 is a diagram showing an example of a BOT selection screen. The BOT selection screen D100, which is displayed when the BOT selection button is selected, is displayed on the chat screen D1 and displays a list of BOTs supported by the BOT service 63 of the chat server 100.

[0064] When the Scan To Chat BOTD101 is selected and the Select Execute button D111 is selected, the scan setting screen shown in FIG. 9 is displayed.

[0065] 9 is a diagram showing an example of a scan setting screen. The scan-to-chat screen D200 is displayed on the chat screen D1. The pull-down menu D201 is used to select the MFP to send the scan instruction to. The pull-down menu D202 is used to specify the reading destination, and allows the user to select either the ADF (Automatic Document Feeder) of the MFP 400 or the flatbed platen.

[0066] Pull-down menu D203 is for selecting the color, and one of black and white, grayscale, and color can be selected. Pull-down menu D204 is for selecting the reading method, and one of single-sided, double-sided (opens left and right), and double-sided (opens left and right) can be selected.

[0067] Pull-down menu D205 is used to select the scan size. This diagram shows an example where A4 size scanning has been selected. Pull-down menu D206 is used to select the file format for the image data to be digitized and stored. In this diagram, PDF format has been selected.

[0068] A pull-down menu D207 is used to specify whether or not to include a mention (notification) after the scan to chat. If mention is enabled, the user can specify the user to be mentioned.

[0069] The pull-down menu D208 specifies whether or not to perform OCR on scanned and digitized data. If the OCR results indicate that the data contains text, the data is converted into text code and the text is retrieved. Furthermore, if text exists, the first few characters are automatically entered into the chat message.

[0070] Cancel D210 is operated to instruct cancellation of this process. Scan execution button D211 is operated to instruct Scan To Chat by sending setting information selected from other pull-down menus to the MFP 400 selected in D201.

[0071] 10 is a diagram showing an example of a chat screen. Message D300 indicates a chat message posted when Scan To Chat is executed from MFP 400. File D301 indicates a file uploaded when MFP 400 executes Scan To Chat. Attached files have different extensions depending on the file format specified in D206, and a file viewer (viewing software) is provided on mobile terminal 200 or information processing terminal 300 for each extension.

[0072] By selecting the file D301, the file can be downloaded or displayed.

[0073] 11 is a sequence diagram showing an example of processing performed by a user to start a chat. This sequence is executed by the CPU of each device reading a program stored in ROM or storage into RAM. At 1000, the user operates the operation unit 46 of the terminal (mobile terminal 200 or information processing terminal 300) to instruct the application control unit 71 to start communication with the chat application 65. When starting this communication, information required for authentication at 1001 in the diagram is input via the operation unit 46.

[0074] Next, in 1001, a user operating the mobile terminal 200 or the information processing terminal 300 performs authentication with the chat server 100 to use the chat service 62. Authentication is achieved by sending information to the chat server 100 to identify a user who is permitted to use the service (a user for whom data is held by the storage service 61) in the [ACCOUNT ID] and [PASSWORD] shown as an example in FIG.

[0075] Although not shown, the character strings stored in [ACCOUNT ID] and [PASSWORD] are set on the screen displayed on the operation unit 46 during the chat start operation in 1000.

[0076] Next, the chat service 62 of the chat server 100 performs authentication using the character strings specified in [ACCOUNT ID] and [PASSWORD], and if authentication is successful, returns the service ID required for subsequent services to the application control unit 71 of the terminal operated by the user.

[0077] Next, in 1003 and 1004, the user obtains a list of content available to the user from the storage service 61, chat service 62, and BOT service 63 for the chat service 62 of the chat server 10. The results obtained here are displayed on the screen as shown in FIG. 7. D10 in FIG. 7 is the content of the chat service 62, and D11 and D12 in FIG. 7 are information obtained from the storage service 61. The information obtained from the BOT service 63 is the same as that displayed on the BOT selection screen in FIG. 8.

[0078] The information acquired from the storage service 61 includes a unique ID that allows each of the chats, users, threads, chat messages, group chats, and channels in Fig. 6 to be uniquely identified. The unique ID can be used to identify the chats and threads.

[0079] 12 is a sequence diagram showing an example of the processing for exchanging chat messages. This sequence is executed by the CPU of each device reading a program stored in ROM or storage into RAM. In this diagram, it is assumed that both user A and user Z have completed authentication for chat service 62 of chat server 100.

[0080] First, in 1011, user A operates operation unit 46 of mobile terminal 200 or information processing terminal 300 to input a chat message. After inputting the chat message, in 1012 the chat message is sent to chat application 65 of chat service 62 of chat server 100. Upon receiving this, chat application 65 of chat service 62 of chat server 100 updates the contents of user A 64 and user Z in storage service 61 of chat server 100 in 1013.

[0081] After the update, in 1014, the mobile terminal 200 or the information processing terminal 300 notifies (mentions) the user Z who operates the terminal via the application control unit 71 of the terminal.

[0082] Next, at 1015, the user operates the operation unit 46 to input a chat message, at 1016 the chat message is sent to the chat application 65, at 1017 the storage service 61 is updated, and at 1018 the other party is notified (mentioned). The exchange of the above two chat messages is displayed on the operation unit 46 as chat message b and chat message c in FIG. 7.

[0083] 13 is a sequence diagram showing an example of a process for replying to a specific chat message. This sequence is executed by the CPU of each device reading a program stored in ROM or storage into RAM. The process in FIG. 13 corresponds to the process when the reply button D20 in FIG. 7 is operated.

[0084] First, in 1101, a selection of a chat room by a user is accepted via the application control unit 71 of the mobile terminal 200 or the information processing terminal 300. When a chat is selected, the {Channel-id} value is determined, and one of 1:1 chat, group chat, or others (conference, live event, etc.) is identified. In addition, a user associated with each is also selected. The processing of 1101 corresponds to the selection operation of D10 and the selection operation of D11 in FIG. 7.

[0085] Next, a thread is selected in 1102. When a thread is selected, a {Thread-id} value is specified. In Figure 7, it is shown that one of threads A, B, or C of D12 has been selected.

[0086] Next, the chat message to which the reply is to be made is selected in 1103. When the chat message is selected, the {Message-id} value is specified. This indicates that an individual chat message is selected with the reply button D20 in FIG.

[0087] When confirming chats, channels, threads, and chat messages, each target data is assigned a unique ID, as explained in Figure 6.

[0088] When the reply button D20 is operated in 1104, in 1105 and 1106, a reply message ID corresponding to the specific message is obtained.

[0089] In this embodiment, at 1105, the application control unit 71 sends "https: / / businesschat.com / users / {user-id} / Services / {Service-id} / Channels / {Channel-id} / Threads / {THread-id} / Messages / {Message-id} / Replyid=? / " to the chat service 62.

[0090] Next, in 1106, the chat service 62 determines from "Replyid=?" that a reply message ID is to be obtained. Then, based on the individual unique IDs specified by {user-id}, {Service-id}, {Channel-id}, {Thread-id}, and {Message-id}, the desired information is obtained from the chat server 100 and returned.

[0091] Note that {user-id} is the same value as the [ACCOUNT ID] used in 1001 in Fig. 11. {Service-id} indicates the value obtained from the chat server 100 in 1002 in Fig. 11. {Channel-id}, {Thread-id}, and {Message-id} can identify the corresponding unique IDs in Fig. 6 among 1101, 1102, and 1103.

[0092] Next, a list of members related to the selected message is obtained in steps 1107 and 1108. The information collected as described above is stored in the mobile terminal 200 as chat information 2101 required for attaching a scanned image in Fig. 17, which will be described later.

[0093] Fig. 14 is a sequence diagram showing an example of a process for selecting a thread and replying. This sequence is executed by the CPU of each device reading a program stored in ROM or storage into RAM. The processes of 1201 to 1203 are similar to 1101 to 1103 in Fig. 13, so a description thereof will be omitted.

[0094] In 1204 and 1205, a reply message ID is obtained from the individual unique IDs determined in 1201 to 1203. 1105 and 1106 in Fig. 13 are the same except that {Message-id} does not exist.

[0095] In 1206, the chat server 100 returns the desired information based on the {user-id}, {Service-id}, {Channel-id}, and {Thread-id} received in 1205.

[0096] Figure 15 is a sequence diagram showing an example of the process of creating a new thread and sending a chat message. This sequence is executed by the CPU of each device reading a program stored in ROM or storage into RAM. The sequence in Figure 15 corresponds to the process when the new thread creation button D40 in Figure 7 is operated.

[0097] 13. 1301 is the same as 1101 in Fig. 13, and therefore description thereof will be omitted. In 1302, the mobile terminal 200 accepts the user's selection of the new thread creation button D40 in Fig. 7.

[0098] Next, in 1303, the mobile terminal 200 accesses "https: / / businesschat.com / users / {user-id} / Services / {Service-id} / Channels / {Channel-id} / Threads=? / " and instructs the chat server 100 to create a new thread. The mobile terminal 200 processes the ID returned from the chat server 100 in 1304 as a reply message ID.

[0099] In the command 1303, businesschat.com is information for identifying the chat server 100, and "Threads=?" in the parameter instructs the creation of a new thread.

[0100] Fig. 16 is a sequence diagram showing an example of the Scan To Chat process. Note that in this diagram, the explanation is given assuming that the user has completed authentication of the chat service 62 of the chat server 100. The sequence in Fig. 16 is also based on the premise that the user has selected the reply button D20 and then the BOT selection button in order to reply to the chat message c in the thread D12. The sequence in Fig. 16 is executed by the CPU of each device reading a program stored in the ROM or storage into the RAM.

[0101] 1401 indicates that the user performing a chat operation performs a BOT selection operation via the application control unit 71 of the mobile terminal 200. Specifically, the mobile terminal 200 accepts the selection of a desired BOT application from among the BOT applications displayed on the BOT selection screen D100 of Fig. 8. Here, the mobile terminal 200 accepts the selection of the Scan To Chat BOTD101 and the selection execution button D111.

[0102] Next, in 1402, the application control unit 71 notifies the BOT control unit 72 of the mobile terminal 200 that the scan to chat BOT has been selected and operated.

[0103] Next, in 1403, the BOT control unit 72 instructs the BOT service 63 of the chat server 100 to start up the scan-to-chat BOT.

[0104] Next, the BOT service 63 confirms that a cooperable MFP exists on the network in 1404. The cooperable MFP may be registered in advance in the chat server 100, or may be dynamically searched for, for example, from MIB (Management Information Base) information.

[0105] In this embodiment, from the viewpoint of security etc., a method of pre-registration is adopted, and in 1404, it is confirmed whether the MFP can be used online or not offline.

[0106] Next, in 1405 , the BOT service 63 of the chat server transmits a list of registered MFPs to the BOT control unit 72 of the mobile terminal 200 .

[0107] In 1406, the BOT control unit 72 of the mobile terminal 200 instructs the application control unit 71 to display a list of registered MFPs on the chat screen.

[0108] In 1407, the user is prompted to select which MFP to use for scanning from the displayed list of MFPs. Specifically, the mobile terminal 200 displays a list of registered MFPs, as in the pull-down menu D201 on the scan-to-chat screen D200 in Fig. 9, and accepts a selection from the user.

[0109] As a result of the MFP being selected, in 1408 the application control unit 71 of the mobile terminal 200 notifies the BOT control unit 72 of information indicating the selected MFP.

[0110] Next, in 1409, the BOT control unit 72 of the mobile terminal 200 instructs the BOT service 63 to issue a temporary link key (nonce) to enable message and file transmission from the MFP 400 to the chat server 100.

[0111] In 1410, the BOT service 63 transmits to the MFP 400 an authentication URL required for issuing a temporary link key.

[0112] In 1411, the MFP 400 performs authentication processing for the chat service 62 of the chat server 100 using the URL obtained in 1410.

[0113] In 1412, the chat service 62 of the chat server 100 checks whether the authentication is correct based on the expiration date of the authentication URL, etc., and if it is determined to be correct, issues a temporary link key in 1413.

[0114] Next, in 1414, the BOT service 63 of the chat server 100 instructs the BOT control unit 72 of the mobile terminal 200 to display the scan to chat screen D200.

[0115] In 1415, the application control unit 71 of the mobile terminal 200 receives an instruction to display the scan to chat screen D200 from the BOT control unit 72 and displays the scan to chat screen D200. In 1416, the application control unit 71 of the mobile terminal 200 receives each setting from the user on the scan to chat screen D200 and waits for the scan execution button D211 to be selected.

[0116] When the scan execution button D211 is selected, the application control unit 71 sends an execution instruction to the BOT control unit 72 at 1417. Then, at 1418, the BOT control unit 72 sends an execution instruction for scan-to-chat and the setting information set on the scan-to-chat screen D200 to the BOT service 63 of the chat server 100.

[0117] In 1419, the BOT service 63 of the chat server 100 transmits the execution instruction and setting information received in 1418 to the MFP 400. This setting information includes scan settings (reading settings), mention destinations, and thread information. Note that this thread information is determined based on which thread the reply button selected by the user on the chat screen D1 displayed on the mobile terminal 200 corresponds to. For example, in the example of FIG. 7, the user selects the reply button D20 for thread D12, so thread information indicating thread D12 is included in the setting information. It may be the BOT control unit 72 of the mobile terminal 200 or the BOT service 63 of the chat server 100 that determines which thread information to include in the setting information.

[0118] At 1420, the MFP 400 generates a scan job based on the setting information received at 1419. Then, at 1421, the MFP 400 executes the scan job, reads an image of the document, and generates image data. At 1422, the MFP 400 converts the generated image data into the file format set on the Scan To Chat screen D200.

[0119] Next, at 1423, MFP 400 uses the temporary link key acquired at 1413 to send image data to chat service 62 of chat server 100. It also sends an instruction to upload the image data. Here, the thread to which the image data is to be uploaded is determined based on the thread information included in the setting information received at 1419, so that the image data is uploaded to the thread indicated by the thread information. In other words, the upload instruction sent at 1423 includes information for specifying the thread. This information for specifying the thread may be the thread information received at 1419 itself.

[0120] In this embodiment, an example has been described in which thread information of a thread designated by a user is transmitted to the MFP 400, and the MFP 400 transmits an instruction to upload image data to the thread indicated by the thread information, but the present invention is not limited to this. For example, the thread information designated by a user is stored by the BOT service 63, and the BOT service 63 of the chat server 100, which receives the image data generated from the MFP 400 and an upload instruction, uploads the image data to the chat service 62. At this time, the thread to which the BOT service 63 uploads is determined based on the thread information stored by the BOT service 63.

[0121] At 1424, chat service 62 of chat server 100 stores the image data received from MFP 400. Then, at 1425, chat service 62 updates chat screen D1 based on the image data being uploaded to mobile terminal 200, so that chat screen D1 of Fig. 10 is displayed on mobile terminal 200. Furthermore, if a mention destination is set, chat service 62 of chat server 100 transmits a notification to the terminal of the user specified as the mention destination.

[0122] In 1427, the MFP 400 transmits a scan job completion notification to the BOT service 63 based on the completion of the scan job execution.

[0123] In 1428, the BOT service 63 transmits information instructing the closing of the scan to chat screen D200 to the BOT control unit 72 of the mobile terminal 200. Note that the scan to chat screen D200 may be closed by selecting the scan execution button D211.

[0124] Fig. 17 is a diagram showing an example of information included in the setting information. The setting information sent to the MFP 400 in 1419 of Fig. 16 includes scan setting information (read setting information) and chat information.

[0125] The user setting information 2001 stores information set on the scan to chat screen D200 in FIG.

[0126] The scan setting information 2001 includes MFP information 2002, reading destination information 2003, color information 2004, double-sided information 2005, reading size information 2006, file format information 2007, and OCR information 2008. Each piece of information 2002 to 2008 included in the scan setting information 2001 is information set in each pull-down menu D201 to 206 and D208 on the scan to chat screen D200.

[0127] The chat information 2101 includes user information 2102 , authentication information 2103 , posting destination information 2104 , reply destination information 2105 , mention information 2106 , member information 2107 , an association ID 2108 , and a chat message 2109 .

[0128] User information 2102 is the [ACCOUNT ID] set in 1001 in Fig. 11. In other words, it is information about the user who instructed to execute Scan To Chat. Authentication information 2103 is the service ID returned in 1002 in Fig. 11.

[0129] The posting destination information 2104 includes the channel information {Channel-id} of the channel corresponding to the thread to which the user instructed to execute a scan to chat, the thread information {Thread-id} of the thread, and the message information {Message-id} of the message to be replied to.

[0130] The reply destination information 2105 is, for example, an ID that is requested in Replyid=? in 1105 of FIG. 13 and returned in response in 1106.

[0131] Mention information 2106 is information set in the pull-down menu D207. Member information 2107 is information indicating the mention destination user set in the pull-down menu D207.

[0132] The association ID 2108 stores information called a nonce, which is an association key and enables temporary use.

[0133] The chat message 2109 is a message based on character information obtained by performing character recognition processing on image data generated by scanning when OCR is selected in the pull-down menu D208. This OCR may be performed on an area preset by the user, or on all areas.

[0134] 18 is a flowchart showing an example of processing for acquiring an associated ID. This flow is realized by the CPU 1 of the MFP 400 reading a program stored in the ROM 2 or the storage 4 into the RAM 3 and executing it. This flow is also a flowchart showing processing for acquiring a nonce, which is an associated ID, 1409 to 1413 in FIG. 16.

[0135] In S201, the CPU 1 checks whether an instruction to obtain a link key has been issued from the BOT service 63 of the chat server 100. In this embodiment, the link key can be obtained by accessing an authentication URL for issuing a link key.

[0136] In S202, the CPU 1 instructs the chat service 62 to access the URL acquired in S201 and issue the corresponding link key.

[0137] In S203, the chat service 62 checks whether the authentication is correct based on the expiration date of the accessed authentication URL, and the CPU 1 waits for a temporary link key to be issued.

[0138] In S204, the CPU 1 stores the association key issued by the chat service 62 as an association ID 2108.

[0139] Fig. 19 is a flowchart showing an example of scan-to-chat processing. This processing is realized by the CPU 1 of the MFP 400 reading a program stored in the ROM 2 or storage 4 into the RAM 3 and executing it. This is also a flow showing the processing related to 1419 to 1423 in Fig. 16. The processing in Fig. 19 is processing performed when the MFP 400 receives a scan instruction (read instruction) and setting information from the BOT service 63 of the chat server (1419).

[0140] In S210, the CPU 1 checks whether a request to execute Scan To Chat has been received. The request to execute Scan To Chat is sent from the BOT service 63 to the MFP 400 when the scan execution button D211 on the Scan To Chat screen D200 in Fig. 9 is selected. If an execution request has been received, the process proceeds to S211. If not, the process ends.

[0141] In S211, the CPU 1 receives the execution request and the setting information in JSON format or the like, and generates a scan job based on the setting information.

[0142] In S212, the CPU 1 controls the reading unit 8 to read the image of the document and generate image data. Furthermore, based on the OCR information included in the received setting information, the CPU 1 performs OCR processing on the generated image data. If the OCR information indicates that OCR processing should not be performed, the processing is not performed.

[0143] In S213, the CPU 1 determines whether the scan is complete, and if so, proceeds to S214, otherwise repeats S213.

[0144] In S214, the CPU 1 converts the generated image data into the file format specified by the file format information included in the received setting information. Note that the process of S214 does not necessarily have to be executed.

[0145] In S215, it is determined whether the thread information is specified based on the thread information included in the setting information received together with the execution request in S210. In this embodiment, this determination is made based on whether the value is NULL or not, and if the value is NULL, the process proceeds to S216. If a value is included, the thread specified by the thread information is determined as the upload destination for the image data. In S216 and S217, the CPU 1 determines the new thread as the upload destination for the image data.

[0146] In S218, the CPU 1 determines whether or not a character string exists as a result of OCR. If it exists, the process proceeds to S219. If it does not exist, the process proceeds to S220.

[0147] In S219, the CPU 1 sets the character information acquired by executing OCR as a chat message.

[0148] In S220, the CPU 1 sets a fixed character string as the chat message: "Attach an image file scanned by the MFP." Note that although a fixed character string may be set in this way, it is also possible not to set anything.

[0149] In S221, the CPU 1 determines whether or not a mention destination is specified based on the mention destination information included in the received setting information. If a mention destination is specified, the process proceeds to S222, and if not, the process proceeds to S223.

[0150] In S222, the CPU 1 sets a user (mention destination) to whom a notification is to be sent when image data and a chat message are uploaded (posted) based on the mention destination information.

[0151] In S223, the CPU 1 uploads the generated image data and chat message to the thread identified in the previous process, and executes a transmission process so that a notification is sent to the identified mention destination.

[0152] In the above flow, an example of identifying thread information is described, but in addition to the thread information, channel information indicating the channel and the message to be replied to are also identified, and the posting of image data is performed based on the identified information.

[0153] By performing the above process, the image data generated by the image processing device reading an image of a document can be easily uploaded to a desired thread by the user.

[0154] Fig. 20 is a flowchart showing an example of a process for obtaining each unique ID. The flow of Fig. 20 is realized by CPU 21 of chat server 100 reading a program stored in ROM 22 or storage 24 into RAM 23 and executing it.

[0155] In S301, the CPU 21 checks whether or not the request is for obtaining a channel ID. If it is a request for obtaining a channel ID, the process proceeds to S302. If not, the process proceeds to S304.

[0156] In S302, the CPU 21 acquires a channel ID. In S304, the CPU 21 determines whether or not the request is for acquiring a thread ID. If it is a request for acquiring a thread ID, the process proceeds to S305. If not, the process proceeds to S306.

[0157] In S305, the CPU 21 acquires a thread ID. In S306, the CPU 21 determines whether or not the request is for acquiring a message ID. If the request is for acquiring a message ID, the process proceeds to S307. If not, the process proceeds to S308, where the CPU 21 executes other processes.

[0158] In step S307, the CPU 21 acquires the message ID. In step S303, the CPU 21 transmits the acquired ID to the application control unit 71.

[0159] 21 is a flowchart showing an example of the authentication URL generation process. This process is executed by the CPU 21 of the chat server 100 reading a program stored in the ROM 22 or storage 24 into the RAM 23. In S310, it is confirmed whether or not there is a request to generate an authentication URL. If there is a request to generate an authentication URL in S310, the process proceeds to S311. In S311, a URL requiring authentication is generated to obtain an associated ID. In S312, the generated authentication URL is returned to the request source.

[0160] 22 is a flowchart showing an example of an associated ID issuing process. This process is executed by the CPU 21 of the chat server 100 reading a program stored in the ROM 22 or storage 24 into the RAM 23. In S320, it is confirmed whether or not the authentication URL is the one generated in S311 of FIG. 21. If it is the authentication URL, the process proceeds to S321. In S321, an associated ID is generated, and in S322, the generated associated ID is returned to the request source of this request.

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

[0162] 100 Chat Server 200 mobile devices 400 MFP

Claims

1. An image processing device capable of communicating with an information processing device, a reading means for reading an image of an original and generating image data; a receiving means for receiving, from the information processing device, thread information indicating a thread in a talk room of a chat service specified by a user on a terminal device and a read setting specified by the user on the terminal device; a transmitting means for transmitting the image data generated by the reading means based on the received reading setting and the thread information to the information processing device; The image processing device is characterized in that the transmitted image data is uploaded to the thread indicated by the thread information.

2. the receiving means receives the thread information and a read instruction from the information processing device; 2. The image processing apparatus according to claim 1, wherein the reading means reads an image of the document based on the reading instruction, generates the image data, and the transmitting means transmits the image data and the thread information to the information processing apparatus.

3. The image processing device according to claim 2, characterized in that, based on the reception of the reading instruction by the receiving means without the thread information being received, the transmitting means transmits the image data to the information processing device so that the image data is uploaded to a newly created thread.

4. An image processing device as described in any one of claims 1 to 3, characterized in that the receiving means receives the thread information transmitted from the information processing device based on the thread specification accepted by the terminal device while the talk room screen is displayed on the display unit of the terminal device connected to the information processing device.

5. An image processing device as described in any one of claims 1 to 4, characterized in that the receiving means receives reading settings sent from the information processing device, which reading settings are accepted by the terminal device while the talk room screen is displayed on the display unit of the terminal device connected to the information processing device.

6. 6. The image processing device according to claim 1, wherein the transmitting means also transmits a message to the information processing device based on character information obtained by performing character recognition processing on the generated image data.

7. A control method executed by an image processing device, comprising: a reading step of reading an image of a document and generating image data; a receiving step of receiving, from an information processing device, thread information indicating a thread in a talk room of a chat service specified by a user on a terminal device and a read setting specified by the user on the terminal device; a transmitting step of transmitting the image data generated by reading the image based on the received reading setting in the reading step and the thread information to the information processing device; The control method for an image processing apparatus, wherein the transmitted image data is uploaded to the thread indicated by the thread information.

8. the receiving step receives the thread information and a read instruction from the information processing device; The control method according to claim 7, characterized in that in the reading process, an image of the original is read based on the reading instruction, and the image data is generated, and in the sending process, the image data is sent to the information processing device so that the image data generated in the reading process is uploaded to the thread indicated by the thread information received in the receiving process.

9. The control method according to claim 8, characterized in that the receiving step does not receive the thread information, but, based on receiving the reading instruction, transmits the image data to the information processing device so that the image data is uploaded to a newly created thread in the transmitting step.

10. A control method described in any one of claims 7 to 9, characterized in that the thread information transmitted from the information processing device based on the thread specification accepted by the terminal device while the talk room screen is displayed on the display unit of the terminal device connected to the information processing device is received in the receiving process.

11. A control method described in any one of claims 7 to 10, characterized in that the receiving process receives reading settings sent from the information processing device, which reading settings are accepted by the terminal device while the talk room screen is displayed on the display unit of the terminal device connected to the information processing device.

12. A control method according to any one of claims 7 to 11, characterized in that in the transmission step, a message is also transmitted to the information processing device based on character information obtained by performing character recognition processing on the generated image data.

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

Images