Message delivery system and program

Abstract

To improve operability of a file sender in processing on a file according to user information on a recipient when transmitting the file in sending and receiving messages.SOLUTION: A system comprises a storage device 16g which stores user information on a user who sends and receives message in a chart room of a message service, and a CPU 16b. When executing a program to transmit a message for sharing a file, the CPU 16b inquires a first user who is the sender of the message about processing on the file if the processing is required based upon the user information, and executes the processing on the file on receiving an execution direction for the processing from the first user.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a message providing system and a program.

Background Art

[0002] Patent Document 1 describes an access control system and an access control program that can appropriately set access rights to stored content while ensuring security. That is, a storage unit that stores content, a determination unit that determines whether a user notified of the storage location of the content has access rights to the content, and if the user does not have access rights, determines the confidentiality of the content according to predetermined conditions, and if it is determined that the confidentiality is not high, an access right setting support unit that sets temporary access rights to the content for the user, and a service unit that enables viewing of the content for a user to whom access rights or temporary access rights to the content are set. An access control system is described.

Prior Art Documents

Patent Documents

[0003] <00]]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, in a message service where users exchange messages in a chat room, when a user shares a file with another user, there is a known technique in which the system appropriately checks for changes in access rights to the file according to the access rights set for the file.

[0005] For example, when sending a file that is accessible to all users who know its location, the sender does not ask the user to confirm the change in access permissions. However, when sending a file that is accessible only to specific users, the sender may ask the user to confirm the change in access permissions. When sending a file that is accessible only to specific users, the sender is asked to confirm the change in access permissions, and the sender must verify whether the recipient user is one of the specific users who can access the file, and if necessary, set the access permissions for the recipient user on the file. Checking the recipient's user information and performing actions on the file according to that user information when sending such a file is a cumbersome operation for the sender.

[0006] The present invention aims to improve the usability for file senders when sending files in message exchange, specifically when performing processing on files according to the recipient's user information. [Means for solving the problem]

[0007] A first aspect of the present invention comprises an acquisition means for acquiring user information of users exchanging messages in a chat room on a message service, and a processor, wherein the processor executes a program to send a message to share a file, and the sender of the file in the message content included in the user information Processing details This message delivery system determines whether processing is necessary for the file based on the text conveying the intent, and if it determines that processing is necessary for the file, it inquires about the processing from the first user who sent the message, and if it receives an instruction from the first user to execute the processing, it executes the processing on the file.

[0008] The second aspect is a message provision system according to the first aspect, wherein the user information is whether or not a second user, who is the recipient of the message, has access rights to the file, and the processor, if it determines that the second user does not have access rights to the file, queries the first user to ask whether or not to grant access rights to the second user.

[0009] The third aspect is a message provision system according to the second aspect, wherein the processor queries only the first user and not the second user whether or not to grant the access rights.

[0012] The 4 In this configuration, the processor determines whether or not the file has been checked when the message content contains wording indicating confirmation. The recipient of the aforementioned message This is a message provision system related to the first type of inquiry, which involves contacting a second user.

[0013] The fifth aspect is the user information to teeth, moreover, The first embodiment of a message provision system is a system that provides at least one of the file size, resolution, and file format of the file desired by a second user who is the recipient of the message, and the processor queries whether or not to convert at least one of the file size, resolution, and file format of the file when at least one of the file size, resolution, and file format of the file does not match the file size, resolution, and file format desired by the second user.

[0014] The sixth aspect is the user information to teeth, moreover,The first embodiment of the message provision system is a system that provides at least one of the file size and resolution of the file desired by a second user who is the recipient of the message, and the processor queries whether to convert at least one of the file size and resolution of the file when the file size of the file is greater than or equal to a threshold, or when the resolution of the file is less than a threshold.

[0015] The 7 The embodiment is a message provision system according to either the fifth or sixth embodiment, wherein the processor queries the first user and the second user.

[0016] The eighth aspect comprises an acquisition means for acquiring user information of users exchanging messages in a chat room on a messaging service, and a processor, wherein the processor executes a program to send a message that shares a file, and the sender of the file in the message contained in the user information Processing details This message delivery system determines whether processing is necessary for the file based on the text conveying the intent, and if it determines that processing is necessary for the file, it selectively switches between the first user who sent the message and the second user who received the message, depending on the type of processing, to inquire about the processing, and if it receives an instruction to execute the processing, it executes the processing on the file.

[0017] The 9 The manner of is, The system comprises an acquisition means for acquiring user information of users exchanging messages in a chat room on a messaging service, and a processor, wherein the processor, by executing a program, determines whether processing is necessary on the file based on the user information when sending a message to share a file, and if it determines that processing is necessary on the file, it selectively switches between the first user who is the sender of the message and the second user who is the recipient of the message, depending on the type of processing, to inquire about the processing, and if it receives an instruction to execute the processing, it executes the processing on the file. The processor queries the first user when there is only one type of processing, and queries the second user when there are multiple types of processing. , Me It is a message delivery system.

[0018] The 10The embodiment is a message provision system according to the ninth embodiment, wherein the user information is at least one of the file size, resolution, and file format of the file desired by the second user, and the processor queries the second user when at least one of the file size, resolution, and file format of the file does not match the file size, resolution, and file format desired by the second user, and there are multiple types of processing because at least one of the file sizes, resolutions, and file formats of the files desired by multiple second users are different from each other.

[0019] The 11 The embodiment is a message provision system according to the ninth embodiment, wherein the user information is at least one of the file size, resolution, and file format of the file desired by the second user, and the processor queries the first user when at least one of the file size, resolution, and file format of the file does not match the file size, resolution, and file format desired by the second user, and at least one of the file sizes, resolutions, and file formats of the files desired by multiple second users is the same, so the type of processing is single.

[0020] The 12 The embodiment is a message provision system according to any of the first to eighth embodiments, wherein the processor executes the inquiry by sending a message via a chatbot.

[0021] A 13th aspect involves the processor performing the steps of exchanging messages between users in a chat room on a messaging service, and sending a message to share a file, including the sender's information regarding the file in the message, which is included in the user information of the user. Processing detailsA step of determining whether processing for the file is necessary based on the text for conveying the intention, a step of inquiring about the processing to a first user who is the sender of the message when the processing for the file is necessary, and a step of executing the processing for the file when an execution instruction for the processing is received from the first user. It is a program for executing these steps.

Advantages of the Invention

[0022] According to the first, the 8 the 13 According to the aspect, in the message exchange, the operability of the file sender can be improved when sending a file.

