Message processing methods and apparatuses, and related device

Abstract

Disclosed in the embodiments of the present application are message processing methods and apparatuses, and a related device, which are applicable to the technical field of data processing. A method comprises: displaying, on a session page, a message processing control for a target session message, wherein the target session message is a message selected from among session messages on the session page; in response to a trigger operation for the message processing control, displaying N service programs matching the message data type of the target session message, wherein N is a positive integer, and each of the N service programs is a sub-program that relies on a client to run; in response to a trigger operation for a target service program, displaying a message processing page of the target service program; and on the message processing page, performing message processing on the target session message. By using the embodiments of the present application, an improvement in the flexibility and convenience of message processing performed on a session message by means of a service program is facilitated.

Description

Message processing methods, devices and related equipment

[0001] This application claims priority to Chinese Patent Application No. 2025101024054, filed on January 21, 2025, entitled “Message Processing Method, Apparatus and Related Equipment”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of data processing technology, and in particular to message processing methods, apparatus and related equipment. Background Technology

[0003] Currently, for a business object (such as user U1) on a session page, if user U1 needs to process data through a certain mini-program, user U1 must first exit the session page on their terminal device to display the session list page. Then, user U1 can search for mini-programs on the session list page, which will display a search interface for mini-programs on the terminal device. This means that user U1 can then search for the mini-program (such as mini-program CX1) using keywords on this search interface. The search results page on the terminal device will then display all the search results found using those keywords. Finally, user U1 can select the mini-program (such as mini-program CX1) from these search results to process the data.

[0004] However, the inventors discovered in practice that existing methods of searching for mini-programs require closing the session page before further searching for mini-programs within the session list. This means that finding mini-programs that match the user's U1 needs takes a considerable amount of time, resulting in low data processing efficiency. Furthermore, when subsequent keyword searches yield mini-programs for business processing, it's impossible to directly process session messages (e.g., images, text) within the session page of the searched mini-programs, thus reducing the flexibility and convenience of processing session messages through mini-programs. Summary of the Invention

[0005] This application provides a message processing method, apparatus, and related devices that can trigger a session message on a session page to display a business program that matches the message data type of the session message. This allows for quick access to the business program on the session page, improving the flexibility and convenience of message processing through the business program.

[0006] This application provides a message processing method, executed by a terminal device running a client, comprising:

[0007] Display message handling controls for the target session message on the session page; the target session message is the message selected from the session messages on the session page.

[0008] In response to a trigger operation on the message processing control, N business programs that match the message data type of the target session message are displayed, where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the N business programs include the target business program used to process the target session message;

[0009] In response to a triggered operation on the target business application, display the message processing page of the target business application;

[0010] Process the target session messages on the message processing page.

[0011] This application provides a message processing method, executed by a first server corresponding to a client, comprising:

[0012] Receive a program matching request for a target session message from a terminal device running a client. Based on the program matching request, obtain N business programs that match the message data type of the target session message; N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the target session message is the message selected from the session messages on the session page.

[0013] Obtain the program association information for N business programs; the program association information includes the program description information and program access path information of the business programs;

[0014] The program association information of N business programs is returned to the terminal device, so that the terminal device can display the N business programs that match the message data type of the target session message based on the program description information of the N business programs. In response to the trigger operation for the target business program among the N business programs, the terminal device accesses the message processing page of the target business program based on the program access path information of the target business program, and performs message processing on the target session message on the message processing page.

[0015] One embodiment of this application provides a message processing apparatus, which operates on a terminal device, the terminal device running a client, including:

[0016] The control display module is used to display message processing controls for a target session message on the session page; the target session message is a message selected from the session messages on the session page.

[0017] The program display module is used to respond to the trigger operation of the message processing control and display N business programs that match the message data type of the target session message, where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the N business programs include the target business program for message processing of the target session message;

[0018] The program triggering module is used to respond to triggering operations on the target business program and display the message processing page of the target business program;

[0019] The message processing module is used to process target session messages on the message processing page.

[0020] One embodiment of this application provides a message processing apparatus, which operates on a first server corresponding to a client, including:

[0021] The program matching module is used to receive program matching requests for target session messages sent by terminal devices running clients, and to obtain N business programs that match the message data type of the target session message based on the program matching request; N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the target session message is a message selected from the session messages on the session page;

[0022] The association information acquisition module is used to acquire the program association information of N business programs; the program association information includes the program description information and program access path information of the business programs.

[0023] The information return module is used to return the program association information of N business programs to the terminal device, so that the terminal device can display the N business programs that match the message data type of the target session message based on the program description information of the N business programs. In response to the trigger operation of the target business program among the N business programs, the terminal device can access the message processing page of the target business program based on the program access path information of the target business program, and perform message processing on the target session message in the message processing page.

[0024] One aspect of this application provides a computer-readable storage medium storing a computer program adapted to be loaded and executed by a processor, so that a computer device having the processor performs the method provided in this application.

[0025] One embodiment of this application provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method provided in this application embodiment.

[0026] In this embodiment, a terminal device running a client can display message processing controls for a target session message on the session page. The target session message refers to the session message currently selected by the user that requires message processing. For example, the currently selected session message can specifically refer to the message selected from the session messages displayed on the session page. Furthermore, in response to a trigger operation on the message processing controls, the terminal device can intelligently display N business programs that match the message data type of the target session message. It should be understood that each of these N business programs is a subroutine that depends on the client for execution; that is, these N business programs can be equivalently considered as N intelligently matched mini-programs. In this way, for the user, N available mini-programs can be intelligently and conveniently provided without manual program searching, allowing the user to quickly select the target mini-program (i.e., the target business program selected from the N business programs) from these N mini-programs to process the currently selected session message (i.e., the target session message). In other words, the terminal device can respond to a trigger operation on a target business program among these N business programs, access that target business program, and process the target session message on the message processing page of that target business program. This allows the data processing results obtained from processing the target session message to be subsequently displayed or shown to the user within the message processing business. Based on this, the terminal device can directly display all business programs that might meet the user's needs on the session page without requiring manual program search. This allows the user to more quickly and conveniently view a richer and more diverse range of business programs available for processing the selected target session message from the visually presented business programs on the session page. In this way, the user can flexibly select the business program needed to process conversation messages from the N business programs visually presented on the conversation page according to their own needs. This means that the user no longer needs to manually search for programs (e.g., exiting the conversation page and then searching for business programs). The terminal device can intelligently adapt the program based on the message data type of the target conversation message selected on the conversation page, thus quickly helping the user find the target business program that best suits their needs from among the multiple adapted business programs. This not only improves the flexibility and convenience of processing the currently selected conversation message (i.e., the target conversation message) through the target business program, but also greatly improves the efficiency of message processing. Attached Figure Description

[0027] Figure 1 is a schematic diagram of the structure of a data processing system provided in an embodiment of this application;

[0028] Figure 2 is a schematic diagram of a message processing method provided in an embodiment of this application;

[0029] Figure 3 is a flowchart illustrating a message processing method provided in an embodiment of this application;

[0030] Figure 4 is a schematic diagram of the effect of a first type of session page provided in an embodiment of this application;

[0031] Figure 5 is a schematic diagram of the effect of a second type of conversation page provided in an embodiment of this application;

[0032] Figure 6 is a schematic diagram illustrating the effect of displaying a message association area according to an embodiment of this application;

[0033] Figure 7 is a schematic diagram of the effect of displaying a second type of session page provided in an embodiment of this application;

[0034] Figure 8 is a schematic diagram illustrating the effect of a business program display method provided in an embodiment of this application;

[0035] Figure 9 is a flowchart illustrating a message processing procedure provided in an embodiment of this application;

[0036] Figure 10 is a flowchart illustrating another message processing procedure provided in an embodiment of this application;

[0037] Figure 11 is a schematic flowchart of another message processing procedure provided in an embodiment of this application;

[0038] Figure 12 is a schematic diagram illustrating the effect of result data sharing provided in an embodiment of this application.

[0039] Figure 13 is a product schematic diagram of a message processing process provided in an embodiment of this application;

[0040] Figure 14 is a flowchart illustrating a message processing method provided in an embodiment of this application;

[0041] Figure 15 is a schematic diagram of a data type matching process provided in an embodiment of this application;

[0042] Figure 16 is a flowchart illustrating a business procedure determination provided in an embodiment of this application;

[0043] Figure 17 is an interactive flowchart of a message processing method provided in an embodiment of this application;

[0044] Figure 18 is a schematic diagram of a message processing flow provided in an embodiment of this application;

[0045] Figure 19 is a timing interaction diagram of a message processing method provided in an embodiment of this application;

[0046] Figure 20 is a schematic diagram of the structure of a message processing device provided in an embodiment of this application;

[0047] Figure 21 is a schematic diagram of a message processing device provided in an embodiment of this application;

[0048] Figure 22 is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0049] The concepts of relevant technical terms used in the embodiments of this application will be explained below:

[0050] 1. Conversation messages refer to messages displayed on the conversation page. In this embodiment of the application, conversation messages specifically refer to messages visually presented on the conversation page in conversation scenarios such as group chats or one-on-one chats.

[0051] For example, a conversation message can specifically be a message sent and / or received by a user (also known as a business object or operation object) with a message data type of at least one of the following types: text data type, image data type, voice data type, video data type, file data type, and link data type, etc. It is understood that, in this embodiment, the message data type can refer to the data type of the message content in the conversation message. For example, if the message content in the conversation message is a file, then the message data type of the conversation message can be a file data type; or, for example, if the message content in the conversation message is text, then the message data type of the conversation message can be a text data type.

[0052] Furthermore, for ease of distinction, in this application embodiment, one or more messages selected from the session messages displayed on the session page that require message processing can be collectively referred to as target session messages.

[0053] Second, a client refers to an application that provides local services to users (also known as business objects or operation objects).

[0054] For example, in an instant messaging scenario, the client running on the terminal device can specifically be an instant messaging client (e.g., a social client) used for conversations.

[0055] Third, business programs refer to subroutines that depend on the client to run, or mini-programs or lightweight programs that run on the client. Specifically, a mini-program can refer to another application that can be used directly without downloading or installing it.

[0056] In this embodiment, users do not need to manually search for programs after exiting the session page. Instead, based on one or more messages (i.e., target session messages) selected by the user on the session page, the system quickly finds N business programs that match the message data type of the currently selected one or more messages (i.e., target session messages). In this way, users can flexibly and quickly determine the target business program from these N intelligently provided business programs according to their own search needs, and then quickly achieve the timeliness and convenience of message processing for the currently selected one or more messages (i.e., target session messages) through the target business program.

[0057] Please refer to Figure 1, which is a schematic diagram of a data processing system provided in an embodiment of this application. As shown in Figure 1, the data processing system may include terminal devices (such as terminal devices 11a, 12a, and 13a) and servers (such as servers 100a and 101a). It is understood that the number of terminal devices and servers in Figure 1 is merely illustrative, and any number of terminal devices and servers may be used depending on the implementation requirements. The terminal devices (such as devices 11a, 12a, and 13a) can communicate with the servers through a network (i.e., through a medium that provides a communication link via wired, wireless communication links, or fiber optic cables) to transmit data.

[0058] It is understood that a client can run on a terminal device (such as terminal device 12a), which can be a program providing local services to users (also known as business objects or operation objects). Server 100a can be the server corresponding to the client, and a program running on server 100a can provide resources, service data, and other services to the client. It is understood that the client running on the terminal device can also be called an application client, business client, etc. For example, the client running on the terminal device can be an instant messaging client (e.g., a social client) for conducting conversations, and at least one subroutine (such as a mini-program or any lightweight program that depends on the client to run) can run in this instant messaging client. A mini-program can refer to an application that can be used directly without downloading and installation, and it can depend on the client to run. Server 100a can be the server corresponding to the instant messaging client to provide instant messaging services to the client. Server 101a can be the server corresponding to a mini-program (such as program CX1) that depends on the client to run. It can be understood that server 100a and server 101a can interact with each other. For example, when a user accesses mini-program CX1 through an account logged in on the client (such as account Z1), the user can authorize the terminal device to access mini-program CX1 through the account logged in on the client (such as account Z1). In this way, server 101a corresponding to mini-program CX1 can obtain account information of account Z1 from server 100a corresponding to the client. Server 100a and server 101a can be two independent servers, or different server modules within the same server; this is not limited here.

[0059] For example, in some instant messaging scenarios, user U1 can send a session message to user U2 through client KD1 in a terminal device (such as terminal device 11a). Specifically, client KD1 can respond to user U1's message sending operation by sending session message X1 to a server (such as server 100a), so that server 100a forwards session message X1 to the terminal device corresponding to user U2 (such as terminal device 12a), so that the session message can be displayed in client KD2 running in terminal device 12a. In addition, user U1 can access a mini-program (such as mini-program CX1) that depends on client KD1 through client KD1. Specifically, client KD1 can obtain the access path information of mini-program CX1 from server 100a, and then client KD1 can access mini-program CX1 based on the access path information. Furthermore, mini-program CX1 in terminal device 11a can interact with server 101a corresponding to mini-program CX1 to realize the corresponding message processing of session messages through mini-program CX1.

[0060] It is understood that terminal devices (such as terminal device 11a and / or terminal device 12a mentioned above) may include, but are not limited to, mobile phones, computers, smart voice interaction devices, smart home appliances, vehicle terminals, aircraft, smart speakers, etc., without limitation. The server 100a may be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms, without limitation.

[0061] Please refer to Figure 2, which is a schematic diagram of a message processing method provided in an embodiment of this application. As shown in Figure 2, when a client (e.g., the instant messaging client described above) is running in the terminal device 22a, the client (e.g., the instant messaging client described above) can be used to display page 201a shown in Figure 2. For example, page 201a can be a session page displayed on the client (e.g., the instant messaging client described above). For example, as shown in Figure 2, page 201a can be a session page when account Z1 and account Z2 are having a conversation. The business object corresponding to the terminal device 22a shown in Figure 2 can be an object that logs in to the client using account Z1. In this way, the business object corresponding to account Z1 can perform a message triggering operation on the session message 211a on page 201a (such as long-pressing the session message 211a with the data message type of file data as shown in Figure 2). At this time, the client running on the terminal device 22a can display the message processing control for the session message 211a in the form of a pop-up window on page 201a (as shown in Figure 2, the control 212a used to indicate "open" the mini-program). Then, the user can be provided with a more convenient message flow link through the open control 212a. For example, the message flow link can help the user quickly transfer one or more session messages selected on page 201a to the mini-program that matches the user's needs for message processing.

[0062] At this time, the session message 211a is the target session message selected by the business object corresponding to account Z1 from page 201a for message processing. As shown in Figure 2, the message processing here may specifically include uploading the file indicated by the session message 211a to the cloud for file storage via a business program (i.e., the target business program, for example, a file upload applet) that matches the message data type (e.g., file data type) of the session message 211a. This cloud storage can specifically refer to a cloud server in a cloud server cluster. In one implementation, the cloud server used for file storage can be the server corresponding to the target business program (e.g., the file upload applet) (e.g., server 101a mentioned above). The file here specifically refers to the message content in the session message 211a.

[0063] Furthermore, in response to a trigger operation on control 212a, the terminal device displays a business program (i.e., step S221a as shown in Figure 2), for example, the business program can be displayed on page 201a. It should be understood that the business program displayed on page 201a can specifically be N business programs matching the message data type of session message 211a. For example, these N business programs can be programs CX1 and CX2 as shown in Figure 2. Each of these N business programs is a subroutine that depends on the client for execution. A subroutine can refer to a small program that depends on the client for execution or any lightweight application (such as a decentralized application), without limitation here. The message data type can refer to the data type of the message content in the session message, for example, the message data type can be text data type, image data type, file data type, etc., without limitation here. Specifically, in response to the trigger operation on control 212a, the terminal device sends a program matching request to the server 100a (i.e., step S221b shown in FIG2). The program matching request can be a request to obtain a business program that matches the message data type of the target session message. The server 100a can determine N business programs that match the message data type of the target session message based on the program matching request, and obtain the program association information of the N business programs. The program association information includes the program description information of the business program. Then, the server 100a returns the program association information of the N business programs to the terminal device 22a (i.e., step S221c shown in FIG2). Thus, the terminal device 22a can display the business program based on the program description information. For example, in the embodiments of this application, when displaying business programs, a corresponding program access entry can be configured for each business program based on the program description information of each business program, so as to visually present the program access entry corresponding to each business program to the user. For example, as shown in Figure 2, the program access entry for program CX1 can be entry 213a. The program description information displayed in the program access entry (i.e., entry 213a) of program CX1 can include the displayed business description information of program CX1 (i.e., business description information 1) and program name (such as program name 1), and can also include the displayed avatar of program CX1 and other information, which are not limited here.

[0064] Furthermore, in response to the trigger operation on entry point 213a, page 202a of program CX1 is displayed (i.e., step S222a shown in Figure 2). This page 202a can be the message processing page of program CX1, which can be the aforementioned file upload mini-program. Here, the file upload mini-program refers to a mini-program used to upload the message content of the session message to the cloud (i.e., the aforementioned cloud server). Therefore, this page 202a can be the message processing page displayed after the file in session message 211a (e.g., file WJ1 shown in Figure 2) is uploaded to the cloud (i.e., the cloud server). This message processing page 202a can display the message processing result, for example, the message processing result can be a prompt message indicating that file WJ1 has been successfully uploaded (as shown in 214a in Figure 2). It is understood that in this embodiment of the application, the message processing page can be the page corresponding to the sub-function of the target business program.

[0065] It should be noted that this application may display prompt interfaces, pop-ups, or output voice prompts before and during the collection of user-related data (such as the mini-programs used by the user). These prompt interfaces, pop-ups, or voice prompts are used to inform the user that their relevant data is being collected. This ensures that the application only begins the steps related to collecting user-related data after receiving confirmation from the user regarding the prompt interface or pop-up; otherwise (i.e., without receiving confirmation from the user), the steps to collect user-related data end, meaning no user-related data is collected. In other words, all user data collected in this application is collected with the user's consent and authorization, and the collection, use, and processing of relevant user data must comply with the relevant laws, regulations, and standards of the relevant regions.

[0066] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0067] Further, please refer to Figure 3, which is a flowchart illustrating a message processing method provided in an embodiment of this application. This method can be executed by a terminal device running a client, such as the aforementioned terminal device 11a. The method may include at least the following steps S101-S104.

[0068] S101. Display message handling controls for the target session message on the session page;

[0069] The target session message refers to one or more messages selected from the session messages displayed on the session page. In other words, in this embodiment of the application, any number of messages selected from the session messages displayed on the session page can be collectively referred to as the target session message.

[0070] The conversation page can be a page used to display conversation messages. Specifically, the conversation page can be a page where a first account has a conversation with any other account, and the first account can be an account logged in on the client. Furthermore, the conversation page can display at least one conversation message. This message can be a message sent by the first account or a message received by the first account; there are no restrictions on this. For example, if the conversation page is a page where the first account has a conversation with a second account, then the page can be used to display conversation messages sent from the first account to the second account, or vice versa.

[0071] Optionally, the conversation page can be the page selected by the business object corresponding to the first account from the conversation list (e.g., the historical conversation list) for a one-on-one conversation in a one-on-one scenario, or the page selected by the business object corresponding to the first account from the historical conversation list for a group conversation in a group conversation scenario. In other words, in different conversation scenarios (e.g., one-on-one or group conversation scenarios), the number of second accounts that can have a conversation with the first account can be one or more. For example, if there is only one second account, the conversation page can be a one-on-one conversation between the first account and a single second account; conversely, if there are multiple second accounts, the conversation page can be a group conversation between the first account and multiple second accounts. It should be understood that in a one-on-one chat scenario, the two accounts displayed on the chat page (i.e., the second account and the first account) can be the same account or different accounts. That is, when a user needs to have a chat with themselves, they can establish a chat through the first account and the second account (i.e., the account that is the same as or related to their own first account). Optionally, in a one-on-one chat scenario, the second account among the two accounts displayed on the chat page can also be a service account, such as a service account used for file transfer. This is not limited here.

[0072] The target session message can refer to the message selected from the session messages on the session page, meaning that the target session message is selected. The target session message can be any one or more session messages on the session page. Each session message in the target session message has a corresponding message data type, which can refer to the data type of the message content. For example, the message data type can be text, image, file (e.g., various file types such as Word, PDF, XLSX), link, etc., without limitation. If the target session message contains multiple session messages, the data type of each session message can be the same or different, and its specific selection can be made by the business object (e.g., the user corresponding to the first account) according to its own needs, without limitation.

[0073] Among them, the message processing control can be a control used to trigger message processing of the target session message through the mini program. In other words, the message processing control can be a control used to trigger the display of the mini program that can process the target session message (i.e., the mini program that supports the message processing type of the target session message).

[0074] The session page may include a first type of session page and a second type of session page.

[0075] The first type of session page can be a session page that allows direct sending and / or receiving of session messages through the first account. This first type of session page can include a message sending area for sending session messages and a first message display area for displaying received or sent session messages. The message sending area can be an area for sending session messages, and can include multiple controls for sending session messages, such as controls for sending text, voice, files, emoticons, etc. Thus, business objects (such as the user corresponding to the first account) can send various types of session messages through multiple session controls in the message sending area. The first message display area is an area on the first type of session page that displays session messages received or sent by the first account. Each session message can be associated with and display information about the account that sent the session message (referred to as account information), such as account name, account avatar, etc.

[0076] Optionally, the first type of session page may be displayed in response to a triggered operation on a session entry displayed in the historical session list or the session search list. The session entry on this session page may be displayed in the historical session list or the session search list; this is not limited here. The historical session list may refer to a list of created sessions, and the session search list may refer to a list of sessions obtained through a search.

[0077] For example, please refer to Figure 4, which is a schematic diagram of the effect of a first type of conversation page provided in an embodiment of this application. Page 411a is a first type of conversation page, which may include a first message display area 401a for displaying received or sent conversation messages and a message sending area 402a for sending conversation messages. As shown in Figure 4, the first message display area 401a can be used to display conversation messages sent when account Z1 and account Z2 have a conversation, such as conversation message 403a. As shown in Figure 4, the conversation sending area 402a can be an area used to instruct account Z1 to enter and send conversation messages. The conversation sending area 402a may include multiple controls for sending conversation messages, such as controls for sending text (as shown in Figure 4 405a), controls for sending voice (as shown in Figure 4 404a), controls for sending emoticons (as shown in Figure 4 407a), and controls for sending more data (such as files) (as shown in Figure 4 406a), etc., which are not limited here.

[0078] The second type of conversation page can be a conversation page determined based on the first type of conversation page. Specifically, the second type of conversation page can be displayed in response to a conversation selection operation performed in the first type of conversation page. The conversation selection operation can be an operation used to trigger a flexible selection of at least one conversation message displayed. In other words, the second type of conversation page can be a conversation page used to flexibly select conversation messages visually presented in the first type of conversation page. For example, in this embodiment of the application, the conversation page obtained by the user through triggering the "multi-select" control in the menu bar where the control 212a is located, which is used to flexibly select one or more conversation messages that are the same as each conversation message in the first type of conversation page, can be called the second type of conversation page. In this way, the one or more messages that the user can flexibly select in the second type of conversation page are collectively referred to as the above-mentioned target conversation message.

[0079] The second type of conversation page may include a second message display area and a function display area for processing selected conversation messages. The second message display area is essentially a region within the second type of conversation page used to display and allow the user to select conversation messages received or sent by the first account. Each conversation message displayed in this second message display area is associated with information about the account that sent the message, such as the account name and avatar. Furthermore, each conversation message displayed in the second message display area of ​​the second type of conversation page is also associated with a corresponding message selection control (i.e., a control for selecting conversation messages). A message selection control can be used to select or deselect a conversation message associated with it. This means that the user corresponding to the first account can select or deselect each conversation message displayed in the second message display area of ​​the second type of conversation page by triggering the respective message selection controls.

[0080] The processing function display area can be an area for processing selected conversation messages (e.g., batch processing). Various functional controls can be displayed in this processing function display area. For example, the functional controls can be message processing controls (e.g., controls for indicating "open" the mini program), and can also include message forwarding controls (controls for batch forwarding selected conversation messages), message deletion controls (controls for batch deleting selected conversation messages), message collection controls (controls for batch collecting selected conversation messages), etc. There are no limitations here.

[0081] Optionally, the second type of conversation page can also be understood as an equivalent adjustment to the first type of conversation page. For example, the page adjustment here may specifically include adding a display of associated message selection controls to each conversation message in the first type of conversation page, and adding a display area for processing functions while canceling the display of the message sending area.

[0082] For example, please refer to Figure 5, which is a schematic diagram of the effect of a second type of conversation page provided in an embodiment of this application. As shown in Figure 5, page 511a is a second type of conversation page. The second type of conversation page 511a may include a second message display area 521a and a processing function display area 522a for processing (e.g., batch processing) selected conversation messages. The second message display area 521a can be an area in the second type of conversation page used to display conversation messages generated between account Z1 and account Z2. Furthermore, each conversation message displayed in the second type of conversation page is associated with a corresponding message selection control. For example, in page 511a, the message selection control for conversation message 502a is shown as 501a in Figure 5. This message selection control 501a indicates that conversation message 502a is in an unselected state; similarly, the message selection control for conversation message 504a is shown as 503a in Figure 5. This message selection control 503a indicates that conversation message 504a is in a selected state. The processing function display area 522a may include various functional controls. For example, the functional controls may be message processing controls (as shown in 508a in Figure 5), message forwarding controls (as shown in 505a in Figure 5), message collection controls (as shown in 506a in Figure 5), message deletion controls (as shown in 507a in Figure 5), and controls for triggering the display of more message processing functions (as shown in 509a in Figure 5).

[0083] In one embodiment, the session page includes a first type of session page; the target session message includes a first session message among the session messages displayed in the first type of session page, and the first session message includes a single session message; then, the specific process by which the terminal device displays a message processing control for the target session message in the session page may include the following steps: ① In response to a message triggering operation for the first session message in the first type of session page, displaying a first message association area associated with the first session message; the first message association area is determined based on the message display position of the first session message; the first session message associated with the first message association area is in a selected state; ② Displaying a first message processing control for the first session message in the first message association area; the first message processing control is a message processing control.

[0084] The description of the first type of session page can be found in the above description, and will not be repeated here.

[0085] The first session message can be a session message selected from the session messages displayed within the first type of session page. This first session message includes a single session message; that is, in this embodiment, session pages that allow users to directly select a single session message for message processing can be collectively referred to as first type session pages.

[0086] The first message-associated area can be a message-associated area related to the first conversation message. The message-associated area can be an area used to display related processing controls (such as message processing controls, favorite controls, delete controls, etc.) for the conversation message (such as the first conversation message). It is understood that the message-associated area for any conversation message can be the area corresponding to a function option bar (also called a menu bar) that pops up on the conversation page. The first message-associated area is determined based on the message display position of the first conversation message; this first message-associated area can be above, below, or overlap with the message display position of the first conversation message, etc., without limitation here. Optionally, if the message display position of the first conversation message is in the upper half of the first type of conversation page, then the first message-associated area can be displayed below the message display position of the first conversation message; if the message display position of the first conversation message is in the lower half of the first type of conversation page, then the first message-associated area can be displayed above the message display position of the first conversation message.