[0023] According to the second, the 3 According to the aspect, furthermore, when the second user has no access right to the file, the access right to the second user can be granted.

[0024] According to the 4 According to the aspect, furthermore, processing according to the message content can be executed.

[0025] According to the 5 the 6 the 7 According to the aspect, furthermore, processing according to at least any one of the file size, resolution, and file format of the file desired by the second user can be executed.

[0026] According to the 9 the 10 the 11 According to the aspect, furthermore, the processing desired by the second user can be executed.

[0027] According to the 12 According to the aspect, furthermore, the operability of the file operator can be improved in a chat format by a chatbot.

Brief Description of the Drawings

[0028] [Figure 1]This is a system configuration diagram of an embodiment. [Figure 2] This is a functional block diagram of the bot server in the embodiment. [Figure 3] This is a block diagram of the configuration of the bot server in the embodiment. [Figure 4] This is an example screen of the embodiment (part 1). [Figure 5] This is an example screen of the embodiment (part 2). [Figure 6] This is an example screen of the embodiment (part 3). [Figure 7A] This is a schematic diagram (part 1) of the process in the embodiment. [Figure 7B] This is a schematic diagram (part 2) of the process in the embodiment. [Figure 7C] This is a schematic diagram (part 3) of the process in the embodiment. [Figure 8A] This is a schematic diagram (part 4) of the process in the embodiment. [Figure 8B] This is a schematic diagram (part 5) of the process of the embodiment. [Figure 8C] This is a schematic diagram (part 6) of the process of the embodiment. [Figure 9A] This is a schematic diagram (part 7) of the process of the embodiment. [Figure 9B] This is a schematic diagram (part 8) of the process of the embodiment. [Figure 9C] This is a schematic diagram (part 9) of the process in the embodiment. [Figure 10] This is a schematic diagram (10th) of the process of the embodiment. [Figure 11] This is an example screen of the embodiment (part 4). [Figure 12] This is an example screen of the embodiment (No. 5). [Figure 13] This is an example screen of the embodiment (No. 6). [Figure 14] This is an example screen of the embodiment (No. 7). [Figure 15A] This is a schematic diagram (No. 11) of the process of the embodiment. [Figure 15B] This is a schematic diagram (No. 12) of the process of the embodiment. [Figure 16]This is a processing flowchart of the embodiment. [Figure 17] This is a diagram illustrating the rules of the embodiment. [Modes for carrying out the invention]

[0029] The embodiments of the present invention will be described below with reference to the drawings, using a messaging service in which users exchange messages in a chat room as an example.

[0030] Figure 1 shows the overall configuration of a message delivery system that executes a message service in an embodiment. The message delivery system comprises user terminals A (10A) to C (10C), a chat service server 14 on the cloud 12, and a bot server 16. User terminals A (10A) to C (10C) are terminals used by users of the message service, and are information terminals such as smartphones, tablet terminals, and PCs (personal computers). In Figure 1, three terminals, user terminals A (10A), B (10B), and C (10C), are shown, but the number is arbitrary. Users operate user terminals A (10A) to C (10C) to access the chat service server 14 on the cloud 12 and exchange messages with other users and chatbots. In the following, it will be assumed that user A operates user terminal A, user B operates user terminal B, and user C operates user terminal C. User terminals A (10A) to C (10C) and the chat service server 14 are connected via a wired or wireless communication network, enabling data transmission and reception. An example of such a communication network is a public network such as the internet, but a dedicated line may also be used.

[0031] Here, "chatbot" refers to a (personified) software robot program designed to simulate human interaction via voice or text, operating on messaging services. Chatbots work by detecting specific words or phrases from messages entered by users and outputting pre-prepared responses that match them. Some chatbots are operated by messenger service accounts assigned for advertising or commercial purposes by companies or stores, allowing users to enjoy conversations with chatbots in chat rooms through natural messaging and to perform various services on the chatbots.

[0032] The chat service server 14 is a cloud server located on the cloud 12 and is a server that provides chat services. The chat service server 14 consists of one or more server computers. The chat service server 14 performs all processing related to message exchange, such as sending and receiving messages to user terminals A to C, and displaying message exchange screens. In addition to processing message exchanges between two users, the chat service server 14 can form a group of three or more users and process message exchanges within that group (group chat). Furthermore, the chat service server 14 works in cooperation with the bot server 16 to process message exchanges to the chatbot provided by the bot server 16. Message exchanges between users and chatbots include message exchanges between one user and a chatbot, and message exchanges between multiple users and a chatbot.

[0033] Bot server 16 is a server on which a chatbot software robot program that exchanges messages with users is installed and which runs said program.

[0034] The bot server 16 collaborates with the chat service server 14 via a specific API (Application Programming Interface) to exchange messages with users and automatically respond to user messages. The specific API is an API for using the chat service server 14. The format of the API is arbitrary, but for example, it could be a JSON (Javascript Object Notation) API, where JSON data in a specified format is sent to a specific URL of the chat service server 14 via POST or GET, and the result is returned as JSON data.

[0035] Furthermore, in this embodiment, when a user (referred to as the first user) sends a message to another user in the chat room (referred to as the second user) to share a file, the bot server 16 determines, based on user information, whether or not processing is required for the file. Sending a message here includes both when the first user attempts to send a message to the second user and when the first user has already sent a message to the second user. Specifically, this includes both before and after the first user gives a sending instruction (such as pressing the "Send" button or pressing the Enter key) to send a message to the second user. Determining, based on user information, whether or not processing is required for the file when the first user attempts to send a message to the second user means, specifically, determining, based on user information, whether or not processing is required for the file while the first user is creating the message to send to the second user. If it is determined that processing is required for the file, the bot server 16 sends a message to the first user, the message sender, inquiring about the processing. Then, upon receiving an instruction from the first user to execute the processing, the bot server 16 executes the processing on the file.

[0036] User information includes the user information of both the first and second users, as well as user attribute information and user preference information. User attribute information includes information such as which chat rooms the user belongs to and information about file access permissions. The content of messages posted by the first user may also be included in the first user's user information.

[0037] File processing includes granting access rights to files and converting at least one of the following: file size, resolution, or format.

[0038] Figure 2 is a functional block diagram of the bot server 16. The bot server 16 comprises the following functional blocks: API gateway 160, communication unit 161, message receiving unit 162, content analysis unit 163, response message creation unit 164, user information DB (database) 165, group information DB (database) 166, message storage unit 167, and file storage unit 168.