[0087] It is understandable that when displaying the first message association area associated with the first session message, the first session message is in a selected state. The display style of the message content of the selected first session message can differ from the display style of the message content of a session message that is not selected. For example, when the message data type of the first session message is text, in response to the message trigger operation for the first session message in the first type of session page, when displaying the first message association area associated with the first session message, the background color of the text within the area containing the text content of the first session message is adjusted so that the background color of the text within the area containing the text content of the first session message can be changed. For example, the background color of the text within the area containing the text content of the first session message after adjustment can be darker than the background color of the text within the area containing the text content of the first session message before adjustment; optionally, the background color of the text within the area containing the text content of the first session message after adjustment can also be darker than the background color of other areas containing the message content of other session messages that are not selected. For example, when the message data type of the first session message is an image data type or a file data type, in response to the message triggering operation of the first session message in the first type of session page, when displaying the first message association area associated with the first session message, the area where the image content or file content in the first session message is located is highlighted.

[0088] Based on the above description, the first message processing control can refer to the message processing control displayed in the menu bar (i.e., the first message association area) that pops up on the first type of session page for the first session message that is in the selected state. The first message processing control belongs to the above-mentioned message processing control.

[0089] In one embodiment, the specific process of a terminal device performing a message triggering operation in response to a first session message in a first type of session page and displaying a first message association area associated with the first session message may include the following steps: in response to a long press operation on a first session message in a first type of session page, displaying a first message association area for the first session message; a long press operation refers to an operation in which the first session message is pressed and held for a duration that reaches a target duration threshold.

[0090] Among them, a long press operation refers to an operation in which the duration of pressing and holding the first conversation message reaches a target duration threshold. The target duration threshold can be the minimum duration used to determine whether pressing and holding the conversation message is a long press operation. For the long press operation of the first conversation message, it can be any position in the message display position where the first conversation message is located.

[0091] For example, please refer to Figure 6, which is a schematic diagram of the effect of displaying a message association area provided by an embodiment of this application. As shown in Figure 6, page 611a is a first type of session page, which may include multiple session messages, such as session message 601a. ​​In response to a message triggering operation for session message 601a, the message association area 602a of session message 601a is displayed (i.e., step S621a shown in Figure 6). The message association area 602a may include a message processing control 603a for session message 601a. ​​Furthermore, session message 601a may be in a selected state, and the display style (e.g., background color) of the area where the text content of session message 601a is located when it is in a selected state is different from the display style of the area where the text content of session message 601a is located when it is in an unselected state. Specifically, please refer to 604a in Figure 6. It is understandable that the message association area 602a may also include other functional controls, such as a forwarding control 608a, a favorite control 609a, a reference control 607a (a control used to reference session messages), a delete control 606a, and a session selection control 605a for selecting sessions, as shown in Figure 6. The session selection control 605a may be a "multi-select" control used to indicate the selection of sessions.

[0092] Optionally, the functional controls displayed in the message association area of ​​a conversation message can be determined based on the message data type of the conversation message. For example, for conversation messages of voice data type, functional controls for speech-to-text conversion can be displayed in the message association area displayed in response to conversation messages of voice data type, while functional controls for speech-to-text conversion can be omitted in the message association area displayed for conversation messages of text data type.

[0093] It is understandable that this long-press operation can be a message trigger operation targeting a first conversation message (e.g., a single conversation message). Optionally, the message trigger operation targeting a first conversation message can also be a target gesture operation targeting a first conversation message (e.g., one or more conversation messages). The conversation messages traversed by the swiping trajectory generated by the target gesture operation are the first conversation messages. Therefore, when selecting a first conversation message through the target gesture operation, the first conversation message can also refer to one or more conversation messages, specifically determined by the number of conversation messages traversed by the swiping trajectory generated by the target gesture operation. Furthermore, the first conversation messages traversed by the swiping trajectory generated by the target gesture operation are in a selected state. For example, the target gesture operation can be an operation of swiping in an "S" shape with multiple fingers (e.g., two fingers) on a first type of conversation page; then the conversation messages traversed by the "S"-shaped swiping trajectory generated by the target gesture operation are the first conversation messages.

[0094] In one embodiment, the session page includes a second type of session page, where the session messages displayed are the same as those displayed in the first type of session page; the target session message includes a second session message among the session messages displayed in the second type of session page, and the second session message includes at least one session message; then, the specific process by which the terminal device displays a message processing control for the target session message in the session page may include the following steps: in response to a session selection trigger operation for the first type of session page, displaying the second session message in the second type of session page, and displaying a second message processing control for the second session message; the second message processing control is a message processing control.

[0095] The second session message can be a session message selected from the session messages displayed within the second type of session page. This second session message includes at least one session message; that is, one or more session messages can be selected for message processing within the second type of session page.

[0096] The session selection trigger operation can be an operation used to trigger the display of a second type of session page within a first type of session page. Optionally, the session selection trigger operation can be a trigger operation on a session selection control within the second message association area (which may be referred to as the second message association area) when the first type of session page displays a message association area associated with the session message triggered by the message trigger operation. This session selection control can be a control used to trigger session selection. The second message association area can be the same as or different from the first message association area mentioned above; this is not limited here, and its specific nature depends on the session message triggered by the message trigger operation.

[0097] Optionally, the session selection trigger operation can be a target gesture operation on at least one session message displayed on the first type of session page. The descriptions of message trigger operations and target gesture operations can be found in the above descriptions. Based on the above descriptions, triggering a second type of session page through a target gesture operation on the first type of session page can include: on the first type of session page, in response to a target gesture operation on at least one session message, a message association area associated with the at least one session message can be displayed; then, in response to a trigger operation on the session selection control in the message association area, the second type of session page is displayed; or, on the first type of session page, in response to a target gesture operation on at least one session message, the second type of session page is displayed.

[0098] When a second conversation message is displayed on a second-type conversation page, it is in a selected state. The display style of the message selection control corresponding to a selected second conversation message can be different from the display style of the message selection control corresponding to a deselected conversation message. For example, the message selection control corresponding to a selected conversation message may be displayed as a circle (or other shape) with a fill color, while the message selection control corresponding to a deselected conversation message may be displayed as a circle (or other shape) without a fill color.

[0099] Based on the above description, the second message processing control can refer to the message processing control displayed on the second type of session page for the selected second session message, and this second message processing control belongs to the aforementioned message processing controls. Based on the above description, the second message processing control can be displayed in the processing function display area of ​​the aforementioned second type of session page.

[0100] It is understood that the second conversation message displayed on the second type of conversation page can refer to the conversation message targeted by the conversation selection trigger operation, which is directly displayed on the second type of conversation page in response to the conversation selection trigger operation for the first type of conversation page. For example, the conversation message triggered by the message trigger operation, or the conversation message traversed by the swipe trajectory generated by the target gesture operation. Optionally, the second conversation message displayed on the second type of conversation page can also be the conversation message selected after flexibly selecting from the various conversation messages displayed on the second type of conversation page in response to the conversation selection trigger operation for the first type of conversation page. In this case, the second conversation message may or may not include the conversation message targeted by the conversation selection trigger operation; this is not limited here.

[0101] In one embodiment, the specific process by which a terminal device displays a second session message on a second type of session page in response to a session selection trigger operation for a first type of session page may include the following steps: ① in response to a message trigger operation for a session message displayed on the first type of session page, displaying a second message association area associated with the session message triggered by the message trigger operation; ② displaying a session selection control for selecting a session in the second message association area; ③ in response to a trigger operation for the session selection control, displaying the second session message on the second type of session page.

[0102] The description of message triggering operations can be found above and will not be repeated here. The second message association area can be the message association area associated with the session message triggered by the message triggering operation. Its display method can be found above in the description of the first message association area and will not be repeated here.

[0103] In one embodiment, each session message displayed in the second type of session page is associated with a corresponding message selection control; the session messages displayed in the second type of session page include triggering session messages and optional session messages that are different from triggering session messages, wherein the triggering session message is the session message triggered by a message triggering operation; the second session message is the session message displayed in the second type of session page that is in a selected state; then, the specific process by which the terminal device performs a triggering operation on the session selection control and displays the second session message in the second type of session page may include the following steps: ① In response to a triggering operation on the session selection control, display the triggering session message in a selected state and the optional session message in an unselected state in the second type of session page; ② In response to a triggering operation on the message selection control of the optional session message in an unselected state, display the optional session message in a selected state; both the triggering session message in a selected state and the optional session message in a selected state belong to the second session message.

[0104] Among them, the triggering operation for the session selection control (for example, the "multi-select" control shown in Figure 7 below) can be a touch operation on the session selection control, such as clicking the session selection control.

[0105] Among them, the triggering conversation message is the conversation message triggered by the message triggering operation, and the optional conversation message is an optional conversation message that is different from the triggering conversation message. For example, when the conversation messages displayed in the first type of conversation page include conversation message X1, conversation message X2, conversation message X3, and conversation message X4, if the message triggering operation performed by the user in the first type of conversation page is a long press operation on conversation message X2, then conversation message X2 triggered by the message triggering operation in the first type of conversation page can be called the triggering conversation message used for visual presentation (i.e., display) in the second type of conversation page, and other conversation messages in the first type of conversation page that are not triggered by the message triggering operation (e.g., conversation message X1, conversation message X3, and conversation message X4) are collectively called optional conversation messages used for visual presentation (i.e., display) in the second type of conversation page. Understandably, when navigating from the first type of conversation page to the second type of conversation page, the message state of the triggering conversation message can be selected, meaning the triggering conversation message displayed on the second type of conversation page is currently selected. Conversely, the message state of the optional conversation message can be unselected, meaning the optional conversation message displayed on the second type of conversation page is currently unselected. Therefore, business objects (such as the user corresponding to the first account) can flexibly select from various conversation messages. For example, they can add a selection to an optional conversation message. In this case, the terminal device can respond to a trigger operation (add selection operation) on the message selection control corresponding to the optional conversation message to change the message state of that optional conversation message from unselected to selected. The optional conversation message in the selected state can then be referred to as a newly added triggering conversation message. Similarly, they can deselect a triggering conversation message. In this case, the terminal device can respond to a trigger operation (deselect operation) on the message selection control corresponding to the triggering conversation message to change the message state of that triggering conversation message from selected to unselected. The triggering conversation message in the unselected state can then be referred to as a newly added optional conversation message. Therefore, in the second type of conversation page, the message selection controls displayed in front of each conversation message can be used to change the status of each conversation message.

[0106] For example, the trigger operation for a message selection control that is in an unselected state can be a touch operation on the message selection control, such as clicking the message selection control, which can adjust the display style of the message selection control to the selected display style, such as displaying it as a circle with a fill color. Then the message state of the corresponding optional conversation message can be changed from the original unselected state to the selected state.

[0107] For example, please refer to Figure 7, which is a schematic diagram illustrating the effect of displaying a second type of conversation page according to an embodiment of this application. As shown in Figure 7, page 711a is a first type of conversation page. In page 711a, a message association area 703a for conversation message 701a is displayed. This message association area 703a may be displayed in response to a message triggering operation for conversation message 701a, which will not be elaborated here. A conversation selection control 702a may be included in the message association area 703a. In response to a triggering operation for the conversation selection control 702a, page 712a is displayed (i.e., step S721a shown in Figure 7). As shown in Figure 7, page 712a is a second-type session page. When entering the second-type session page, since the message status of session message 701a is selected, the terminal device can configure the display style of the message selection control corresponding to session message 701a on the second-type session page to the selected display style (as shown in 704a in Figure 7). This allows the message selection control 704a with the selected display style to be displayed in association with session message 701a on the second-type session page. For the other session messages, the message status is unselected. Therefore, the terminal device can configure the display style of the message selection controls corresponding to the other session messages on the second-type session page to the unselected display style (as shown in 705a in Figure 7) for display. For example, as shown in Figure 7, when session message 706a is unselected, the display style of the message selection control corresponding to session message 706a is the unselected display style (as shown in 705a in Figure 7). Furthermore, in response to the trigger operation of the message selection control 705a, if the session message 706a is selected (step S722a), then after the session message 706a is selected, the display style of the message selection control corresponding to the session message 706a can be adjusted to the selected display style (as shown in 707a in Figure 7).

[0108] In one embodiment, the present application embodiment may further include the following steps: in response to a selection cancellation operation of the message selection control for the selected trigger session message, displaying the trigger session message in an unselected state; the trigger session message in an unselected state does not belong to the second session message.

[0109] For example, the deselection operation for a message selection control that triggers a session message when it is currently selected can be achieved through a touch operation on the message selection control, such as clicking the message selection control. This will change the display style of the message selection control to an unselected display style, thereby changing the previously selected session message to an unselected state. For instance, when the display style of the message selection control changes from a circle with a fill color to a circle without a fill color, the status of the corresponding session message will simultaneously change from selected to unselected.

[0110] It is understandable that in the second type of conversation page, a selection cancellation operation can be performed on any conversation message that is selected, and a selection operation can be performed on any conversation message that is not selected. For an introduction to the selection cancellation operation and the selection operation, please refer to the relevant descriptions above, which will not be repeated here.

[0111] S102. In response to a trigger operation on the message processing control, display N business programs that match the message data type of the target session message;

[0112] Where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; these N business programs include the target business program used to process the target session messages.

[0113] Among them, the triggering operation for the message processing control can be a touch operation on the message processing control, such as clicking the message processing control.

[0114] Here, a business program can refer to a small program that matches the message data type of the target session message. The number of business programs can be N, where N is a positive integer. That is, there must be at least one business program that matches the message data type of the target session message. The N business programs may include the target business program, which can be any of the N business programs. Optionally, the target business program can be selected by the business object (such as the user corresponding to the first account) according to its needs. The target business program is used to process the target session message. Here, the specific method of determining the target business program will not be limited.

[0115] Optionally, the N business programs can be mini-programs that match the message data type, determined from the historical program set of the first account. This historical program set can be a collection of mini-programs already used by the first account. Alternatively, if no mini-program matching the message data type exists in the historical program set of the first account, the N business programs can be mini-programs that match the message data type, determined from the recommended programs for the first account. Recommended programs can refer to mini-programs accessed by accounts that have established a friend relationship with the first account through triggering conversation messages on the conversation page, or mini-programs whose access count meets the recommendation criteria among all registered accounts (i.e., all registered accounts) accessed through triggering conversation messages on the conversation page. The recommendation criteria can be a condition that the access count is greater than an access count threshold, or a condition that the sorted order obtained when ranking the access counts of each mini-program from high to low is less than an order threshold.

[0116] It is understandable that each business program has a corresponding processable data type. The processable data type can refer to the data type that the business program can process. The business program can be obtained by matching the data type of the target session message with the processable data type of the business program. The specific process of data type matching can be executed by the first server corresponding to the client (e.g., the server 100a mentioned above).

[0117] In one embodiment, the present application embodiment may further include the following steps: ① When displaying N business programs, N program access entries corresponding to the N business programs are displayed, and one program access entry is used to access one business program; ② In each program selection entry of the N program access entries, the program description information of the corresponding business program is displayed respectively; the program description information includes at least: program identifier and business description information.

[0118] Among them, the program access entry can be an entry point used to access a business program, and one program access entry can be used to access one business program.

[0119] The program description information can be used to describe the corresponding business program. The program description information includes at least: a program identifier and business description information. The program identifier can identify a business program; for example, it can be the name of the business program, its program avatar, or its unique identifier. The business description information can describe the message processing procedures that can be performed when accessing the corresponding business program through the corresponding program access portal. For example, if the business program is a program CX1 that provides cloud storage functionality through the aforementioned cloud server, then the business description information of program CX1 can describe that the message content of the target session message can be uploaded to the cloud (i.e., the aforementioned cloud server) for storage. Optionally, the program description information may also include other information, such as the permissions required by the business program, the number of times the business program has been accessed, which friend accounts have used it, and the number of times the first account itself has used it; this is not limited here.

[0120] Optionally, when displaying N business programs, they can be displayed in a different function option bar (also known as a menu bar) that pops up on the session page. The area where this pop-up function option bar displays the N business programs is located is the program trigger area. In other words, the N business programs can be displayed in the program trigger area on the session page. Optionally, when displaying N business programs, they can also be displayed on a different page than the session page (i.e., a program trigger page independent of the session page). There is no limitation here.

[0121] For example, please refer to Figure 8, which is a schematic diagram of the effect of a business program display method provided by an embodiment of this application. As shown in Figure 8, if the session page is a first type of session page, for example, the first type of session page is page 811a, page 811a can display a message processing control 831a for the currently selected single session message. Then, in response to the trigger operation of the message processing control 831a, N business programs are displayed (i.e., step S821a shown in Figure 8). The N business programs (such as program CX1 and program CX2) can be displayed in the program trigger area 801a on page 811a. The program trigger area 801a can be the area corresponding to the function option bar that pops up on page 811a. In the program trigger area 801a, there can be an area 802a for displaying the program access entry of the business program. The program access entry of each business program can be displayed in the area 802a, for example, the program access entry 803a of program CX1 can be displayed. Optionally, the program triggering area 801a may also include an area 804a for displaying devices that can process the target session messages. For example, devices that can process the target session messages may include a television 1 (as shown in 805a in Figure 8) and a printer 2 (as shown in 806a in Figure 8).

[0122] Optionally, as shown in Figure 8, if the session page is a second type of session page, for example, page 812a, page 812a can display message processing controls 832a for the currently selected multiple session messages. Then, in response to a trigger operation on the message processing controls 832a, N business procedures are displayed (i.e., step S822a shown in Figure 8). These N business procedures (e.g., procedures CX1 and CX2) can be displayed in the program trigger area 807a on page 812a. This program trigger area 807a can be the area corresponding to the function option bar that pops up on page 812a. For a description of the program trigger area 807a, please refer to the description of the program trigger area 801a above; it will not be repeated here.

[0123] In one embodiment, displaying N business programs that match the message data type of the target session message in response to a trigger operation on the message processing control may include the following steps: ① In response to a trigger operation on the message processing control, sending a program matching request for the target session message to a first server corresponding to the client, so that the first server queries N business programs that match the message data type of the target session message based on the program matching request, and obtains program association information of the N business programs; the program association information includes program description information of the business programs; ② Upon receiving the program association information of the N business programs returned by the server, displaying the N business programs that match the message data type of the target session message based on the program description information of the N business programs.

[0124] The triggering operations for the message processing controls can be referred to the relevant descriptions above, and will not be repeated here. The first server can be the server corresponding to the client.

[0125] The program matching request can be a request sent by the client to retrieve a business program that matches the message data type of the target session message. This program matching request may carry the message data type of the target session message, and may also carry an account identifier for a first account. This account identifier can be used by the server to determine the historical program set corresponding to the first account.

[0126] The method by which the first server queries N business programs that match the message data type of the target session message based on the program matching request can be referred to in the following related description, and will not be repeated here.

[0127] The program association information refers to information associated with a business program. This information may include the program description information of the business program. For a description of the program description information, please refer to the relevant descriptions above; it will not be repeated here. Furthermore, the terminal device can display N business programs that match the message data type of the target session message based on the program description information of N business programs. The specific display method of the program description information of each business program displayed in the program access entry of the business program can be referred to the relevant descriptions above; it will not be repeated here.

[0128] The program association information may also include the program access path information of the business program. This program access path information can be the path information used to access the page (i.e., the message processing page) in the business program used to process the target session message. For example, the program access path information is "pages / material / index".

[0129] S103. In response to a trigger operation on the target business program, display the message processing page of the target business program.

[0130] The triggering operation for a target business application can be an operation used to trigger access to the target business application. Specifically, the triggering operation for a target business application can be a touch operation targeting the application's access point, such as a click operation on any location within the area where the application's access point is located. The triggering operation for a target business application can also be called "opening the target business application." Here, "opening" can represent the flow of data between different carriers (terminal devices, mini-programs, clients, etc.). For example, opening a target business application means that when a user triggers access to the target business application in the client, the terminal device can transfer the target session message selected by the user in the client to the mini-program, so that subsequent message processing of the target session message can be performed on the mini-program's message processing page.

[0131] The message processing page can be used to process messages in the target session. It is understood that this message processing page can be determined by the program access path information of the target business application, and the message processing page corresponding to different business applications can be configured by the management objects of the business applications (such as developers) according to business needs.

[0132] Optionally, based on the above description, if the target session message contains multiple session messages, the data type of each session message can be the same or different. Therefore, the N business programs match all session messages in the target session message; that is, the processable data types of the N business programs can match the message data types of all session messages in the target session message.

[0133] Alternatively, the N business programs may only match a portion of the session messages in the target session message. That is, the processable data types of the N business programs may match the message data types of a portion of the session messages in the target session message. In this case, the target business program triggered by the business object (such as the user corresponding to the first account) may only be able to process a portion of the session messages in the target session message. Therefore, before displaying the message processing page of the target business program, a data processing prompt can be displayed to indicate that session messages whose message data types do not match the target data type need to be filtered before further message processing can be performed. The target data type can be a processable data type of the target business program.

[0134] In one embodiment, the specific process by which a terminal device displays the message processing page of a target business program in response to a trigger operation for that target business program may include the following steps: ① When the target session message includes multiple session messages, in response to the trigger operation for the target business program, display a data processing prompt message; the data processing prompt message is displayed when there are session messages among the multiple session messages included in the target session message whose message data type does not match the target data type; the target data type is a data type that the business program can process; the data processing prompt message is used to prompt that the session messages whose message data type does not match the target data type be filtered before message processing; ② In response to the data processing confirmation operation of the data processing prompt message, display the message processing page of the target business program; the message processing page is used to process the filtered session messages.

[0135] The data processing prompt is displayed when a message among the multiple session messages included in the target session message contains a message whose data type does not match the target data type. The target data type is a data type that the business program can process. The data processing prompt is used to suggest filtering the session message whose data type does not match the target data type, so that the filtered session message can be processed. Optionally, the detection of a message among the multiple session messages included in the target session message containing a message whose data type does not match the target data type can be performed by the client when it obtains the target data type that the target business program can process (i.e., supports processing) from the first server, or it can be performed by the server when it obtains the message type of the target session message, and then the detection result is returned to the client so that the data processing prompt is displayed based on the detection result. There is no limitation here.

[0136] Optionally, the data processing prompt can be displayed in a pop-up window on the session page. When displaying the data processing prompt in the pop-up window, a data processing confirmation control and a data processing cancellation control can be shown. The data processing confirmation control confirms message processing of the filtered session message. The data processing cancellation control cancels message processing of the filtered session message; responding to a triggering operation on the data processing cancellation control returns the user to the session page.

[0137] The data processing confirmation operation for the data processing prompt information can be a confirmation operation for processing filtered session messages. For example, this data processing confirmation operation can be a touch operation on a data processing confirmation control, such as clicking the data processing confirmation control. Furthermore, the message processing page of the target business program can be used to process filtered session messages. In other words, the target business program will not need to process session messages whose data type does not match the target data type, thus improving the message processing success rate to some extent.

[0138] Optionally, if the target session message includes multiple session messages, and none of the session messages in the target session message contain a message whose data type does not match the target data type, the message processing page of the target business program is directly displayed in response to a trigger operation for the target business program. Optionally, if the target session message includes a single session message, the message processing page of the target business program can also be directly displayed in response to a trigger operation for the target business program. Based on this, it can be seen that when the message data type of the target session message completely matches the target data type that the target business program can support processing, the message processing page of the target business program can be directly displayed in response to a trigger operation for the target business program, thereby improving the efficiency of displaying the message processing page and thus improving the timeliness of showing the user the message processing results obtained from processing the target session message on the message processing page.

[0139] Optionally, the terminal device can also pre-determine whether there are any session messages whose message data type does not match the target data type among the multiple session messages included in the target session message. In this way, when there are session messages whose message data type does not match the target data type among multiple session messages, the terminal device can ensure that it can quickly pop up a prompt window in response to the trigger operation of the target business program to display data processing prompt information. This allows the user to better understand whether the data type supported by the target business program is the target data type (i.e., the aforementioned processable data type).

[0140] In one embodiment, the program association information includes program access path information for N business programs. Therefore, the specific process by which the terminal device displays the message processing page of the target business program in response to a trigger operation for that target business program may include the following steps: ① In response to a trigger operation for the target business program, a message processing request is determined based on the program access path information of the target business program and the message content of the target session message (i.e., the target message content). A message processing request is then sent to the second server corresponding to the target business program, so that the second server determines the message processing data for the target message content based on the message processing request; ② Upon receiving the message processing data returned by the second server, the message processing page of the target business program is displayed based on the message processing data.

[0141] The description of the program access path information can be found above and will not be repeated here. The second server can be the server corresponding to the target business program, and can be used to provide services to the target business program (for example, it can provide the target business program with a service for processing target session information).

[0142] The message processing request can be a request to process a target session message through a target business program. This request can carry the program access path information of the target business program and the target message content of the target session message. The program access path information can be used to instruct the second server to obtain page data related to the message processing page. The target message content can refer to all or part of the content included in the target session message. Based on the above description, the target message content submitted to the second server can be the content of a session message whose message data type matches the target data type. That is, when there are session messages among the multiple session messages included in the target session message whose message data type does not match the target data type, the target message content submitted to the second server is the content of the filtered session message.

[0143] Optionally, the message processing request may also carry the account information of the first account, so that the second server can obtain the access rights of the first account based on the account information of the first account, and then authenticate the first account. Only after successful authentication can the second server determine the message processing request as a legitimate processing request, and then quickly determine the message processing data for the target message content based on the legitimate message processing request.

[0144] The message processing data refers to the data displayed on the message processing page. This can include page data, such as UI information and textures, used for page display. Optionally, the data may also include the message processing result for the target message session. This result refers to the outcome of processing the target message content. When the client receives the message processing data from the second server, it can simultaneously render and display the message processing result on the message processing page while simultaneously rendering the page based on the page data. For example, if the target business application is a mini-program for summarizing content, the summary information (i.e., the message processing result) obtained from summarizing the target message session can be displayed simultaneously on the message processing page when accessing it.

[0145] Optionally, the message processing result involved in the embodiments of this application may also be data that is separately issued by the second server and is independent of the message processing data containing page data. That is, when the message processing data does not include the message processing result for the target session message but still contains the page data of the message processing page, the client can directly and quickly display the message processing page of the target business program based on the page data in the message processing data when it receives the message processing data returned by the second server. In response to the interactive operation on the message processing page, the client can further retrieve and display the message processing result from the second server.

[0146] For example, when the target business application is a mini-program used to upload the message content of the target session message to the cloud (i.e., the aforementioned cloud server, which can be a second server), when accessing the message processing page of the target business application, at least one folder provided by the second server for storing data can be displayed on the message processing page. In this way, the terminal device can upload the message content of the target session message to the target folder in the cloud (i.e., the second server) in response to the selection operation of the target folder among the displayed at least one folder, thereby displaying a prompt message indicating successful message content upload (i.e., message processing result). The display method of this message processing page can be determined according to the actual business processing method of the target business application, and is not limited here.

[0147] Optionally, for some types of business applications (such as mini-programs used to translate conversation messages), when the client submits the target message content of the target conversation message to the second server corresponding to the business application, it can also synchronously send the account information corresponding to each conversation message (i.e., the information of the account that sent the conversation message) to the second server. The second server can then generate the message processing result for each conversation message (such as the result of translating the conversation message), and associate each account with the message processing result of each conversation message. When outputting the translation result of the conversation message corresponding to each account, the translation result of each conversation message can be associated with the corresponding account and displayed.

[0148] S104. Process the target session message in the message processing page.

[0149] In this context, message processing on the message processing page can be achieved through interaction between the target business program and the second server. For example, message processing on the message processing page could involve receiving the message processing result from the second server's processing of the target session message content and displaying the result; or, message processing on the message processing page could involve the terminal device responding to an interactive operation on the message processing page, notifying the second server to process the target session message content, and then displaying the processing result on the message processing page when the terminal device receives the result returned by the second server.