[0039] The communication unit 161 communicates with the chat service server 14. The communication unit 161 communicates with the chat service server 14 via the API gateway 160 and exchanges messages. The communication unit 161 outputs the messages received from the chat service server 14 via the API gateway 160, i.e., messages from user terminals A to C, to the message receiving unit 162. The communication unit 161 also sends the response messages created by the response message creation unit 164 to the chat service server 14 via the API gateway 160, i.e., to user terminals A to C. The communication unit 161 also obtains information about users who use the chat service server 14.

[0040] The message receiving unit 162 receives messages from the communication unit 161 and outputs them to the content analysis unit 163. Messages may include attachments, and may also include text that conveys the sender's intentions regarding those attachments. The message receiving unit 162 sequentially stores the received messages in the message storage unit 167.

[0041] The content analysis unit 163 analyzes the content of the received message and determines whether or not processing is required for any attached files in the message.

[0042] Specifically, if a message contains an attachment, the system determines whether a user other than the message sender, i.e., a second user receiving the message, has access rights to the attachment. It also determines whether the message contains specific text, such as "confirm" or "review." Furthermore, it checks the file size, resolution, and format of the attachment and determines whether these match the recipient user's desired size, resolution, and format. Regarding the file size, resolution, and format of the attachment, instead of the recipient user's desired size, resolution, and format, the system may determine whether the file size is greater than or equal to a predetermined threshold, whether the file resolution is smaller than or equal to a predetermined threshold, or whether the file format is a specific format.

[0043] The method for extracting text from a message and performing syntactic analysis is arbitrary; for example, the input message can be broken down into morphemes, and then nouns, adjectives, verbs, and interrogative pronouns can be extracted as keywords.

[0044] The content analysis unit 163 determines whether or not processing of the attached file is necessary based on these analysis results, and if it determines that processing is necessary, it instructs the response message creation unit 164 to create a response message for the first user who sent the message, and further for the second user who received the message.

[0045] The response message creation unit 164 creates a response message in response to a command from the content analysis unit 163 and sends it via the communication unit 161 to the chat service server 14, i.e., user terminals 10A to 10C.

[0046] When a user terminal sends a reply message in response to a response message created by the response message creation unit 164, the message receiving unit 162 receives the message again, and the content analysis unit 163 analyzes the content of the reply message.

[0047] The content analysis unit 163 determines and executes processing on the attached file according to the content of the reply message from the user terminal to the response message. For example, depending on the content of the reply message to the response message regarding granting access rights to the attached file to a second user, it grants access rights to the attached file to the second user.

[0048] The user information database 165 stores information about users who use the chat service server 14, obtained by the communication unit 161, as a table. User information includes, for example, user ID, information about each user's permissions, each user's desired size, desired resolution, and desired format. The content analysis unit 163 accesses the user information database 165 and retrieves the user information of each user stored therein, more specifically the access permissions of the second user, the second user's desired file size, the second user's desired file resolution, and the second user's desired file format, to determine whether processing of the attached file is necessary.

[0049] In this embodiment, the content of the message is analyzed by the content analysis unit 163, and the analyzed content is stored in the user information DB 165 and can be treated as one of the user information items.

[0050] User information stored in the user information DB 165 can be updated as appropriate in accordance with the processing performed by the content analysis unit 163. For example, if user B is the second user and initially does not have access rights to a certain attachment, and the content analysis unit 163 decides to grant access rights to user B, the information for user B stored in the user information DB 165 will be updated from "no access rights" to "access rights granted".

[0051] The group information DB 166 stores information about chat groups (chat rooms). Specifically, it stores the user IDs of the users belonging to each group (room). The content analysis unit 163 accesses this group information DB 166 to identify the group of users participating in a particular chat room. For example, if the group of users belonging to a chat room consists of user A, user B, and user C, and user A sends a message in this chat room, the content analysis unit 163 identifies user A as the first user, and the other users B and C in the same chat room as second users.

[0052] The message storage unit 167 and the file storage unit 168 store messages and attached files sent from the user terminal, respectively.

[0053] Figure 3 shows a block diagram of the bot server 16. The bot server 16 consists of one or more server computers and includes one or more CPUs 16b, ROM 16c, RAM 16d, communication interface (I / F) 16e, input / output I / F 16f, and storage device 16g.

[0054] One or more CPUs 16b read the bot application stored in ROM 16c or storage device 16g and use RAM 16d as working memory to realize the functionality of a chatbot. That is, they automatically respond to messages from users and create response messages for the user as needed. By executing the bot application, the CPUs 16b realize the message receiving unit 162, content analysis unit 163, response message creation unit 164, and API gateway 160 shown in Figure 2.

[0055] The communication interface 16e handles message exchanges with the chat service server 14.

[0056] The Input / Output I / F16f transmits and receives data to and from input devices such as keyboards and mice, and output devices such as display devices.

[0057] The storage device 16g is composed of non-volatile memory such as an HDD (Hard Disk Drive) or SSD (Solid State Drive). In addition to storing the bot application, the storage device 16g also stores a user information table, a group information table, a message management table, and a file management table. As storage means, the storage device 16g implements the user information DB 165, group information DB 166, message storage unit 167, and file storage unit 168 shown in Figure 2.

[0058] In this embodiment, a software robot program for realizing the chatbot's functionality is executed by the CPU. However, some parts of the chatbot may be implemented by hardware processing instead of program execution.

[0059] Furthermore, the term "processor" refers to a broad category of processors, including general-purpose processors (such as CPUs, Central Processing Units, etc.) and specialized processors (such as GPUs, Graphics Processing Units, ASICs, Application Specific Integrated Circuits, FPGAs, Field Programmable Gate Arrays, programmable logic devices, etc.).

[0060] Furthermore, the operation of the processor may not be performed solely by a single processor, but may also be performed collaboratively by multiple processors located in physically separate locations. The order of each processor operation may also be changed as appropriate.

[0061] Next, the operation of this embodiment will be described in detail using an example of a screen displayed on the user terminal.

[0062] Figure 4 shows screen 20 displayed on the display device of user terminal 10A operated by user A. It is a chat screen of a chat room, and it is assumed that users A and B are participating in that chat room.

[0063] User A operates user terminal 10A to post a message to a participant in the chat room, namely User B. User A, the sender, corresponds to the first user, and User B, the recipient, corresponds to the second user. The screen 20 displays an icon 22 representing User A, for example, "Please leave a review." He posts message 24, and also attaches file 26 to message 24, "Development Plan" Attachment 26 is attached. The size, resolution, and format of attachment 26 can be set by user A.