[0150] For example, please refer to Figure 9, which is a flowchart illustrating a message processing procedure provided in an embodiment of this application. As shown in Figure 9, page 911a is a first-type session page, which may include multiple session messages, such as session message 901a. In response to a message triggering operation for session message 901a, the message association area 902a of session message 901a is displayed (step S921a). The message association area 902a includes a message processing control 903a for session message 901a. At this time, session message 901a is selected, that is, session message 901a is the target session message. Further, in response to a triggering operation for message processing control 903a, the business program is displayed (step S922a). Specifically, the program access entry of each business program can be displayed in the program trigger area. For example, the program access entry 904a of program CX1 can be displayed. Program CX1 can be a mini-program used to upload data to the cloud. Furthermore, in response to the trigger operation of the program access entry 904a, page 912a is displayed (step S923a). This page 912a can be the message processing page of the program CX1. At least one folder that can be uploaded can be displayed on the message processing page of the program CX1 (i.e., page 912a). In response to the selection operation of the target folder in the at least one displayed folder, the message content of the target session message is uploaded to the cloud through the target folder (i.e., the message content of the target session message can be uploaded to the second server corresponding to the program CX1 and stored in the target folder of the second server). A prompt message indicating that the message content has been successfully uploaded can be displayed (as shown in 905a in Figure 2), which is the message processing result.

[0151] After successfully uploading the message content of the target session, the CX1 message processing page (page 912a) can also display various folders located in the cloud (i.e., the second server corresponding to the CX1 program), such as folder 1 (as shown in 906a in Figure 9). Users can then view the data uploaded to the cloud through folder 1. The CX1 message processing page (page 912a) can also include controls for sharing files stored in the cloud (as shown in 907a in Figure 9), allowing users to share cloud-stored data with other users based on control 907a. The message processing page 912a can also include controls for uploading data (as shown in 908a in Figure 9), allowing users to upload more data to the cloud based on control 908a.

[0152] For example, please refer to Figure 10, which is a flowchart illustrating another message processing process provided in this application embodiment. As shown in Figure 10, page 1011a can be a second type of conversation page, in which various conversation messages can be flexibly selected. The description of determining the second type of conversation page can be referred to the relevant description in Figure 7 above, and will not be repeated here. It can be seen that in page 1011a, conversation messages 1001a, 1002a and 1003a are all in the selected state. That is, at this time, the selected conversation messages 1001a, 1002a and 1003a can be collectively referred to as target conversation messages. At this time, the terminal device responds to the trigger operation of the message processing control 1004a and displays the business program (step S1021a). Specifically, the program access entry of each business program can be displayed in the program trigger area. For example, the program access entry 1005a of program CX2 can be displayed. Program CX2 can be a small program for intelligent question answering, which can summarize the content of conversation messages.

[0153] Furthermore, in response to a trigger operation on the program access point 1005a, page 1012a is displayed (step S1022a). This page 1012a can be a message processing page of program CX2, which can display message processing results. For example, the message processing results can be text results obtained by summarizing the content of the target conversation message (as shown in 1006a in Figure 10). In addition, the message processing page 1012a can also include controls for interacting with the artificial intelligence model, such as controls for sending text messages to participate in question-and-answer sessions (as shown in 1009a in Figure 10), controls for sending voice data to participate in question-and-answer sessions (as shown in 1007a in Figure 10), and controls for uploading data (such as files) to participate in question-and-answer sessions (as shown in 1008a in Figure 10). Thus, users can use these controls for interacting with the artificial intelligence model to achieve more interaction with the artificial intelligence model, such as conducting multiple rounds of question-and-answer sessions to obtain more accurate and satisfactory content summary results.

[0154] For example, please refer to Figure 11, which is a flowchart illustrating another message processing process provided in this application embodiment. As shown in Figure 11, page 1111a can be a second type of conversation page. It can be seen that in page 1111a, conversation messages 1101a, 1102a, and 1103a are all selected. That is, at this time, the selected conversation messages 1101a, 1102a, and 1103a are the target conversation messages. The target conversation messages contain multiple conversation messages, thereby responding to the trigger operation of the message processing control 1104a and displaying the business program (step S1121a). Specifically, the program access entry of each business program can be displayed in the program trigger area. For example, the program access entry 1105a of program CX2 can be displayed. Program CX2 can be a mini-program for intelligent question answering, which can summarize the content of conversation messages. Furthermore, in response to the triggering operation on the program access entry 1105a, a data processing prompt message is displayed (step S1122a). Specifically, this data processing prompt message may be a message displayed in a pop-up window stating "This mini-program only supports text data type conversation messages. It will be opened after filtering out unsupported message data types" (as shown in the pop-up window 1106a in Figure 11). This pop-up window 1106a may be determined when there are conversation messages among the multiple conversation messages included in the target conversation message whose message data type does not match the target data type. In the pop-up window 1106a, in addition to displaying the data processing prompt message (as shown in 1109a in Figure 11), a data processing confirmation control 1107a and a data processing cancellation control 1108a may also be displayed. Furthermore, in response to the triggering operation of the data processing confirmation control 1107a, page 1112a is displayed (step S1123a). This page 1112a can be a message processing page of program CX2. The message processing page can display message processing results. For example, the message processing results can be the text results obtained by summarizing the content of the target session message (as shown in 1110a in Figure 11). For an introduction to page 1112a, please refer to the relevant description of page 1012a above, which will not be repeated here.

[0155] Among these, the message processing results obtained by processing the target session message through a business program of the first program type may contain shareable result data. The first program type can refer to a program type that can generate data (i.e., shareable result data) for sharing with other accounts (such as a second account) outside the first account. This shareable result data (also called feedback result data) refers to result data used for sharing (or feedback) with other accounts (such as the second account) outside the first account. For example, program CX1 can be used to translate a file. Then, when the second server corresponding to program CX1 obtains file WJ1 from the target session message, it can translate file WJ1 and return the translation result to the client, allowing the client to display the translation result. This translation result can be shared with other accounts (such as the second account), and this translation result is the shareable result data in the message processing results. Program CX1 is the business program of the first program type.

[0156] Optionally, the message processing result obtained by processing the target session message through a business program of the second program type may not contain shareable result data. This second program type can refer to a program type that does not generate data (i.e., shareable result data) for sharing with other accounts besides the first account (such as the second account). For example, program CX1 can be used to upload a file to the cloud. Then, when the server corresponding to program CX1 obtains file WJ2 from the target session message, it can upload file WJ2 to the cloud. The second server corresponding to program CX1 can then return an upload success message to the client. This upload success message is not used to share with other accounts (such as the second account), and no shareable data is generated during the entire message processing process. Therefore, program CX2 is a business program of the second program type.

[0157] In one embodiment, the conversation page is the page where the first account and the second account conduct a conversation; then, this embodiment may further include: ① displaying the message processing result on the message processing page; the message processing result refers to the result obtained after processing the target conversation message; the message processing result includes shareable result data for the target conversation message; ② sending the shareable result data to the second account.

[0158] The descriptions of shareable result data and session pages can be found above and will not be repeated here. Based on this, after receiving the message processing result, the client can automatically send the shareable result data from that result to the second account, improving the efficiency of sharing the message processing result. Furthermore, when sending the shareable result data to the second account, it can be sent directly to the second account corresponding to the session page of the target session message, eliminating the need to manually select the account for sharing the shareable result data, thus further improving the efficiency of sharing shareable result data.

[0159] In one embodiment, the conversation page is the page where the first account and the second account conduct a conversation; then, this embodiment may further include the following steps: ① Displaying the message processing result on the message processing page; the message processing result refers to the result obtained after processing the target conversation message; the message processing result includes shareable result data for the target conversation message; ② Displaying a result sharing control for the message processing result on the message processing page; ③ In response to the triggering operation of the result sharing control, sending the shareable result data to the second account.

[0160] The result sharing control is used to share shareable result data from message processing to a second account. The triggering operation for the result sharing control can be a touch operation, such as clicking the result sharing control. Based on this, the first account can flexibly choose whether to share shareable result data to the second account according to its own needs, thereby improving the flexibility of sharing message processing results. Furthermore, when sending shareable result data to the second account, it is not necessary to manually select the account to share the shareable result data, thus improving the efficiency of sharing shareable result data.

[0161] In one embodiment, sending shareable result data to a second account may include the following steps: ① obtaining the shareable data type of the shareable result data; ② when multiple data sharing interfaces are obtained from the data sharing interface set, determining the target data sharing interface that matches the shareable data type from the multiple data sharing interfaces; ③ calling the target data sharing interface to send the shareable result data to the second account.

[0162] Here, the shared data type can refer to the data type of the result data that can be shared. For example, the shared data type can be text data type, image data type, video data type, emoticon data type, file data type, etc., without any limitation here.

[0163] The data sharing interface set can be a collection of interfaces used for data sharing, and this set can include multiple data sharing interfaces. Each of these multiple data sharing interfaces refers to an interface used for data sharing. For example, these multiple data sharing interfaces include: a data sharing interface for sharing images (sharesImageToGroup), a data sharing interface for sharing emoticons (shareEmojiToGroup), a data sharing interface for sharing videos (shareVideoToGroup), a data sharing interface for sharing files (shareFileToGroup), and a data sharing interface for sharing application link cards for business applications (shareAppMessageToGroup).

[0164] The target data sharing interface can be a data sharing interface that matches the data type being shared. This interface can then be invoked to send shareable data to the second account. For example, when the data type is text, the target data sharing interface can be one used for sharing text; when the data type is image, it can be one used for sharing images; when the data type is video, it can be one used for sharing videos; when the data type is emoticon, it can be one used for sharing emoticons; when the data type is file, it can be one used for sharing files; and when the data type is not one of the above, the target data sharing interface can be a data sharing interface for sharing a program link card for a business application. This allows the second account to directly share the program link to the business application, enabling them to open the link card, access the application, and view the shareable data.

[0165] Optionally, embodiments of this application may further include: displaying a result sharing control for message processing results on a message processing page; displaying an account selection page in response to a trigger operation on the result sharing control; and sending shareable result data to the target account in response to a selection operation on the target account displayed on the account selection page. The account selection page may be a page displaying accounts for sharing shareable result data. This page may include at least one account, and the target account may be any account selected from the at least one account displayed on the account selection page, specifically selected by the business object corresponding to the first account. It is understood that the target account may be a second account or not, and this is not limited here. Based on this, users can flexibly select the users to whom they want to share the result data according to their own needs, which helps to improve the flexibility of data sharing.

[0166] In one embodiment, the session page includes a first type of session page. This application embodiment may further include the following steps: in response to a session viewing operation on the first type of session page, a shared session message containing shareable result data is displayed on the first type of session page; the message data type of the shared session message is any one of the following: text data type, image data type, data type of program link card for viewing shareable result data, and file message data type.

[0167] Specifically, the session viewing operation for the first type of session page can be any operation used to view the first type of session page. For example, this session viewing operation can be a trigger operation for the session entry point of the target session corresponding to the session page, such as clicking the session entry point of the target session in the historical session list or search session list. The description of the session entry point for the session page can refer to the relevant descriptions above, and is not limited here.

[0168] Optionally, upon successfully sending the shareable result data to the second account, a sharing success message can be displayed on the message processing page. This message indicates that the shareable result data has been successfully shared to the second account. The sharing success message may include a session viewing control for viewing the session page. Therefore, the session viewing operation can include triggering actions on this session viewing control (such as clicking the session viewing control).

[0169] The sharing session message can be a session message containing shareable result data sent to a second account. The message data type of this sharing session message can be determined based on the target data sharing interface being invoked. Since the target data sharing interface matches the shareable result data, the message data type of the sharing session message is determined by the data type of the shareable result data. Specifically, the message data type of the sharing session message can be any of the following: text data type, image data type, data type of a program link card used to view the shareable result data, or file message data type.

[0170] For example, please refer to Figure 12, which is a schematic diagram of the effect of result data sharing provided by an embodiment of this application. As shown in Figure 12, page 1211a can be a message processing page of a business program for intelligent question answering. Page 1201a can include the message processing result obtained after processing the target session message (as shown in 1201a in Figure 12). The message processing result 1201a is shareable result data (i.e., shareable result data). The target session message can be the session message selected from the session messages between account Z1 and account Z2. Then, the shareable result data 1201a can be sent to account Z2. Further, after the shareable result data 1201a is sent to account Z2, in response to the session viewing operation for the first type of session page, page 1212a is displayed (step S1221a). The description of the session viewing operation can be referred to the above-mentioned related description, and will not be repeated here. Page 1212a can be a first type of session page, and then the session message carrying shareable result data 1201a is displayed on the first type of session page (as shown in 1202a in Figure 12).

[0171] Optionally, in the first type of session page, in response to a file viewing operation on a session file (i.e., the file carried in the session message) in a session message with a file data type, a file content page (a page for displaying the file's content) corresponding to that session file is displayed. Then, a message processing control can be triggered on this file content page. In response to a trigger operation on the message processing control, N business programs matching the file data type are displayed on this file content page. For example, these can be displayed in a pop-up function option bar (also called a menu bar) on the file content page. Then, by triggering a target business program, the session file can be processed through that target business program. The file viewing operation can be a touch operation on a session message corresponding to a file data type, such as clicking on the session message corresponding to the file data type.

[0172] For example, please refer to Figure 13, which is a product schematic diagram of a message processing process provided in an embodiment of this application. As shown in Figure 13, page 1311a is a first-type session page, which includes a session message 1301a with a message data type of file data type, and the file carried by the session message 1301a is file WJ1. Further, in response to a file viewing operation on session message 1301a, page 1312a is displayed (step S1321a). Page 1312a can be a file content page, which can be used to display the file content of file WJ1 (as shown in 1302a in Figure 13). Page 1312a can include a processing function trigger control 1303a for file WJ1, and then, in response to a touch operation on control 1303a, a message processing control 1305a is displayed (step S1322a), which can be a control used to trigger the display of a business program. The message processing control 1303a can be displayed in the file function area 1304a on the file content page 1312a. This file function area 1304a can also display a forwarding control 1308a, a favorites control 1307a, and a control that can trigger file processing through other applications (as shown in 1309a in Figure 13). The file function area 1304a can also include forwardable accounts for quick forwarding, such as accounts U3 and U4 in the area shown in 1306a in Figure 13. Furthermore, in response to a touch operation on the message processing control 1305a, business programs are displayed (step S1323a). For example, the program access entries for programs CX1, CX2, and CX3 can be displayed. For instance, the program access entry for program CX1 can be seen in 1331a in Figure 13. Each business program can be displayed in the program triggering area 1332a corresponding to a function option bar that pops up on the file content page 1312a.

[0173] In this embodiment, a message processing control for the selected target session message can be displayed on the session page. In response to a trigger operation on the message processing control, N business programs matching the target session message are displayed. Then, in response to a trigger operation on the target business program among the N business programs, the target business program can be accessed, and the data processing results can be displayed on the target business program's data processing page. Based on this, users can directly view the business programs available for processing the selected target session message on the session page, allowing them to flexibly select the business program needed for processing session messages according to their own needs. Users do not need to exit the session page to search for business programs, thus improving the flexibility and convenience of message processing through the mini-program, and significantly increasing the efficiency of message processing.

[0174] Further, please refer to Figure 14, which is a flowchart illustrating a message processing method provided in an embodiment of this application. This method can be executed by a first server corresponding to the client, such as server 100a as described above. The method may include at least the following steps S201-S203.

[0175] S201. Receive a program matching request for a target session message sent by a terminal device running a client, and obtain N business programs that match the message data type of the target session message based on the program matching request.

[0176] Where N is a positive integer; each of the N business processes is a subroutine that depends on the client to run; the target session message is the message selected from the session messages on the session page.

[0177] The descriptions of program matching requests and target session messages can be found in the above descriptions and will not be repeated here.

[0178] In one embodiment, the client is a client logged in with a first account; the program matching request carries the account identifier of the first account; then, the specific process by which the first server executes the process of obtaining N business programs that match the message data type of the target session message based on the program matching request may include the following steps: ① Obtain the account identifier of the first account from the program matching request, and query the historical program set corresponding to the first account based on the account identifier; the historical program set includes at least one historical program that has been used by the first account; ② If a historical program set is found, obtain the configuration file data of each historical program in the historical program set, and obtain the processable data type of each historical program from the configuration file data of each historical program; ③ Perform data type matching between the processable data type corresponding to each historical program and the message data type of the target session message to obtain the historical program whose processable data type matches the message data type of the target session message; ④ Determine N business programs that match the message data type of the target session message based on the historical programs obtained by data type matching.

[0179] As can be seen from the above description, the historical program set can be a set of mini-programs that the first account has used, and the historical program set includes at least one historical program that the first account has used (i.e., a used mini-program, referred to as a historical mini-program).

[0180] The configuration file data can be data within a configuration file used to configure and set various parameters of the mini-program. A mini-program's configuration file data can include the data types that the mini-program can process. This configuration file data may also include the aforementioned program access path information, program description information, etc., without limitation here.

[0181] Data type matching refers to the process of finding historical programs that match the target session message. It can be understood that if the target session message is single, data type matching can retrieve the historical program that matches that single session message; if the target session message is multiple, data type matching can retrieve the historical program that matches each individual session message within the target session message.

[0182] Optionally, when retrieving the processable data types of each historical program from the configuration file data of each historical program, different types of processable data types can be determined based on the number of session messages in the target session message. Specifically, when the number of session messages in the target session message is single, the processable data type of each historical program can be determined as the first processable data type from the configuration file data. When the number of session messages in the target session message is multiple, the processable data type of each historical program can be determined as the second processable data type from the configuration file data. The first processable data type contains a single data type, and the second processable data type contains one or more data types, which can be recorded using an array.

[0183] The first processable data type for each historical procedure, determined from the configuration file data, can be a first field identified in the configuration file data. This first field can be a field used to declare processing information when including a single session message in the target session message. For example, this first field can be as follows:

[0184] Here, `supportedMaterials` represents the first field. The `materialType` field indicates the data types the mini-program can handle; here, it can be the first handleable data type, such as "image / *". The `name` field represents the mini-program's description information, which can be described as "Open with ${nickname}", where `nickname` represents the mini-program's name. The `desc` field represents the description information for the first field; for example, here, the description information for the first field is "Single selection to open image materials". The `path` field represents the mini-program's access path information; for example, the access path information is "pages / material / index".

[0185] The second processable data type for each historical procedure, determined from the configuration file data, can be derived from a second field in the configuration file data. This second field can be a field used to declare processing information when multiple session messages are included in the target session message. For example, this second field can be as follows:

[0186] Here, `multiSelectSupportedMaterials` represents the second field. The `materialType` field indicates the data types that the mini-program can handle; in this case, it's the second type of data type. For example, this second type of data type could be `["text / message","image / *","video / *","application / pdf"]`, which can be represented by an array, specifically including `"text / message"` (text data type), `"image / *"` (image data type), `"video / *"` (video data type), and `"application / pdf"` (PDF file data type). The `desc` field represents the description information for this second field; for example, in this case, the description information is "Multi-select open materials". The `path` field represents the mini-program's access path information; for example, the access path information is "pages / material / index". The `scopes` field represents the user permissions required by the mini-program; for example, this user permission is "scope.userLocation" (i.e., user location permission).

[0187] Furthermore, when obtaining historical programs through data type matching, N business programs that match the message data type of the target session message can be determined based on these historical programs. Specifically, when the target session message contains a single session message, the historical program matching that single session message can be identified as the business program.

[0188] When a target session message contains multiple session messages, the business program can be determined by the union or intersection of the historical procedures that match each of the multiple session messages. For example, the target session message includes a text-based session message X1, an image-based session message X2, and a file-based session message X3. The historical procedures matching session message X1 include mini-programs CX1 and CX2, the historical procedures matching session message X2 include mini-programs CX2 and CX3, and the historical procedures matching session message X3 include mini-programs CX1, CX2, and CX4. If the business program is determined based on the union of the historical procedures matching each session message, the final determined business program can include mini-programs CX1, CX2, CX3, and CX4. Therefore, any business program can be used to process at least one session message in the target session message. This allows the user to choose which business program to use for processing when it is displayed on the terminal device, providing the user with greater choice. If the business procedure is determined based on the intersection of the historical procedures matched for each session message, the final determined business procedure may include: Mini Program CX2. Based on this, the determined business procedure can process all session messages in the target session message, thereby avoiding the display of the above data processing prompt information when the business procedure is triggered in the future, and improving the efficiency of accessing the business procedure.

[0189] Optionally, when the target session message includes any number of session messages, the processable data types of the historical program determined from the configuration file data are all the same, that is, the processable data types of the historical program can be recorded using a unified array.

[0190] In one embodiment, the processable data type includes a first processable data type; the first processable data type is determined when the number of target session messages is single; the first processable data type contains a single data type; then, the specific process by which the first server performs data type matching between the processable data type corresponding to each historical program and the message data type of the target session message to obtain historical programs whose processable data type matches the message data type of the target session message may include the following steps: ① In the historical program set, find historical programs whose first processable data type is consistent with the message data type of a single session message in the target session message; ② Determine the found historical programs as those whose processable data type matches the message data type of the target session message.

[0191] For example, if the target session message is session message CX1 and the message data type of the session message is text, then the first processable data type of each historical program in the historical program set can be determined. Then, from the historical program set, the historical program with the first processable data type being text is searched. The historical program with the first processable data type being text is then identified as the historical program whose processable data type matches the message data type of the target session message. Thus, the historical program with the first processable data type being text can be identified as the business mini-program.

[0192] In one embodiment, the processable data type includes a second processable data type; the second processable data type is determined when there are multiple target session messages; the second processable data type contains at least one data type; then, the specific process by which the first server performs data type matching between the processable data type corresponding to each historical program and the message data type of the target session message to obtain the historical program whose processable data type matches the message data type of the target session message may include the following steps: ① obtaining the message data types corresponding to multiple session messages in the target session message; ② determining the historical programs that match each session message in the target session message in the historical program set; the second processable data type of the historical program matched by a session message contains a data type that matches the message data type of a session message; ③ determining the historical program whose processable data type matches the message data type of the target session message based on the historical programs that match each session message in the target session message.

[0193] For example, if the target session message includes a text-type session message X1, an image-type session message X2, and a file-type session message X3, then the second processable data type of each historical program in the historical program set can be determined. Then, from the historical program set, historical programs containing text-type data types in the second processable data type are searched to obtain the historical program that matches session message X1. From the historical program set, historical programs containing image-type data types in the second processable data type are searched to obtain the historical program that matches session message X2. From the historical program set, historical programs containing file-type data types in the second processable data type are searched to obtain the historical program that matches session message X3. Furthermore, based on the historical programs that match session message X1, session message X2, and session message X3, the applets whose processable data types match the message data type of the target session message are determined.

[0194] For example, please refer to Figure 15, which is a schematic flowchart of a data type matching process provided in an embodiment of this application. As shown in Figure 15, the server can obtain a historical program set (step S1501a), which may be the historical program set corresponding to the first account. Furthermore, the server can determine the number of messages in the target session (step S1502a), and then determine whether the number of messages is greater than 1 (step S1503a). If the number of messages is no more than 1, then the first processable data type corresponding to each historical mini-program is determined from the field data corresponding to the first field in the configuration file data of each historical mini-program in the historical program collection (step S1504a). Then, the message data type of the target session message is matched with the first processable data type of each historical mini-program (step S1505a). Further, based on the matched historical mini-program, the business program is determined (step S1508a). Conversely, if the number of messages is greater than 1, then the second processable data type corresponding to each historical mini-program is determined from the field data corresponding to the second field in the configuration file data of each historical mini-program in the historical program collection (step S1506a). Then, the target session message is matched with the second processable data type of each historical mini-program (step S1507a). Further, based on the matched historical mini-program, the business program is determined (step S1508a).

[0195] In one embodiment, the present application further includes: ① if no historical program (i.e., a historical mini-program) whose processable data type matches the message data type of the target session message is determined, then at least one program to be recommended is obtained, and the configuration file data of each program to be recommended is obtained; the configuration file data of each program to be recommended includes the processable data type; ② the processable data type of each program to be recommended is matched with the message data type of the target session message to obtain the program to be recommended whose processable data type matches the message data type of the target session message; ③ based on the program to be recommended obtained by the data type matching, N business programs that match the message data type of the target session message are determined.

[0196] The method for determining at least one program to be recommended can be referred to the relevant descriptions above, and will not be repeated here.

[0197] The process of matching the data types of each program to be recommended with the data type of the target session message can be referred to the above description of matching the data types of each historical program with the data type of the target session message, and will not be repeated here. The process of determining the N business programs that match the data type of the target session message among the programs to be recommended obtained from the data type matching can be referred to the above description of determining the N business programs that match the data type of the target session message among the historical programs obtained from the data type matching.

[0198] For example, please refer to Figure 16, which is a flowchart illustrating the process of determining a business procedure according to an embodiment of this application. As shown in Figure 16, the server can obtain a historical program set (step S1601a), and then determine whether the historical program set has been obtained (step S1602a). If the historical program set has been obtained, the data type of each historical program can be matched with the message data type of the target session message (step S1603a). Then, it can be determined whether a historical program whose data type of processing matches the message data type of the target session message has been obtained (step S1604a). Based on the historical programs obtained by data type matching, N business programs that match the message data type of the target session message are determined (step S1605a). If no historical program set is obtained, or if no historical program whose processable data type matches the message data type of the target session message is obtained, at least one program to be recommended can be obtained (step S1606a). Data type matching is performed based on the processable data type corresponding to each program to be recommended and the message data type of the target session message (step S1607a). Based on the program to be recommended obtained by data type matching, N business programs that match the message data type of the target session message are determined (step S1608a).

[0199] Optionally, if no historical program that can process data types matching the message data type of the target session message is identified, after determining N business programs that match the message data type of the target session message based on the recommended program obtained through data type matching, when displaying the N business programs, a prompt message can be displayed to indicate that the N business programs are recommended mini-programs, such as displaying the text "Recommended Mini-Program".

[0200] Optionally, if no historical program that can process data types matching the message data type of the target session message is identified, the first server can directly return a prompt message to the client indicating that no matching business program was found, thereby not displaying the business program.

[0201] Optionally, when a terminal device responds to a message triggering operation for a session message on a first type of page, it can send a program matching request to a first server. The first server can then determine, based on this request, a business program that matches the message data type of the session message triggered by the message triggering operation. The first server can then determine whether to display message processing controls in the message association area corresponding to the session message triggered by the message triggering operation by checking whether a query result showing a matching business program is found. Specifically, if a historical program whose processable data type matches the message data type of the target session message is identified, the first server can directly return a prompt message to the client indicating that a matching business program has been found. The client can then display message processing controls in the message association area of ​​the session message triggered by that message triggering operation. Conversely, if no historical program whose processable data type matches the message data type of the target session message is identified, the first server can directly return a prompt message to the client indicating that no matching business program was found. The message processing controls will not be displayed in the message association area of ​​the session message triggered by that message triggering operation. Therefore, when a conversation message is triggered on the first type of conversation page, it can be determined in advance whether the triggered conversation message can be processed through the history program. If not, the message processing control can be hidden, allowing users to know whether the selected conversation message can be processed through the history program without clicking the message processing control, thus improving the convenience of conversation message processing.

[0202] S202. Obtain the program association information of N business programs;

[0203] The program association information includes the program description information and program access path information of the business program.

[0204] The description of program association information can be found in the above descriptions and will not be repeated here.

[0205] Based on the above description, obtaining the program association information of N business programs can be determined based on the number of session messages in the target session message. Specifically, when the number of session messages in the target session message is single, the program association information of each business program can be determined from the field data corresponding to the first field of the configuration file data of each business program. Specifically, the program description information and program access path information can be determined from the field data corresponding to the first field. For a description of the first field, please refer to the relevant description above; it will not be repeated here. When the number of session messages in the target session message is multiple, the program association information of each business program can be determined from the field data corresponding to the second field of the configuration file data of each business program. Specifically, the program description information and program access path information can be determined from the field data corresponding to the second field. For a description of the second field, please refer to the relevant description above; it will not be repeated here.

[0206] S203. Return the program association information of N business programs to the terminal device, so that the terminal device can display N business programs that match the message data type of the target session message based on the program description information of the N business programs. In response to the trigger operation for the target business program among the N business programs, access the message processing page of the target business program based on the program access path information of the target business program, and perform message processing on the target session message in the message processing page.

[0207] The method by which the terminal device displays N business programs based on their program description information can be referred to the above descriptions and will not be repeated here. The method for accessing the message processing page of the target business program based on its program access path information can also be referred to the above descriptions and will not be repeated here; that is, accessing the message processing page of the business program by sending a message processing request to the second server.

[0208] Based on the above description, it can be seen that in this embodiment, efficient and convenient data flow between business objects (i.e., users), sessions, and mini-programs can be achieved. For example, please refer to Figure 17, which is an interactive flowchart of a message processing method provided in this embodiment. As shown in Figure 17, business object 1401a (such as the user corresponding to the first account) can send session messages of various data types (such as text, images, files, links, locations, etc.) in a session 1402a with other accounts. In this embodiment, the user can also access mini-program 1403a in the session and can pass the message content of the session message to mini-program 1403a so that mini-program 1403a can process the message content of the session message. Thus, mini-program 1403a can be quickly accessed and processed in the session from the session page. After mini-program 1403a obtains the message processing result, it can also feed back the message processing result to the business object.

[0209] The processing logic between the business object, the client, and the mini-program is illustrated here. Please refer to Figure 18, which is a schematic diagram of a message processing flow provided in an embodiment of this application. As shown in Figure 18, the business object can send or receive session messages of various data types (as shown in 1801a in Figure 18), such as image session messages, text session messages, video session messages, file session messages, etc. Furthermore, the business object can select the target session message on the client's session page. This can be a single selection or multiple selection, which is not limited here. Then, the client can respond to the trigger operation of the message processing control for the target session message (as shown in 1802a in Figure 18) to obtain a list of business programs that match the message data type of the target session message from the first server (as shown in 1803a in Figure 18), and then display the list of business programs (as shown in 1804a in Figure 18). This list of business programs can be a list composed of the aforementioned N business programs. Furthermore, in response to the trigger operation for the business program (as shown in 1805a in Figure 18), the client transmits the target message content of the target session message to the business program, thereby enabling the business program to process the target message content and obtain the target data processing result (as shown in 1806a in Figure 18). Then, the shareable result data is shared (as shown in 1807a in Figure 18).

[0210] The entire message processing process is illustrated here with reference to Figure 19, which is a timing interaction diagram of a message processing method provided in an embodiment of this application. As shown in Figure 19, the message processing method involves a terminal device, a first server, and a second server. The terminal device runs a client and may also include a target business program that depends on the client. The first server is the server corresponding to the client, and the second server is the server corresponding to the target business program. The first server and the second server can be the same server or different servers; this is not limited here. The message processing method can include: S1901, the client displays a message processing control for the target session message on the session page; S1902, in response to a trigger operation on the message processing control, the client sends a program matching request to the first server; S1903, the first server obtains N business programs that match the message data type of the target session message based on the program matching request; S1904, the first server returns program association information of the N business programs to the client; S1905, the client displays the N business programs that match the message data type of the target session message based on the program description information of the N business programs; S1906, in response to a trigger operation on the target business program among the N business programs, the client sends the target message content of the target session message to the second server; S1907, the second server processes the target message content; S1908, the second server returns message processing data to the target business program; S1909, the target business program displays the message processing data on the message processing page and processes the target session message on the message processing page.

[0211] In this embodiment, a message processing control for the selected target session message can be displayed on the session page. In response to a trigger operation on the message processing control, N business programs matching the target session message are displayed. Then, in response to a trigger operation on the target business program among the N business programs, the target business program can be accessed, and the data processing results can be displayed on the target business program's data processing page. Based on this, users can directly view the business programs available for processing the selected target session message on the session page, allowing them to flexibly select the business program needed for processing session messages according to their own needs. Users do not need to exit the session page to search for business programs, thus improving the flexibility and convenience of message processing through the mini-program. Furthermore, users do not need to manually upload the data to be processed; instead, the client directly passes the message content of the selected session message to the target business program for message processing, thereby improving message processing efficiency.

[0212] Please refer to Figure 20, which is a schematic diagram of the structure of a message processing device provided in an embodiment of this application. As shown in Figure 20, the message processing device 1 may be a computer program (including program code) running on a terminal device (e.g., the terminal device 11a mentioned above), and the terminal device runs a client. For example, the message processing device 1 is an application software; it is understood that the message processing device 1 can be used to execute the corresponding steps in the message processing method provided in the embodiment of this application. As shown in Figure 20, the message processing device 1 may include: a processing control display module 11, a program display module 12, a program triggering module 13, and a message processing module 14;

[0213] The processing control display module 11 is used to display message processing controls for a target session message on the session page; the target session message is a message selected from the session messages on the session page.

[0214] The program display module 12 is used to respond to the trigger operation of the message processing control and display N business programs that match the message data type of the target session message, where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the N business programs include the target business program for message processing of the target session message;

[0215] The program triggering module 13 is used to respond to a triggering operation on the target business program and display the message processing page of the target business program;

[0216] The message processing module 14 is used to process target session messages in the message processing page.

[0217] In one embodiment, the session page includes a first type of session page; the target session message includes a first session message displayed within the session messages of the first type of session page, and the first session message includes a single session message.

[0218] The control display module 11 is specifically used for:

[0219] In response to a message triggering operation on a first session message in a first type of session page, a first message association area associated with the first session message is displayed; the first message association area is determined based on the message display position of the first session message; the first session message associated with the first message association area is selected.

[0220] The first message handling control for the first session message is displayed in the first message association area; the first message handling control is a message handling control.

[0221] In one embodiment, the control display processing module 11 is specifically used for:

[0222] In response to a long press operation on the first conversation message in the first type of conversation page, the first message associated area for the first conversation message is displayed; a long press operation refers to the operation of pressing and holding the first conversation message for a duration that reaches the target duration threshold.

[0223] In one embodiment, the session page includes a second type of session page, where the session messages displayed are the same as those displayed in the first type of session page; the target session message includes a second session message displayed within the second type of session page, and the second session message includes at least one session message.

[0224] The control display module 11 is specifically used for:

[0225] In response to a session selection trigger operation for the first type of session page, a second session message is displayed on the second type of session page, along with a second message handling control for the second session message; the second message handling control is a message handling control.

[0226] In one embodiment, the control display processing module 11 is specifically used for:

[0227] In response to a message triggering operation for a session message displayed on a first type of session page, a second message association area associated with the session message triggered by the message triggering operation is displayed;

[0228] A session selection control for selecting sessions is displayed in the second message association area;

[0229] In response to a trigger action on the session selection control, a second session message is displayed on the second type of session page.

[0230] In one embodiment, each conversation message displayed in the second type of conversation page is associated with a corresponding message selection control; the conversation messages displayed in the second type of conversation page include trigger conversation messages and optional conversation messages that are different from trigger conversation messages. Trigger conversation messages are conversation messages triggered by message triggering operations; the second conversation messages are conversation messages that are selected in the second type of conversation page.

[0231] The message processing device 1 further includes: a message selection module 15;

[0232] Message selection module 15 is specifically used for:

[0233] In response to a trigger action on the session selection control, the triggered session message when the control is selected and the selectable session message when the control is unselected are displayed on the second type of session page.

[0234] In response to a trigger action on a message selection control for an unselected optional session message, the selected optional session message is displayed; both the triggering session message and the optional session message in the selected state belong to the second session message category.

[0235] In one embodiment, the message selection module 15 is further configured to:

[0236] In response to a deselection operation of the message selection control for a selected trigger session message, the trigger session message in an unselected state is displayed; the trigger session message in an unselected state does not belong to the second session message.

[0237] In one embodiment, the program display module 12 further includes:

[0238] When displaying N business programs, there are N program access entries corresponding to the N business programs displayed, and one program access entry is used to access one business program.

[0239] In each of the N program access entry points, the program description information of the corresponding business program is displayed; the program description information includes at least: program identifier and business description information.

[0240] In one embodiment, the program triggering module 13 is specifically used for:

[0241] When the target session message includes multiple session messages, a data processing prompt message is displayed in response to a trigger operation for the target business program. The data processing prompt message is displayed when there are session messages among the multiple session messages included in the target session message whose message data type does not match the target data type. The target data type is a data type that the business program can process. The data processing prompt message is used to prompt that the session messages whose message data type does not match the target data type should be filtered before message processing.

[0242] In response to the data processing confirmation operation for the data processing prompt information, the message processing page of the target business program is displayed; the message processing page is used to process the filtered session messages.

[0243] In one embodiment, the session page is the page where the first account and the second account conduct a session;

[0244] The message processing device 1 also includes: a data sharing module 16;

[0245] Data sharing module 16 is specifically used for:

[0246] The message processing page displays the message processing results; the message processing results refer to the results obtained after processing the target session message; the message processing results include shareable result data for the target session message;

[0247] Shareable results data is sent to a second account.

[0248] In one embodiment, the session page is the page where the first account and the second account conduct a session;

[0249] Data sharing module 16 is also used for:

[0250] The message processing page displays the message processing results; the message processing results refer to the results obtained after processing the target session message; the message processing results include shareable result data for the target session message;

[0251] On the message processing page, a result sharing control for the message processing result is displayed;

[0252] In response to a triggered action on the results sharing control, shareable results data is sent to a second account.

[0253] In one embodiment, the session page includes a first type of session page;

[0254] Data sharing module 16 is also used for:

[0255] In response to a session viewing operation on a first-type session page, a sharing session message containing shareable result data is displayed on the first-type session page; the message data type of the sharing session message is any of the following: text data type, image data type, file data type, video data type, or data type of a program link card used to view shareable result data.

[0256] In one embodiment, the program display module 12 is specifically used for:

[0257] In response to a trigger operation on a message processing control, a program matching request for the target session message is sent to the first server corresponding to the client. This allows the first server to query N business programs that match the message data type of the target session message based on the program matching request, and to obtain the program association information of the N business programs. The program association information includes the program description information of the business programs.

[0258] Upon receiving the program association information of N business programs returned by the server, based on the program description information of the N business programs, display the N business programs that match the message data type of the target session message.

[0259] In one embodiment, the program association information includes program access path information for N business programs;

[0260] Program trigger module 13 is specifically used for:

[0261] In response to a trigger operation targeting a target business program, a message processing request is determined based on the program access path information of the target business program and the target message content of the target session message. The message processing request is then sent to the second server corresponding to the target business program, so that the second server determines the message processing data for the target message content based on the message processing request.

[0262] Upon receiving message processing data from the second server, the message processing page of the target business program is displayed based on the message processing data.

[0263] In one embodiment, the data sharing module 16 is specifically used for:

[0264] Retrieve shareable data types for shareable results;

[0265] When multiple data sharing interfaces are obtained from the data sharing interface set, the target data sharing interface that matches the data type being shared is determined from among the multiple data sharing interfaces.

[0266] Call the target data sharing interface to send the shareable result data to the second account.

[0267] Please refer to Figure 21, which is a schematic diagram of the structure of a message processing device provided in an embodiment of this application. As shown in Figure 21, the message processing device 2 may be a computer program (including program code) running on a first server (e.g., server 100a) corresponding to the client, and the terminal device runs a client. For example, the message processing device 2 is an application software; it can be understood that the message processing device 2 can be used to execute the corresponding steps in the message processing method provided in the embodiment of this application. As shown in Figure 21, the message processing device 2 may include: a program matching module 21, an associated information acquisition module 22, and an information return module 23;

[0268] The program matching module 21 is used to receive a program matching request for a target session message sent by a terminal device running a client, and to obtain N business programs that match the message data type of the target session message based on the program matching request; N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the target session message is a message selected from the session messages on the session page;

[0269] The association information acquisition module 22 is used to acquire the program association information of N business programs; the program association information includes the program description information and program access path information of the business programs.

[0270] The information return module 23 is used to return the program association information of N business programs to the terminal device, so that the terminal device can display the N business programs that match the message data type of the target session message based on the program description information of the N business programs. In response to the trigger operation for the target business program among the N business programs, the terminal device can access the message processing page of the target business program based on the program access path information of the target business program, and perform message processing on the target session message in the message processing page.

[0271] In one embodiment, the client is a client logged in with a first account; the program matching request carries the account identifier of the first account;

[0272] Program matching module 21 is specifically used for:

[0273] Obtain the account identifier of the first account from the program matching request, and query the historical program set corresponding to the first account based on the account identifier; the historical program set includes at least one historical program that the first account has used;

[0274] If a collection of historical programs is found, the configuration file data of each historical program in the collection is obtained, and the data types that can be processed by each historical program are obtained from the configuration file data of each historical program.

[0275] For each historical program, the data type that can be processed is matched with the data type of the target session message to obtain the historical program whose data type can be processed matches the data type of the target session message.

[0276] Based on the historical procedures obtained through data type matching, N business procedures are identified that match the message data type of the target session message.

[0277] In one embodiment, the processable data type includes a first processable data type; the first processable data type is determined when the number of target session messages is single; the first processable data type contains a single data type;

[0278] Program matching module 21 is specifically used for:

[0279] In the historical procedure collection, find the historical procedure whose first processable data type matches the message data type of a single session message in the target session message;

[0280] The found historical programs are identified as those whose data types match the message data type of the target session message.

[0281] In one embodiment, the processable data type includes a second processable data type; the second processable data type is determined when there are multiple target session messages; the second processable data type contains at least one data type.

[0282] Program matching module 21 is specifically used for:

[0283] Retrieve the message data types corresponding to multiple session messages in the target session message;

[0284] In the historical program set, the historical programs that match each session message in the target session message are determined; the second processable data type of any historical program that matches any session message contains a data type that matches the message data type of that session message.

[0285] Based on the historical procedures matched against each session message in the target session message, the historical procedures that can process data types that match the message data types of the target session message are identified.

[0286] In one embodiment, the program matching module 21 is further configured to:

[0287] If no historical program is found that can handle data types that match the message data type of the target session message, at least one program to be recommended is obtained, and the configuration file data of each program to be recommended is obtained; the configuration file data of each program to be recommended includes the data types that can be handled.

[0288] For each program to be recommended, the data type that can be processed is matched with the data type of the target session message to obtain the program to be recommended whose data type can be processed matches the data type of the target session message.

[0289] Based on the data type matching results, N business programs are identified that match the message data type of the target session message.

[0290] Please refer to Figure 22, which is a schematic diagram of the structure of a computer device provided in an embodiment of this application. This computer device can be the aforementioned terminal device or server. As shown in Figure 22, the computer device 1000 may include: a processor 1001, a network interface 1004, and a memory 1005. Furthermore, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. The communication bus 1002 is used to implement communication between these components. The user interface 1003 may include a display screen and a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located remotely from the aforementioned processor 1001. As shown in Figure 22, the memory 1005, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0291] In the computer device 1000 shown in Figure 22, the network interface 1004 provides network communication functionality; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to execute the message processing method described in any of the corresponding embodiments above, which will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated.