[0064] The chatbot implemented on the bot server 16 parses the content of the message 24 posted by user A and determines whether or not an attachment 26 exists. If it determines that an attachment 26 exists and that user B needs access to the attachment 26 based on the content of message 24, it accesses the user information DB 165 to retrieve user B's user information and checks whether user B has access rights to the attachment 26.

[0065] Alternatively, regardless of the analysis of the contents of message 24, it may be determined that user B needs access to attachment 26 simply based on the existence of attachment 26. The conditions under which access is deemed necessary are determined by predetermined rules.

[0066] If User B has access rights to attachment 26, the chatbot will not perform any special actions. User B will check User A's message 24 and attachment 26 displayed on the screen of User Terminal 10B, which they are operating, and since they have access rights, they will open attachment 26 without any problems and check its contents.

[0067] On the other hand, if user B does not have access rights to attachment 26, the chatbot will respond to this fact by informing user A that user B does not have access rights to attachment 26, and will post a message to user A asking whether or not to grant access rights to user B. For example, as shown in Figure 5, the chatbot will "The attached document does not have access rights for person B." Do you want to grant access rights to person B? The message 30 is posted. In Figure 5, the icon 28, which is a representation of the chatbot, is displayed on the screen 20 of user A's user terminal 10A, and message 30 is displayed along with this icon 28. Message 30 contains, "yes" "no" A button will appear, and user A can select one of them.

[0068] To explain in accordance with the functional blocks in Figure 2, the content analysis unit 163 determines whether user B has access rights to a specific document, "Development Plan," and if it determines that user B does not, it instructs the response message creation unit 164 to create a response message. The response message creation unit 164, in accordance with the instruction from the content analysis unit 163, "The attached document does not have access rights for person B." Do you want to grant access rights to person B? A response message is created and output to the communication unit 161. The communication unit 161 sends the response message to the user terminal 10A operated by user A via the API gateway 160 and the chat service server. By viewing screen 20 shown in Figure 5, user A can recognize that user B does not have access rights to attachment 26, and by responding to the chatbot's inquiry, user A can easily grant user B access rights to attachment 26.

[0069] In other words, when granting access rights to user B, user A is included in message 30. "yes" Operate the button. The chatbot will respond from user terminal 10A. "yes" In response to the reply, access rights to attachment 26 are granted to user B, and the access rights information for user B stored in user information DB165 is updated from "none" to "yes". Then, a message is posted to user B indicating that access rights have been granted. For example, as shown in Figure 6, the chatbot "I have granted B access rights to the 'Development Plan'." I posted message 32 with the following message:

[0070] To explain again using Figure 2, from user terminal 10A "yes" When the message receiving unit 162 receives the reply, the content analysis unit 163 analyzes the content of the reply, confirms that it is a positive response ("yes"), and updates the access rights information for user B stored in the user information DB 165. It also instructs the response message creation unit 164 to create a response message. The response message creation unit 164 responds to the instruction from the content analysis unit 163, "I have granted B access rights to the 'Development Plan'." A response message is created and output to the communication unit 161. The communication unit 161 sends the response message to the user terminal 10A operated by user A via the API gateway 160 and the chat service server.

[0071] Since it is considered that user A, who posted message 24, should decide whether or not to grant access rights to user B, message 32 posted by the chatbot will only be displayed on user terminal 10A operated by user A, and not on user terminal 10B operated by user B. This means that the granting of access rights to user B will be controlled solely by the message exchange between user A and the chatbot, without user B's involvement. Furthermore, user A does not need to check in advance whether or not user B has access rights before sending message 24, thus improving usability.

[0072] Figures 7A to 7C schematically illustrate the process of granting access rights to user B. These figures show the processing flow between user terminal 10A operated by user A, user terminal 10B operated by user B, and bot server 16 which functions as a chatbot.

[0073] Figure 7A shows a message posted (sent) from user terminal 10A to user terminal 10B, with attachment file 26 attached to the message. If user B does not have access rights to attachment file 26 in the initial state (indicated by an "×" mark), user B cannot open attachment file 26.

[0074] The bot server 16 analyzes the message from the user terminal 10A and, in the message, "Development Plan" The system analyzes whether an attachment 26 is attached. Based on this analysis, it is determined that it is necessary to determine whether user B has access rights. The system then accesses the user information DB 165 to obtain user B's access information and determines whether user B has access rights. More specifically, the bot server 16 accesses the group information DB 166 to identify user A as the first user who sent the message and user B as the second user who received the message. The system then obtains the access information contained in the user information of the identified user B and determines whether or not they have access rights.

[0075] Here, "access rights" refers to access rights to a specific document, including operational rights to that document. Operational rights to a document include "read," "write," "print," and "edit." Therefore, when determining whether or not access rights exist, the determination may be made based on a combination of the message content and the operational rights. Specifically, even if the message content includes "review," and "read" is permitted but "write" and "edit" are not, access rights may still be determined to exist.

[0076] Figure 7B shows the process when user B does not have access rights to attachment 26. The bot server 16 automatically creates a message informing user B that user B does not have access rights and inquiring with user A about granting access rights to user B, and sends it to user terminal 10A. This message is sent only to user terminal 10A and not to user terminal 10B. When user terminal 10A replies that it will grant access rights to user B (replies with "yes"), the bot server 16 accesses user information DB 165 to update user B's access rights and allows user B to access attachment 26. Once user B's access rights are updated, the bot server 16 sends a message to user terminal 10A informing it of this, that is, that user B has been granted access rights.

[0077] Figure 7C shows the state after user B's access rights have been updated by the bot server 16. User terminal 10B can access and open the attached file 26 (in the figure, the "○" indicates that it is accessible), and user B can review the contents of the attached file 26.

[0078] Furthermore, since it takes a certain amount of time from when User A sends a message to User B until User B is granted access rights, User B cannot access attachment 26 during this period. Therefore, when the bot server 16 confirms that User B has attempted to access attachment 26 and that this attempt has been denied, it sends a message to User B. "We are currently adjusting access permissions, please wait." You can also automatically create and send a message like this.

[0079] Figures 7A to 7C illustrate the case where the chat room participants are User A and User B. However, it is also conceivable that in addition to Users A and B, User C may also be a participant in the chat room, and that both User A and User C have the authority to decide whether or not to grant access rights to User B.

[0080] Figures 8A to 8C schematically show the process when there is permission to grant access rights to user C.