[0292] Furthermore, it should be noted that this application also provides a computer-readable storage medium storing a computer program executed by the aforementioned message processing device 1 and message processing device 2. The computer program includes program instructions, which, when executed by the processor, enable the execution of the message processing method described in the preceding embodiments. Therefore, these descriptions will not be repeated here. Additionally, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer-readable storage medium involved in this application, please refer to the description of the method embodiments of this application.

[0293] The aforementioned computer-readable storage medium can be an internal storage unit of the message processing apparatus or computer device provided in any of the foregoing embodiments, such as a hard disk or memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium can include both internal and external storage units of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0294] Furthermore, it should be noted that this application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method provided in any of the preceding corresponding embodiments. Additionally, the beneficial effects of using the same method will not be repeated here. For technical details not disclosed in the embodiments of the computer program product or computer program involved in this application, please refer to the description of the method embodiments of this application.

[0295] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0296] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0297] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A message processing method, characterized in that, The method is executed by a terminal device running a client, and includes: Display message handling controls for the target session message on the session page; the target session message is a message selected from the session messages on the session page. In response to a trigger operation on the message processing control, N business programs matching the message data type of the target session message are displayed, where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; the N business programs include a target business program for processing the target session message; In response to a triggered operation on the target business program, the message processing page of the target business program is displayed; The target session message is processed on the message processing page.