[0081] Figure 8A shows a message posted (sent) from user terminal 10A to user terminals 10B and 10C, with attachment file 26 attached to the message. If user B does not have access rights to attachment file 26 in the initial state (indicated by an "×" mark), user B cannot open attachment file 26.

[0082] The bot server 16 analyzes the message from the user terminal 10A and, in the message, "Development Plan" The system analyzes whether an attachment, file 26, is attached. Based on the analysis results, it determines whether users B and C have access rights as second users. The system then accesses user information DB 165 to obtain access information for users B and C and determines whether users B and C have access rights. In this case, it is assumed that user C has access rights, but user B does not. It is also assumed that user C has the authority to decide whether to grant access rights.

[0083] Figure 8B shows the process when user B does not have access rights to attachment 26. The bot server 16 automatically creates a message informing user B that they do not have access rights and inquiring with user A about granting access rights to user B, and sends this message to user terminal 10A. In addition, the bot server 16 automatically creates a message informing user B that they do not have access rights and inquiring with user C to grant access rights to user B, and sends it to user terminal 10C. In other words, it inquires with both user A, the first user, and user C, the second user. Note that this message is not sent to user terminal 10B.

[0084] When user terminal 10A or user terminal C replies to grant access rights to user B (a "yes" reply), bot server 16 accesses user information DB 165 to update user B's access rights and grants user B access to attachment 26. After updating user B's access rights, bot server 16 sends a message to user terminals 10A and C to that effect, that is, to inform user B that access rights have been granted.

[0085] Figure 8C shows the state after user B's access rights have been updated by the bot server 16. User terminal 10B can access and open the attached file 26 (in the figure, the "○" indicates that it is accessible), and user B can review the contents of the attached file 26.

[0086] In Figures 8A to 8C, user terminals 10A and 10C respond to the bot server 16's request for access permission. However, depending on the content of the responses from user terminals 10A and 10C, adjustments may be necessary. That is, possible combinations of responses include: (1) Both user terminal 10A and user terminal 10C are "Yes" (2) User terminal 10A responds with "Yes" or no response, and user terminal 10C responds with "No" or no response. (3) User terminal 10A responds with "No" or no response, and user terminal 10C responds with "Yes" or no response. (4) Both user terminal 10A and user terminal 10C are "No". This is possible. Cases (1) and (4) are not a problem, but adjustments will be necessary in cases (2) and (3).

[0087] Figure 9A shows that the bot server 16 sends messages to user terminals 10A and 10C, and only user terminal 10C receives a message. "yes" This indicates the state of the reply. In this case, the bot server 16 grants access rights to user B in response to the reply from user terminal 10C. User A also, "Please leave a review." Since that message was sent, it is reasonable to assume that granting access rights to user B can be justified unless there are special circumstances.

[0088] On the other hand, Figure 9B shows that the bot server 16 sends messages to user terminals 10A and 10C, and user terminal 10C "no" This indicates the state in which the reply was sent. In this case, bot server 16, "Please leave a review." The user terminal 10A sent the message, and the user terminal 10C responded to it. "no" In response to the reply, a message is sent only to user terminal 10A to inquire whether it is acceptable to deny access rights to user B.

[0089] If user terminal 10A responds to this inquiry with an affirmative answer indicating consent to the denial of access rights, bot server 16 will maintain user B's access rights in their initial state and will not grant access rights. Furthermore, if user terminal 10A responds to the inquiry with an affirmative answer indicating disagreement with the denial of access rights, there will be conflicting responses regarding the granting of access rights to user B. Therefore, bot server 16 should decide whether or not to grant access rights to user B according to a predetermined rule. This decision rule could be, for example, Prioritize User A, the message poster. Prioritize user C, who has access privileges. Access privileges will only be granted if User A and User C agree. And so on.

[0090] Furthermore, it's possible to consider scenarios where the chat room has even more participants. For example, a situation where, in addition to users A, B, and C, user D is also present.

[0091] Figure 10 shows the case where the participants are users A, B, C, and D, and a message is posted (sent) from user terminal 10A to user terminals 10B, 10C, and 10D, with attachment file 26 attached to this message. If user B does not have access rights to attachment file 26 in the initial state, user B will not be able to open attachment file 26.

[0092] The bot server 16 analyzes the message from the user terminal 10A and, in the message, "Development Plan" The system analyzes whether an attachment 26 is attached. Based on the analysis results, it determines whether users B, C, and D have access rights, and accesses the user information DB 165 to obtain the access information for users B, C, and D, and determines whether users B, C, and D have access rights. In this case, it is assumed that users C and D have access rights, but user B does not. It is also assumed that users C and D have the authority to decide whether to grant access rights.

[0093] The bot server 16 automatically creates a message informing user B that they do not have access rights and requests permission to grant access rights to user B, and sends it to user terminals 10A, 10C, and D. This message is not sent to user terminal 10B. In response, user terminal 10A "yes" A reply was received, and from user terminal 10C "no" A reply was received, and from user terminal 10D "no" Let's assume there is a reply. In this case, the bot server 16 decides whether or not to grant access rights to user B according to a predetermined decision rule. For example, the decision rule is: • By majority vote of multiple users If the rule is as follows, then in the example in Figure 10... "no" Since there are many users, bot server 16 follows the decision rule and maintains user B's access rights in their initial state.

[0094] Here, if user B is granted access rights according to the decision rules, user B will not be notified of this; however, if the granting of access rights to user B is denied, user B may be notified of this. For example, "Access to the attachment was denied." This involves automatically creating a message and sending it to user terminal 10B.

[0095] Figure 11 shows another screen 20 displayed on the display device of user terminal 10A operated by user A. It is a chat screen of a chat room, and it is assumed that users A and B are participating in that chat room.

[0096] User A operates user terminal 10A to post a message to a participant in the chat room, namely user B. The screen 20 displays an icon 22 representing user A, and also, for example, "I'll send you the group photo." He posts message 24 with the following attachment: "Group photo" Attachment 26 is attached.

[0097] The chatbot implemented on the bot server 16 analyzes the content of the message 24 posted by user A and determines whether or not an attachment 26 exists. If it determines that an attachment 26 exists and that it is necessary to determine whether or not the size of the attachment 26 is appropriate for user B, it accesses the user information DB 165 to obtain user B's user information and checks whether user B has a desired size for the attachment 26.

[0098] If the desired size for User B's attachment 26 is not found in the user information, the chatbot will not perform the operation.