2. The method according to claim 1, characterized in that, The session page includes a first type of session page; the target session message includes a first session message displayed in the session messages within the first type of session page, and the first session message includes a single session message. The step of displaying message processing controls for the target session message on the session page includes: In response to a message triggering operation on the first session message in the first type of session page, a first message association area associated with the first session message is displayed; the first message association area is determined based on the message display position of the first session message; the first session message associated with the first message association area is in a selected state; A first message processing control for the first session message is displayed in the first message association area; the first message processing control is a subset of the message processing control.

3. The method according to any one of claims 1-2, characterized in that, The step of displaying a first message association area associated with the first session message in response to a message triggering operation for the first session message in the first type of session page includes: In response to a long press operation on the first conversation message in the first type of conversation page, a first message association area for the first conversation message is displayed; the long press operation refers to the operation of pressing and holding the first conversation message for a duration that reaches a target duration threshold.

4. The method according to any one of claims 1-3, characterized in that, The conversation page includes a second type of conversation page, in which the conversation messages displayed are the same as those displayed on the first type of conversation page; the target conversation message includes a second conversation message in the conversation messages displayed in the second type of conversation page, and the second conversation message includes at least one conversation message. The step of displaying message processing controls for the target session message on the session page includes: In response to a session selection trigger operation for the first type of session page, the second session message is displayed on the second type of session page, and a second message processing control for the second session message is also displayed; the second message processing control is part of the message processing control.

5. The method according to any one of claims 1-4, characterized in that, The step of displaying the second session message on the second type of session page in response to a session selection trigger operation for the first type of session page includes: In response to a message triggering operation for a session message displayed on the first type of session page, a second message association area associated with the session message triggered by the message triggering operation is displayed; A session selection control for selecting sessions is displayed in the second message association area; In response to a triggering operation on the session selection control, the second session message is displayed on the second type of session page.

6. The method according to any one of claims 1-5, characterized in that, Each conversation message displayed on the second type of conversation page is associated with a corresponding message selection control; the conversation messages displayed on the second type of conversation page include trigger conversation messages and optional conversation messages that are different from the trigger conversation messages, wherein the trigger conversation messages are the conversation messages triggered by the message triggering operation; the second conversation messages are the conversation messages that are selected in the second type of conversation page. The step of displaying the second session message in the second type of session page in response to a trigger operation on the session selection control includes: In response to a trigger operation on the session selection control, the triggered session message in the selected state and the selectable session message in the unselected state are displayed on the second type of session page; In response to a trigger operation on a message selection control for an optional session message that is in the unselected state, the optional session message that is in the selected state is displayed; both the trigger session message and the optional session message that is in the selected state belong to the second session message.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: In response to a deselection operation of the message selection control for the triggered session message that is in the selected state, the triggered session message that is in the unselected state is displayed; the triggered session message that is in the unselected state does not belong to the second session message.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: When displaying the N business programs, N program access entries corresponding to the N business programs are displayed, and one program access entry is used to access one business program; In each of the N program access entry points, the program description information of the corresponding business program is displayed; the program description information includes at least: program identifier and business description information.

9. The method according to any one of claims 1-8, characterized in that, The step of displaying the message processing page of the target business application in response to a triggered operation includes: When the target session message includes multiple session messages, a data processing prompt is displayed in response to a trigger operation on the target business program. This prompt is displayed when there are session messages among the multiple session messages included in the target session message whose message data type does not match the target data type. The target data type is a data type that the business program can process. The data processing prompt is used to suggest filtering the session messages whose message data type does not match the target data type before processing them. In response to the data processing confirmation operation for the data processing prompt information, the message processing page of the target business program is displayed; the message processing page is used to process the filtered session messages.

10. The method according to any one of claims 1-9, characterized in that, The conversation page is the page where the first account and the second account conduct a conversation; The method further includes: The message processing page displays the message processing results; the message processing results refer to the results obtained after processing the target session message; the message processing results include shareable result data for the target session message; The shareable result data is sent to the second account.

11. The method according to any one of claims 1-10, characterized in that, The conversation page is the page where the first account and the second account conduct a conversation; The method further includes: The message processing page displays the message processing results; the message processing results refer to the results obtained after processing the target session message; the message processing results include shareable result data for the target session message; On the message processing page, a result sharing control for the message processing result is displayed; In response to a triggered operation on the result sharing control, the shareable result data is sent to the second account.

12. The method according to any one of claims 1-11, characterized in that, The session page includes a first type of session page; The method further includes: In response to a session viewing operation on the first type of session page, a sharing session message containing the shareable result data is displayed on the first type of session page; the message data type of the sharing session message is any one of the following: text data type, image data type, file data type, video data type, or data type of a program link card for viewing the shareable result data.

13. The method according to any one of claims 1-12, characterized in that, The step of displaying N business procedures that match the message data type of the target session message in response to a trigger operation on the message processing control includes: In response to a trigger operation on the message processing control, a program matching request for a target session message is sent to the first server corresponding to the client, so that the first server queries N business programs that match the message data type of the target session message based on the program matching request, and obtains the program association information of the N business programs; the program association information includes the program description information of the business programs; Upon receiving the program association information of the N business programs returned by the server, based on the program description information of the N business programs, the N business programs that match the message data type of the target session message are displayed.

14. The method according to any one of claims 1-13, characterized in that, The program association information includes the program access path information of the N business programs; The step of displaying the message processing page of the target business application in response to a triggered operation includes: In response to a trigger operation for the target business program, a message processing request is determined based on the program access path information of the target business program and the target message content of the target session message. The message processing request is then sent to the second server corresponding to the target business program, so that the second server determines message processing data for the target message content based on the message processing request. Upon receiving message processing data returned by the second server, the message processing page of the target business program is displayed based on the message processing data.

15. The method according to any one of claims 1-14, characterized in that, Sending the shareable result data to the second account includes: Obtain the shareable data type of the shareable result data; When multiple data sharing interfaces are obtained from the data sharing interface set, a target data sharing interface that matches the data type being shared is determined from the multiple data sharing interfaces. The target data sharing interface is invoked to send the shareable result data to the second account.

16. A message processing method, characterized in that, The method is executed by the first server corresponding to the client, and includes: The system receives a program matching request for a target session message from a terminal device running the client, and obtains N business programs that match the message data type of the target session message based on the program matching request; where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; and the target session message is a message selected from the session messages on the session page. Obtain the program association information of the N business programs; the program association information includes the program description information and program access path information of the business programs; The program association information of the N business programs is returned to the terminal device, so that the terminal device displays the N business programs that match the message data type of the target session message based on the program description information of the N business programs. In response to the trigger operation of the target business program among the N business programs, the terminal device accesses the message processing page of the target business program based on the program access path information of the target business program, and performs message processing on the target session message on the message processing page.

17. The method according to claim 16, characterized in that, The client is a client logged in with the first account; the program matching request carries the account identifier of the first account; The process of obtaining N business programs that match the message data type of the target session message based on the program matching request includes: Obtain the account identifier of the first account from the program matching request, and query the historical program set corresponding to the first account based on the account identifier; the historical program set includes at least one historical program that the first account has used; If the historical program set is found, the configuration file data of each historical program in the historical program set is obtained, and the processable data type of each historical program is obtained from the configuration file data of each historical program. The data type of each historical program is matched with the message data type of the target session message to obtain the historical program whose data type is matched with the message data type of the target session message. Based on the historical procedures obtained through data type matching, N business procedures are identified that match the message data type of the target session message.

18. The method according to any one of claims 16-17, characterized in that, The processable data type includes a first processable data type; the first processable data type is determined when the number of target session messages is single; the first processable data type contains a single data type; The step of matching the processable data type corresponding to each historical program with the message data type of the target session message to obtain historical programs whose processable data type matches the message data type of the target session message includes: In the historical program set, search for historical programs whose first processable data type matches the message data type of a single session message in the target session message; The found historical programs are identified as those whose data types match the message data type of the target session message.

19. The method according to any one of claims 16-18, characterized in that, The processable data type includes a second processable data type; the second processable data type is determined when the number of target session messages is multiple; the second processable data type contains at least one data type; The step of matching the processable data type corresponding to each historical program with the message data type of the target session message to obtain historical programs whose processable data type matches the message data type of the target session message includes: Retrieve the message data types corresponding to multiple session messages in the target session message; In the set of historical programs, the historical programs that match each session message in the target session message are determined; the second processable data type of the historical program matched by a session message contains a data type that matches the message data type of a session message; Based on the historical procedures matched with each session message in the target session message, a historical procedure whose data type can be processed matches the message data type of the target session message is determined.

20. The method according to any one of claims 16-19, characterized in that, The method further includes: If no historical program is found whose processable data type matches the message data type of the target session message, then at least one program to be recommended is obtained, and the configuration file data of each program to be recommended is obtained; the configuration file data of each program to be recommended includes the processable data type. The data type of each program to be recommended is matched with the data type of the target session message to obtain the program to be recommended whose data type is matched with the data type of the target session message. Based on the data type matching results, N business programs are identified that match the message data type of the target session message.

21. A message processing device, characterized in that, The device operates on a terminal device, and the terminal device runs a client, including: A message processing control display module is used to display message processing controls for a target session message on a session page; the target session message is a message selected from the session messages on the session page. The program display module is configured to, in response to a trigger operation on the message processing control, display N business programs that match the message data type of the target session message, where N is a positive integer; each of the N business programs is a subroutine that depends on the client for execution; the N business programs include a target business program for processing the target session message; The program triggering module is used to display the message processing page of the target business program in response to a triggering operation on the target business program; The message processing module is used to process the target session message in the message processing page.

22. A message processing device, characterized in that, The device operates on the first server corresponding to the client, including: The program matching module is used to receive a program matching request for a target session message sent by a terminal device running the client, and to obtain N business programs that match the message data type of the target session message based on the program matching request; where N is a positive integer; each of the N business programs is a subroutine that depends on the client to run; and the target session message is a message selected from the session messages on the session page. The association information acquisition module is used to acquire the program association information of the N business programs; the program association information includes the program description information and program access path information of the business programs; The information return module is used to return the program association information of the N business programs to the terminal device, so that the terminal device can display the N business programs that match the message data type of the target session message based on the program description information of the N business programs, and, in response to the trigger operation of the target business program among the N business programs, access the message processing page of the target business program based on the program access path information of the target business program, and perform message processing on the target session message on the message processing page.

23. A computer device, characterized in that, Including memory and processor; The memory is connected to the processor, the memory is used to store computer programs, and the processor is used to invoke the computer programs so that the computer device performs the method according to any one of claims 1-20.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted to be loaded and executed by a processor to cause a computer device having the processor to perform the method of any one of claims 1-20.

25. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the method according to any one of claims 1-20.

Images