[0099] On the other hand, if the user information contains a desired size for User B's attachment 26, the chatbot compares the size of attachment 26 with User B's desired size. If User B's desired size matches the size of attachment 26, the chatbot does not perform any processing. User B checks User A's message 24 and attachment 26 displayed on the screen of the user terminal 10B that User B is operating, and opens attachment 26 to check its contents.

[0100] If User B's desired size does not match the size of attachment 26, the chatbot will notify User A that the size of attachment 26 is inappropriate and post a message asking for permission to change the size of attachment 26. For example, (Size of attached file 26) > (Desired size for User B) In that case, the chatbot will, as shown in Figure 11, "The group photo is too large; would you like to reduce its size?" The message 34 is posted. In Figure 11, the icon 28, which is a representation of the chatbot, is displayed on the screen 20 of user A's user terminal 10A, and message 34 is displayed along with this icon 28. Message 34 contains, "yes" "no" A button will appear, and user A can select one of them.

[0101] Note that this message 34 is displayed only on user terminal 10A operated by user A, and not on user terminal 10B operated by user B.

[0102] By viewing screen 20 shown in Figure 11, user A can recognize that the size of the attached file 26 is inappropriate, and by responding to the inquiry from the chatbot, user B can easily change the size of the attached file 26 to a size that is appropriate and desired for user B.

[0103] In other words, User A is included in message 34 "yes" When the button is pressed, the chatbot will respond to the user terminal 10A. "yes" In response to the reply, the size of attachment 26 is converted from its initial size to the size requested by user B. Then, a message is posted indicating that the size conversion has been completed. For example, the chatbot: "The size of the attached file has been reduced." He posted the following message.

[0104] User A does not need to know User B's desired size in advance, and can reliably send attachment 26 to User B.

[0105] The chatbot posted message 34 only to user terminal 10A, but it may also post it to user terminal 10B if necessary so that user B can see it. Furthermore, the chatbot... (Size of attached file 26) < (Desired size for User B) In that case, in addition to not executing the process, "The group photo is too small. Would you like to enlarge it?" You can also post a message saying "You can change the size."

[0106] Furthermore, it is conceivable that in addition to users A and B, user C may be present in the chat room, and that the desired size of attachment 26 attached to message 24 posted by user A may differ between user B and user C. In this case as well, the chatbot will decide whether or not to perform the size conversion process according to predetermined rules. Specifically, • Convert size to meet stricter size requirements. • Convert size to match both size requirements. • Resize each image individually to meet specific size requirements. And so on.

[0107] For example, the chatbot's desired size for user B is Bs, the desired size for user C is Cs, and the size of attachment 26 is As. As > Bs > Cs Therefore, to meet the strictest condition, Cs, convert the size of attachment 26 from As to Cs and send it to users B and C.

[0108] A rule could also be adopted to individually convert the size of each item if there are a certain number of participants in the chat room and a certain number of differences in desired sizes.

[0109] For example, if there are three or more second-party users and three or more different desired sizes, the system will convert the size for each user individually.

[0110] In the example in Figure 11, if the desired size is not found in the user information of the second user, no processing is performed. However, if the desired size is not found, the size may be compared to a predetermined threshold, and the decision to perform / not perform the processing may be made based on the comparison result. Specifically, if user A and user B are present in the chat room, and the desired size for user B's attachment 26 is not found in the user information, the chatbot will not perform the processing, but instead compare the size of attachment 26 to a predetermined threshold. (Size of attached file 26) < threshold If so, the process will not be executed. (Size of attached file 26) ≥ threshold If so, "The group photo is too large; would you like to reduce its size?" He posts message 34 with the following message:

[0111] Figure 12 shows yet another screen 20 displayed on the display device of user terminal 10A operated by user A. This is a chat screen of a chat room, and it is assumed that users A, B, and C are participating in this chat room.

[0112] User A operates user terminal 10A to post a message to the chat room participants, namely users B and C. The screen 20 displays an icon 22 representing user A, and also, for example, "Please leave a review." He posts message 24 with the following attachment: "Development Plan" Attachment 26 is attached.

[0113] The chatbot analyzes the content of message 24 posted by user A and determines whether or not an attachment 26 exists. If it determines that an attachment 26 exists and that it is necessary to confirm from the content of message 24 that users B and C have accessed and reviewed the attachment 26, "Have you reviewed the development plan?" Create message 36 and post it to user terminal 10B operated by user B and user terminal 10C operated by user C. Message 36 contains: "yes" "no" A button will appear, and users B and C can select either of them.

[0114] Figure 13 shows that both User B and User C access attachment 26 and view its contents, and respond to message 36. "yes" This is screen 20 of user terminal 10A when a button is operated. The chatbot responds to replies from users B and C. "Mr. B has reviewed the development plan." Message 38, and "Ms. C has reviewed the development plan." Message 39 is posted to user terminal 10A.

[0115] By viewing these messages 38 and 39, User A can confirm that Users B and C have reviewed attachment 26.

[0116] Figure 14 shows yet another screen 20 displayed on the display device of user terminal 10A operated by user A. This is a chat screen of a chat room, and it is assumed that users A, B, and C are participating in this chat room.

[0117] User A operates user terminal 10A to post a message to the chat room participants, namely users B and C. The screen 20 displays an icon 22 representing user A, and also, for example, "I'll send you the group photo." He posts message 24 with the following attachment: "Group photo" Attachment 26 is attached.

[0118] The chatbot analyzes the content of message 24 posted by user A and determines whether or not an attachment 26 exists. If it determines that an attachment 26 exists and that the content of message 24 indicates the need to determine whether the resolution of the attachment 26 is appropriate for users B and C, it accesses user information DB 165 to retrieve user information for users B and C and checks whether users B and C have a desired resolution for the attachment 26.

[0119] If the desired resolution for attachment 26 for users B and C is not present in the user information, the chatbot will not perform any processing.

[0120] On the other hand, if the user information contains desired resolutions for attachment 26 from users B and C, the chatbot compares the resolution of attachment 26 with the desired resolutions of users B and C.

[0121] If the desired resolutions of users B and C match the resolution of attached file 26, the chatbot will not perform any processing. Users B and C will check user A's message 24 and attached file 26 displayed on the screens of their respective user terminals 10B and 10C, and then open attached file 26 to check its contents.

[0122] If the desired resolution of either User B or User C does not match the resolution of Attachment 26, the chatbot will notify User A that the resolution of Attachment 26 is inappropriate and post a message asking for a change in the resolution of Attachment 26. For example, (Resolution of attached file 26) < (User B's desired resolution) In that case, the chatbot will, as shown in Figure 14, "Would you like to increase the resolution of the group photo?" Message 40 is posted. In Figure 14, the screen 20 of user A's user terminal 10A displays an icon 28, which is a representation of the chatbot, and message 40 is displayed along with this icon 28. Message 40 contains, "yes" "no" A button will appear, and user A can select one of them.

[0123] Note that this message 40 is only displayed on user terminal 10A operated by user A, and is not displayed on user terminals 10B and 10C. By viewing the screen 20 shown in Figure 14, user A can recognize that the resolution of the attached file 26 is inappropriate, and by responding to the chatbot's inquiry, can easily change the resolution of the attached file 26 to the resolution desired by user B.

[0124] In other words, User A is included in message 40 "yes" When the button is pressed, the chatbot will respond to the user terminal 10A. "yes" In response to the reply, the resolution of attached file 26 is converted from the initial resolution to the resolution desired by user B. Then, a message is posted indicating that the resolution has been converted. For example, the chatbot: "I've increased the resolution of the attached file." He posted the following message.

[0125] Furthermore, if User C's desired resolution matches the resolution of attached file 26, the chatbot will maintain the initial resolution of attached file 26.

[0126] User A does not need to know the desired resolutions of Users B and C in advance, and can reliably send the attached file 26 to Users B and C.

[0127] In the example above, for user A who posted message 24 "Would you like to increase the resolution of the group photo?" The user is sending message 40 to inquire about this, but it would also be acceptable to send message 40 to user B or user C, who are recipients of message 24, to inquire about this.

[0128] Figures 15A and 15B schematically illustrate the control of resolution conversion for the attached file 26 in this case. These figures show the processing flow between user terminal 10A operated by user A, user terminal 10B operated by user B, user terminal 10C operated by user C, and bot server 16 which functions as a chatbot.

[0129] Based on the analysis of the message content from user terminal 10A and the presence or absence of an attached file 26, the bot server 16 determines that the desired resolutions of users B and C are required. It then accesses the user information DB 165 to obtain the desired resolution information contained in the user information of users B and C. The bot server then compares the resolution of the attached file 26 with the obtained desired resolutions of users B and C. (Resolution of attached file 26) = (User B's desired resolution) and, (Resolution of attached file 26) = (User C's desired resolution) In that case, bot server 16 will not perform any special processing. Note that "equal resolution" means that they are equal within a predetermined tolerance range, and does not necessarily mean that they are strictly equal.

[0130] Also, (resolution of attached file 26) = (desired resolution of User B) However, (Resolution of attached file 26) ≠ (User C's desired resolution) If so, the bot server 16 posts a message to the user terminal 10C requesting a resolution conversion.

[0131] Also, (resolution of attached file 26) = (desired resolution of user C) However, (Resolution of attached file 26) ≠ (User B's desired resolution) If so, the bot server 16 posts a message to the user terminal 10B requesting a resolution conversion.

[0132] Also, (resolution of attached file 26) ≠ (desired resolution of User B) and, (Resolution of attached file 26) ≠ (User C's desired resolution) If so, the bot server 16 posts messages to user terminals 10B and 10C inquiring about resolution conversion.

[0133] Figure 15A shows the process when the resolution of attached file 26 is R, the desired resolution of user B is X, and the desired resolution of user C is Y. R≠X≠Y Therefore, the bot server 16 posts messages to user terminals 10B and 10C inquiring about resolution conversion.

[0134] User B and User C responded to the inquiry "yes" "no" It will reply with one of the following. Bot server 16 will respond to the replies from user B and user C. "yes" In response to the reply, convert the resolution of attachment 26. "no" In response to the reply, the resolution of attachment 26 will be kept at its default setting.

[0135] Figure 15B shows another process when the resolution of attached file 26 is R, the desired resolution of user B is X, and the desired resolution of user C is Y. R≠X≠Y Therefore, the bot server 16 posts a message to the user terminal 10A requesting a resolution conversion.

[0136] User A responded to the inquiry "yes" "no" It will reply with one of the following. Bot server 16 will respond to the reply from user A, "yes" In response to the reply, convert the resolution of attachment 26. "no" In response to the reply, the resolution of attachment 26 will be kept at its default setting.

[0137] Figure 15A shows a query to the recipient of message 24, while Figure 15B shows a query to the sender of message 24. The advantage of querying the recipient is that, if the recipient is dissatisfied with the image quality of the attached file 26 because its resolution differs from the desired resolution, the sender of message 24 does not need to take any further action, making it more efficient. Also, if the desired resolution differs for each receiving user, resulting in multiple resolution-converted attached files 26 being created, the receiving side can handle the processing efficiently.

[0138] As shown in Figure 15A, it is possible to arbitrarily decide whether to query the receiving side or the sending side as shown in Figure 15B, or the chatbot may automatically switch between the two. Specifically, • If multiple resolution-converted attachments (26) are created because each user has a different desired resolution, please contact the recipient. • If all users have the same desired resolution, contact the sender. And so on.

[0139] Furthermore, regarding file resolution, similar to file size, instead of comparing the resolution of attached file 26 to the resolution desired by the second user, it may be compared to a predetermined threshold, and the necessity of processing may be determined based on the comparison result.

[0140] Figure 16 shows the processing flowchart of this embodiment. First, user A operates user terminal 10A to post a message (S101).

[0141] The chatbot determines whether or not a file is attached to the message posted by user A (S102). If no file is attached, it skips the process described below (NO in S102).

[0142] If a file is attached (YES in S102), the system accesses the user information DB165 to retrieve user information (S103) and determines whether processing of the attached file is necessary according to predetermined rules (S104). More specifically, the determination is made according to predetermined rules based on the analysis results of the content of the posted message and the size and resolution of the attached file. For example, regarding access rights, the system determines whether access rights exist according to the rule "inquire about granting access rights if any of the receiving users do not have access rights," and determines that processing of the file is necessary if there are users without access rights. If processing of the file is not necessary, the processing described later is skipped (NO in S104).

[0143] If processing is required for the file (YES in S104), the chatbot determines the content of its inquiry and the recipient of the inquiry according to the rules (S105), and the chatbot posts the inquiry message (S106). For example, if user B does not have access rights to the attached file, the chatbot will post a message requesting access rights for user B, designating user A as the recipient.

[0144] When a user responds to an inquiry message from the chatbot (S107), the chatbot determines what to do with the file based on that response (S108) and then executes the process on the file (S109). For example, if user A responds "yes" In that case, the chatbot will grant user B access rights to the attachment, update the user information in user information DB165, and post a message to user A informing them that user B has been granted access rights.

[0145] Figure 17 shows an example of the rules for determining whether or not a file needs to be processed. For each type of processing, the conditions for deciding whether to execute the processing and the content of the chatbot's inquiry are defined.

[0146] If the type of process is "Grant access rights," the condition for executing the process is "If there is at least one user in the chat who does not have access rights," and the chatbot's inquiry is "Ask the poster whether or not to grant access rights to that user." Alternatively, the chatbot's inquiry could be "Ask the poster and the user authorized to grant access rights whether or not to grant access rights," and an additional rule could be "The decision on granting access rights will be made by a majority vote of the users."

[0147] Furthermore, if the processing type is "Viewer Verification," the condition for deciding whether to execute the process is "if the poster's message contains words such as 'verification' or 'review'," and the chatbot's inquiry is "to ask whether someone other than the poster has verified it."

[0148] Furthermore, if the processing type is "image processing related," the conditions for deciding whether to execute the processing are: "If the file size exceeds a predetermined threshold" "If the file size does not match the desired size" "If the file resolution is below a predetermined threshold" "If the file resolution does not match the desired resolution" The inquiry is as follows: "Contact the poster whether or not they want to resize the image." "Contact someone other than the poster whether or not they want to change the resolution." That is the case.

[0149] Please note that the contact point differs depending on whether the file size exceeds a predetermined threshold or the file resolution falls below a predetermined threshold. This is because, in the latter case, it takes into account the possibility that there may be users other than the poster, i.e., on the receiving end, who would accept a resolution below the threshold.

[0150] Furthermore, if the processing type is "format conversion," the condition for deciding whether to execute the process is "if the file is in a specific format," and the query content is "ask the poster whether or not to convert the format."

[0151] Although embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications are possible.

[0152] For example, with respect to the rule shown in Figure 17, if there are multiple processes that satisfy the execution decision conditions, the chatbot may decide which process to execute based on a pre-configured priority.

[0153] Specifically, if there is at least one user in the chat who does not have access rights, and the file size exceeds a predetermined threshold, and the priority of the former execution decision condition is set higher, the system will execute a process to ask the poster whether or not to grant access rights to that user. Of course, if access rights are granted after the execution of this process, the system may then immediately execute a process to ask about the file size. [Explanation of Symbols]

[0154] 10A, 10B, 10C User terminals, 12 Cloud, 14 Chat service server, 16 Bot server, 16b CPU, 16c ROM, 16d RAM, 16e Communication I / F, 16f Input / Output I / F, 16g Storage device.

Claims

1. A means for obtaining user information of users who exchange messages in a chat room on a messaging service, Processor and The processor is equipped with the following, and by executing a program, When sending a message to share a file, it is determined whether or not processing is necessary for the file based on the text in the message content, which is included in the user information and conveys the sender's intention to process the file. If it is determined that processing is required for the aforementioned file, the first user, who is the sender of the message, is inquired about the processing. When the system receives an instruction from the first user to execute the process, it executes the process on the file. Message delivery system.

2. The user information refers to whether the second user who will receive the message has access rights to the file. If the processor determines that the second user does not have access rights to the file, it queries the first user to ask whether or not to grant access rights to the second user. The message provision system according to claim 1.

3. The processor queries only the first user whether or not to grant the access rights, and does not query the second user. The message provision system according to claim 2.

4. The processor, when the message content includes wording indicating confirmation, queries the second user, who is the recipient of the message, to ask whether or not the file has been confirmed. The message provision system according to claim 1.

5. The user information further includes at least one of the file size, resolution, and file format of the file desired by the second user who will receive the message. The processor queries whether to convert at least one of the file size, resolution, and file format of the file if at least one of the file size, resolution, and file format of the file does not match the file size, resolution, and file format desired by the second user. The message provision system according to claim 1.

6. The user information further includes at least one of the file size and resolution of the file desired by the second user who will receive the message. The processor queries whether to convert at least one of the file size and / or resolution of the file when the file size of the file is greater than or equal to a threshold, or when the resolution of the file is less than a threshold. The message provision system according to claim 1.

7. The processor queries the first user and the second user. A message delivery system according to any one of claims 5 or 6.

8. A means for obtaining user information of users who exchange messages in a chat room on a messaging service, Processor and The processor is equipped with the following, and by executing a program, When sending a message to share a file, it is determined whether or not processing is necessary for the file based on the text in the message that conveys the sender's intention regarding the file, which is included in the user information. If it is determined that processing is required for the aforementioned file, the system selectively switches between the first user, who is the sender of the message, and the second user, who is the recipient of the message, depending on the type of processing, and inquires about the processing. When an instruction to execute the aforementioned process is received, the process is executed on the aforementioned file. Message delivery system.

9. A means for obtaining user information of users who exchange messages in a chat room on a messaging service, Processor and The processor is equipped with the following, and by executing a program, When sending a message to share a file, it is determined whether or not processing is required for the file based on the user information. If it is determined that processing is required for the aforementioned file, the system selectively switches between the first user, who is the sender of the message, and the second user, who is the recipient of the message, depending on the type of processing, and inquires about the processing. When an instruction to execute the above process is received, the above process is executed on the file. The processor queries the first user when there is only one type of processing, and queries the second user when there are multiple types of processing. Message delivery system.

10. The user information is at least one of the file size, resolution, and file format of the file desired by the second user. The processor queries the second user when at least one of the file size, resolution, and file format of the file does not match the file size, resolution, and file format desired by the second user, and when at least one of the file sizes, resolutions, and file formats of the files desired by multiple second users differs from each other, resulting in multiple types of processing. The message provision system according to claim 9.

11. The user information is at least one of the file size, resolution, and file format of the file desired by the second user. The processor queries the first user when at least one of the file size, resolution, and file format of the file does not match the file size, resolution, and file format desired by the second user, and at least one of the file size, resolution, and file format of the files desired by multiple second users is the same, and therefore the type of processing is single. The message provision system according to claim 9.

12. The processor executes the inquiry by sending a message via a chatbot. A message delivery system according to any one of claims 1 or 8.

13. In the processor, The steps involved in exchanging messages between users in a chat room on a messaging service, When sending a message to share a file, the steps include determining whether or not processing is necessary for the file based on the text in the message that conveys the sender's intention regarding the file, which is included in the user information of the user; If processing is required for the aforementioned file, the first user who sent the message is asked about the processing; When an instruction to execute the process is received from the first user, the process is executed on the file, A program that executes the command.

Images