HK40081317B - Message processing method, apparatus, computer device and storage medium - Google Patents

Description

Message processing methods, apparatus, computer equipment and storage media

Technical Field

This application relates to the field of computer technology, and in particular to a message processing method, apparatus, computer device, and storage medium.

Background Technology

With the development of computer technology, information transmission via the Internet has become increasingly common. For example, communication tools are used to establish sessions, enabling communication and exchange between at least two contacts. When a message sender needs to synchronize messages with members of more than one session, the sender needs to open sessions one by one to send messages. Especially when there are many messages, the sender needs to switch between different sessions, resulting in low message synchronization efficiency.

Summary of the Invention

Therefore, it is necessary to provide a method, apparatus, computer device, and storage medium that can improve the message synchronization efficiency of more than one session in order to address the above-mentioned technical problems.

A message processing method, the method comprising:

Enter a sub-application running within an instant messaging application, where the instant messaging application logs in using the target user identifier, and the sub-application authorizes login using the target user identifier;

The sub-application displays a session identifier corresponding to at least one session, wherein the at least one session is created by the instant messaging application and corresponds to the target user identifier;

In the information editing area that corresponds to the session identifier in each of the sub-applications, the group message input in response to the input operation is displayed;

In response to the sending operation of the mass message, the sub-application sends the mass message as a session message to the session in the instant messaging application corresponding to each session identifier.

A message processing apparatus, the apparatus comprising:

The entry module is used to enter a sub-application running within an instant messaging application, wherein the instant messaging application logs in using the target user identifier, and the sub-application authorizes login using the target user identifier;

The display module is used to display a session identifier corresponding to at least one session in the sub-application, wherein the at least one session is created by the instant messaging application and corresponds to the target user identifier;

The display module is also used to display the group message input in response to the input operation in the information editing area that is commonly corresponding to each session identifier in the sub-application;

The sending module is used to respond to the sending operation of the mass message by sending the mass message as a session message to the sessions in the instant messaging application corresponding to each session identifier through the sub-application.

In one embodiment, the display module is further configured to: display a list of session identifiers in the sub-application, the list of session identifiers including session identifiers of sessions in the instant messaging application corresponding to the target user identifier; and, in response to a selection operation of a session identifier in the list of session identifiers, determine at least one session identifier and display each of the session identifiers in the sub-application.

In one embodiment, the display module is further configured to: display a list of group session identifiers in the instant messaging application that consist of session identifiers of group sessions corresponding to the target user identifier; and, in response to a selection operation of a session identifier in the list of group session identifiers, determine at least one group session identifier and display each of the group session identifiers in the sub-application.

In one embodiment, the display module is further configured to: send a session acquisition request carrying the target user identifier to the application server corresponding to the instant messaging application; receive a session identifier corresponding to the target user identifier returned by the application server in response to the session acquisition request; and display the session identifier list according to the received session identifier.

In one embodiment, the message processing device further includes a determining module, which is configured to: determine the session message sending order of each session identifier according to the selection order of the session identifiers in the session identifier list; the display module is further configured to: in response to the sending operation of the mass message, send the mass message as session messages to the sessions corresponding to each session identifier in the instant messaging application in the order of the session message sending order of each session identifier through the sub-application.

In one embodiment, the display module is further configured to: when the determined at least one session identifier is a session identifier corresponding to more than one session, display a common session member identifier in the sub-application, wherein the common session member identifier is a user identifier corresponding to a session member that simultaneously belongs to the more than one session; the message processing device further includes a selection module, the selection module being configured to: in response to a selection operation on any common session member identifier among the common session member identifiers, use the selected common session member identifier as the sender of the mass message; the sending module is further configured to: when the selected common session member identifier matches the target user identifier, use the target user identifier as the sender, and send the mass message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, the message processing device further includes a sharing module, which is configured to: when the selected common session member identifier does not match the target user identifier, share the sub-application used to send the mass message to the session constructed by the selected common session member identifier and the target session member identifier.

In one embodiment, the display module is further configured to: when the selected common session member identifier matches the target user identifier, display the session identifier corresponding to each of the more than one session in the sub-application; display the group message input in response to the input operation in the information editing area commonly corresponding to each of the session identifiers in the sub-application; the sending module is further configured to: in response to the sending operation of the group message, use the selected common session member identifier as the sender of the group message, and send the group message as a session message to the sessions corresponding to each of the session identifiers in the instant messaging application through the sub-application.

In one embodiment, the display module is further configured to: obtain the session identifier corresponding to each of the more than one session; send a session member acquisition request to the application server of the instant messaging application, the session member acquisition request carrying each of the session identifiers; receive the session member identifiers corresponding to each of the session identifiers returned by the application server in response to the session member acquisition request; and determine the common session member identifier based on the session member identifiers corresponding to each of the session identifiers.

In one embodiment, the display module is further configured to: display an information editing area commonly corresponding to each of the session identifiers in the sub-application; obtain the mass message in response to an input operation in the information editing area; and display the mass message in the information editing area according to an information display format matching the information type of the mass message.

In one embodiment, the entry module is further configured to: enter a sub-application running in the instant messaging application, the instant messaging application being logged in with the target user identifier; display a login authorization window in the sub-application; and log in to the sub-application with the target user identifier in response to an authorization operation in the login authorization window.

In one embodiment, the display module is further configured to: when the session member corresponding to the target user identifier is removed from the session corresponding to the session identifier, display a prompt message in the sub-application regarding the failure to send the mass message in the session corresponding to the session identifier.

In one embodiment, the message processing device further includes a return module, which is further configured to: return from the sub-application to the instant messaging application logged in with the target user identifier; the display module is further configured to: display a session message including the mass message in the session corresponding to each of the session identifiers in the instant messaging application.

In one embodiment, the return module is further configured to: return from the sub-application to the instant messaging application logged in with the target user identifier; the display module is further configured to: display, in the sessions corresponding to each of the session identifiers in the instant messaging application, session messages including the mass messaging information pushed by the sub-application by other session member identifiers besides the target user identifier.

In one embodiment, the display module is further configured to: after sending the mass message as a session message to the instant messaging application logged in by the session member identifier corresponding to each session identifier, display the session message in the session page corresponding to each session identifier through the instant messaging application logged in by the session member identifier.

In one embodiment, the sending module is further configured to: send the mass message, the target user identifier, and each of the session identifiers to the sub-application server via the sub-application; forward the mass message, the target user identifier, and each of the session identifiers to the application server corresponding to the instant messaging application via the sub-application server; send the mass message as a session message to the session with each of the session identifiers via the application server; and display the session message including the mass message pushed by the target user identifier in the session page corresponding to each of the session identifiers via the instant messaging application logged in with the session member identifier among the session identifiers.

In one embodiment, the sending module is further configured to: display, through an instant messaging application logged in with the target user identifier, a session message including the mass message pushed by the target user identifier in a session page corresponding to each of the session identifiers.

A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

Enter a sub-application running within an instant messaging application, where the instant messaging application logs in using the target user identifier, and the sub-application authorizes login using the target user identifier;

The sub-application displays a session identifier corresponding to at least one session, wherein the at least one session is created by the instant messaging application and corresponds to the target user identifier;

In the information editing area that corresponds to the session identifier in each of the sub-applications, the group message input in response to the input operation is displayed;

In response to the sending operation of the mass message, the sub-application sends the mass message as a session message to the session in the instant messaging application corresponding to each session identifier.

A computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, performs the following steps:

Enter a sub-application running within an instant messaging application, where the instant messaging application logs in using the target user identifier, and the sub-application authorizes login using the target user identifier;

The sub-application displays a session identifier corresponding to at least one session, wherein the at least one session is created by the instant messaging application and corresponds to the target user identifier;

In the information editing area that corresponds to the session identifier in each of the sub-applications, the group message input in response to the input operation is displayed;

In response to the sending operation of the mass message, the sub-application sends the mass message as a session message to the session in the instant messaging application corresponding to each session identifier.

A computer program 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 steps of the above-described message processing method.

The aforementioned message processing method, apparatus, computer equipment, and storage medium, through a sub-application running in an instant messaging application and logged in with a target user identifier, display the session identifiers of at least a portion of the sessions in the instant messaging application corresponding to the target user identifier, as well as the information editing area commonly corresponding to each session identifier. In this way, the sub-application can independently edit group messages, thereby sending session messages including group messages to at least a portion of the sessions in the instant messaging application corresponding to the target user identifier. The sub-application enables message synchronization of more than one session in the instant messaging application, improving message synchronization efficiency.

Attached Figure Description

Figure 1 is an application environment diagram of a message processing method in one embodiment;

Figure 2 is a schematic diagram of the application page of the first instant messaging application in one embodiment;

Figure 3 is a schematic diagram of the application page of the second instant messaging application in one embodiment;

Figure 4 is a flowchart of a message processing method in one embodiment;

Figure 5 is a schematic diagram of the interface of the mass messaging record display page in one embodiment;

Figure 6 is a schematic diagram of the interface of the group messaging page in one embodiment;

Figure 7 is a schematic diagram of the interface of the group messaging page in another embodiment;

Figure 8 is a schematic diagram of a session page displayed by a receiving terminal through an instant messaging application in one embodiment;

Figure 9 is a schematic diagram of a session page displayed by the receiving terminal through an instant messaging application in another embodiment;

Figure 10 is a schematic diagram of a session page displayed by the receiving terminal through an instant messaging application in another embodiment;

Figure 11 is a schematic diagram of the interface of the group messaging page in another embodiment;

Figure 12 is a schematic diagram of the session identifier selection page in one embodiment;

Figure 13 is a schematic diagram of the session identifier selection page in another embodiment;

Figure 14 is a schematic diagram of the session message sending steps in one embodiment;

Figure 15 is a schematic diagram of the interface displaying common session member identifiers in a sub-application in one embodiment;

Figure 16 is a schematic diagram of the sharing prompt window interface in one embodiment;

Figure 17 is a schematic diagram of the interface displaying prompt information in a sub-application in one embodiment;

Figure 18 is a schematic diagram of a session page displayed by the receiving terminal through an instant messaging application in another embodiment;

Figure 19 is a schematic diagram of the architecture of a message processing system in one embodiment;

Figure 20 is a flowchart of a message processing method in another embodiment;

Figure 21 is a flowchart of a message processing method in another embodiment;

Figure 22 is a structural block diagram of a message processing device in one embodiment;

Figure 23 is an internal structure diagram of a computer device in one embodiment.

Detailed Implementation

To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

The message processing method provided in this application can be applied to the application environment shown in Figure 1. Referring to Figure 1, the application environment of this message processing method may include a terminal 110 and a server 120. The terminal 110 and the server 120 are connected via a network. The terminal 110 may be, but is not limited to, various personal computers, laptops, smartphones, tablets, portable wearable devices, etc. The server 120 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 (Content Delivery Network), and big data and artificial intelligence platforms. The terminal 110 and the server 120 may be directly or indirectly connected via wired or wireless communication, which is not limited herein.

In one embodiment, terminal 110 may include multiple terminals such as terminal 111, terminal 112, and terminal 113. Terminal 111 acts as the sending terminal for session messages, while terminals 112, 113, etc., act as receiving terminals for session messages. Terminal 111 has an instant messaging application installed. Within the instant messaging application's runtime environment, a sub-application for sending session messages to group sessions and/or contact sessions can run. Terminal 111 sends session messages to receiving terminals such as terminal 112 and terminal 113 through the sub-application running within the instant messaging application. Receiving terminals such as terminal 112 and terminal 113 can receive and display session messages through the same instant messaging application as terminal 111. Server 120 may include server 121 and server 122. Server 121 is the sub-application server corresponding to the sub-application, and server 122 is the application server corresponding to the instant messaging application. It is understood that at least one receiving terminal, such as terminal 112 or terminal 113, can also receive and display session messages through an instant messaging application different from that of terminal 111. Thus, server 120 also includes the application server corresponding to the instant messaging application installed on the at least one receiving terminal.

In one embodiment, terminal 111 enters a sub-application running within an instant messaging application. The instant messaging application is logged in using the target user identifier, and the sub-application is authorized to log in using the target user identifier. The sub-application displays at least one session identifier corresponding to each session, where at least one session is created by the instant messaging application and corresponds to the target user identifier. In the information editing area common to all session identifiers in the sub-application, a mass message input in response to an input operation is displayed. In response to the sending operation of the mass message, the sub-application sends the mass message, the target user identifier, and each session identifier to the sub-application server 121. The sub-application server 121 forwards the mass message, the target user identifier, and each session identifier to the application server 122 corresponding to the instant messaging application. The application server 122 sends the mass message as a session message to the session corresponding to each session identifier. In this way, receiving terminals such as terminal 112 and terminal 113 enter the instant messaging application logged in with the session member identifier. The session member identifier is the user identifier of the session member corresponding to each session identifier. In the session page corresponding to each session identifier, the session message including the group message pushed by the target user identifier is displayed. At the same time, terminal 111 returns from the sub-application to the instant messaging application logged in with the target user identifier. In the session corresponding to each session identifier, the session message including the group message pushed by the target user identifier is displayed.

In some embodiments, the sending terminal can also be the receiving terminal, and vice versa. For example, when terminal A and terminal B are having a social conversation, when terminal A sends a conversation message to terminal B, terminal A is the sending terminal and terminal B is the receiving terminal; when terminal B sends a conversation message to terminal A, terminal B is the sending terminal and terminal A is the receiving terminal.

The message processing method provided in this application can be executed by a message processing device provided in this application, or a computer device integrating the message processing device, wherein the message processing device can be implemented in hardware or software. The computer device can be the terminal 111 shown in FIG1.

The message processing method provided in this application can be applied to mass message sending scenarios in instant messaging applications, such as sending mass messages to group sessions, sending mass messages to contact sessions, or sending mass messages to both group sessions and contact sessions. A group session is a session created by more than two session members, and a contact session is a session created by two session members. Session members of a group session may include one or more social objects from an instant messaging application, and session members of a contact session may be social objects from the same or different instant messaging applications.

It should be noted that group sessions or contact sessions can be established for social contacts from different instant messaging applications, allowing social contacts from different instant messaging applications to enter the session based on their respective instant messaging applications without the need to download additional instant messaging applications. For example, group members in a group session may include social contacts from a first instant messaging application and social contacts from a second instant messaging application. Referring to Figure 2, this figure shows a schematic diagram of the session page interface of the first instant messaging application in one embodiment. Session members of the first instant messaging application, based on the first instant messaging application, publish session messages in the group session. Referring to Figure 3, this figure shows a schematic diagram of the session page interface of the second instant messaging application in one embodiment. Session members of the second instant messaging application, based on the second instant messaging application, receive session messages published by session members of the first instant messaging application in the group session.

For example, using the message processing method provided in this application embodiment, the sending terminal sends a group message to at least a portion of contact sessions and/or group sessions corresponding to the target user identifier in the instant messaging application, through a sub-application running in the instant messaging application logged in with the target user identifier and authorized to log in with the target user identifier. In this way, session members of at least a portion of contact sessions and/or group sessions corresponding to the target user identifier log in to the same or different instant messaging application as the target user identifier, and receive and display the group message pushed by the target user identifier.

In one embodiment, as shown in FIG4, a message processing method is provided. This embodiment mainly illustrates the method by applying it to a computer device (the sending terminal 111 in FIG1 above), and includes the following steps:

Step S402: Enter the sub-application running in the instant messaging application. The instant messaging application logs in with the target user's identity, and the sub-application authorizes login with the target user's identity.

Instant messaging applications are applications that provide instant messaging services to social contacts. Sub-applications are applications that run within the runtime environment provided by instant messaging applications, such as mini-programs.

In one embodiment, the sending terminal enters an instant messaging application logged in with the target user's identifier, displays a sub-application viewing entry, and, in response to a trigger operation on the sub-application viewing entry, displays a sub-application menu. In response to a selection operation on a sub-application within the menu, the sending terminal enters the sub-application corresponding to the selection operation. If the sub-application is not logged in, the sending terminal displays a login authorization window within the sub-application, and, in response to an authorization operation in the login authorization window, logs in to the sub-application with the target user's identifier. Here, the sub-application viewing entry is the entry point for viewing sub-applications within the instant messaging application, and the sub-application menu is the menu within the instant messaging application that displays sub-application options.

Step S404: Display the session identifier corresponding to at least one session in the sub-application. At least one session is a session created by the instant messaging application and corresponds to the target user identifier.

In one embodiment, the sending terminal sends a group message through a sub-application to a session in an instant messaging application corresponding to a target user identifier. The session in the instant messaging application corresponding to the target user identifier can be a group session and/or a contact session in which the target user identifier participates. Specifically, a group session is a session created by more than two session members, and a contact session is a session created by two session members. Session members in a group session can include social contacts from one or more instant messaging applications, and session members in a contact session can be social contacts from the same or different instant messaging applications.

In one embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. This application page may include the session identifier of at least a portion of the sessions corresponding to the target user identifier for this mass messaging session. Optionally, this application page may be a mass messaging record display page or a mass messaging session page for the sub-application, etc. The mass messaging record display page is used to display mass messaging records, and the mass messaging session page is used to send mass messaging session messages.

For example, referring to Figure 5, Figure 5 shows a schematic diagram of the interface of a mass messaging record display page in one embodiment. It can be seen that the mass messaging record display page may include a mass messaging record 502, which may include a mass messaging session identifier 504 and a mass messaging initiation entry point 506. The mass messaging session identifier 504 is the session identifier of at least a portion of the sessions corresponding to this mass messaging record and the target user identifier. The mass messaging initiation entry point 506 is used to enter the information editing area corresponding to this mass messaging record. Referring to Figure 6, Figure 6 shows a schematic diagram of the interface of a session message mass messaging page in one embodiment. It can be seen that the session message mass messaging page may include a mass messaging session identifier 602, which is the session identifier of at least a portion of the sessions corresponding to the target user identifier in this mass messaging session.

In another embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. The application page may include a list of session identifiers. In response to a selection operation of a session identifier in the list of session identifiers, at least one session identifier is determined, and each session identifier of the current group message is displayed in the sub-application.

In another embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. This application page may include a session identifier selection entry. In response to a trigger operation on the session identifier selection entry, a session identifier list is displayed. In response to a selection operation on a session identifier in the session identifier list, at least one session identifier is determined, and each session identifier of the current mass message is displayed in the sub-application. For example, continuing to refer to Figure 5, it can be seen that the mass message record display page may also include a session identifier selection entry 508. The user corresponding to the target user identifier can trigger the display of the session identifier list through the session identifier selection entry 508 and select the session identifier of the current mass message through the session identifier list.

Step S406: In the information editing area corresponding to each session identifier in the sub-application, the group message entered in response to the input operation is displayed.

The message editing area is used to receive input corresponding to the target user's identifier. Bulk messages are messages entered through this input and sent to multiple users. Bulk messages can be text, voice, images, emoticons, files, or audio/video files.

In one embodiment, the sending terminal enters the group messaging page of a sub-application. The group messaging page may include an information editing area corresponding to the common session identifier of the current group messaging sessions. The sending terminal receives input operations corresponding to the target user identifier through the information editing area, and in response to the input operations, displays the group messaging information in the information editing area. Referring again to Figure 6, the group messaging page may include an information editing area 604, through which the user corresponding to the target user identifier can input group messaging information.

In one embodiment, the group messaging page may include a session identifier for the current group messaging session, and may also include a delete control for the session identifier and/or an add entry for the session identifier. The delete control is an operation control for deleting the session identifier for the current group messaging session, and the add entry is an operation entry for adding the session identifier for the current group messaging session. In response to a trigger operation on the delete control, the sending terminal can promptly delete the corresponding session identifier; in response to a trigger operation on the add entry, the sending terminal can promptly add a session identifier. Referring to Figure 7, Figure 7 shows a schematic diagram of the group messaging page interface in another embodiment. It can be seen that the group messaging page may include a delete control 702 for the session identifier, allowing the user corresponding to the target user identifier to delete the corresponding session identifier. The group messaging page may also include an add entry 704 for the session identifier, allowing the user corresponding to the target user identifier to add a session identifier.

Step S408: In response to the sending operation of the mass message, the mass message is sent as a session message to the session corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, in response to the sending operation of mass messaging, the sending terminal uses the target user identifier as the sender and sends the mass messaging as a session message to the session corresponding to each session identifier in the instant messaging application through a sub-application.

In one embodiment, after the receiving terminal sends the mass message as a session message to the instant messaging application logged in by the session member ID corresponding to each session ID, the session message is displayed on the session page corresponding to each session ID through the instant messaging application logged in by the session member ID.

Here, the session member identifier is the user identifier of the session member corresponding to each session identifier. The receiving terminal enters the instant messaging application logged in with the session member identifier, and displays the session messages, including group messages, sent by the target user identifier through the sub-application on the session page corresponding to each session identifier.

In one embodiment, the session corresponding to the target user identifier in an instant messaging application can be a group session and/or a contact session in which the target user identifier participates. The session members of a group session can include social contacts from one or more instant messaging applications, and the session members of a contact session can be social contacts from the same or different instant messaging applications. Referring to Figure 8, Figure 8 shows a schematic diagram of a session page displayed by a receiving terminal through an instant messaging application in one embodiment. It can be seen that when the session member identifier and the target user identifier belong to the same instant messaging application, the session message pushed by the target user identifier, including group messaging information, is displayed on the session page of the receiving terminal. Referring to Figure 9, Figure 9 shows a schematic diagram of a session page displayed by a receiving terminal through an instant messaging application in another embodiment. It can be seen that when the session member identifier and the target user identifier belong to different instant messaging applications, the session message pushed by the target user identifier, including group messaging information, is displayed on the session page of the receiving terminal. The target user identifier can carry identifier information matching the instant messaging application corresponding to the target user identifier.

In one embodiment, the sending terminal returns from the sub-application to the instant messaging application logged in with the target user's identifier, and displays a session message including the mass message in the session corresponding to each session identifier in the instant messaging application.

In one embodiment, the sending terminal returns from the sub-application to the instant messaging application logged in with the target user's identifier. In the instant messaging application, within the sessions corresponding to each session identifier, the session messages, including mass messaging information, sent by the target user's identifier through the sub-application are displayed. Referring to Figure 10, which illustrates a schematic diagram of the session page displayed by the receiving terminal through the instant messaging application in another embodiment, it can be seen that the target user's identifier returns to the instant messaging application, and the session messages, including mass messaging information, sent by the target user's identifier through the sub-application are displayed in the sessions corresponding to each session identifier.

In one embodiment, the group messaging page does not display session messages sent by other session member identifiers within the sessions corresponding to each session identifier. The sending terminal returns from the sub-application to the instant messaging application logged in with the target user identifier. In the instant messaging application, the session messages sent by other session member identifiers, as well as the group messaging messages sent by the target user identifier through the sub-application, are displayed in the sessions corresponding to each session identifier. Referring to Figure 10, it can be seen that when the target user identifier returns to the instant messaging application, the session messages sent by other session member identifiers through the instant messaging application are displayed normally in the sessions corresponding to each session identifier.

In one embodiment, the group messaging page may include a group messaging display area, which is used to display group messaging messages sent by the sending terminal through a sub-application, including group messaging information. Referring again to Figure 6, the group messaging page may also include a group messaging display area 606, which displays group messaging messages sent by a target user identifier.

In one embodiment, the group messaging page displays session message prompts corresponding to each session identifier. These prompts can be used to indicate the status of session messages sent by other session members within the corresponding session, such as the number of messages. Referring to Figure 11, which shows a schematic diagram of the group messaging page interface in another embodiment, the group messaging page can be seen to include session message prompts 1102. Users corresponding to the target user identifier can use these prompts to learn about the session message status for each session identifier and promptly return to the instant messaging application to view the session messages.

The aforementioned message processing method, through a sub-application running within an instant messaging application and logged in with the target user identifier, displays the session identifiers of at least a portion of the sessions in the instant messaging application corresponding to the target user identifier, as well as the message editing area commonly corresponding to each session identifier. In this way, the sub-application can independently edit group messages, thereby sending session messages including group messages to at least a portion of the sessions in the instant messaging application corresponding to the target user identifier. The sub-application enables message synchronization of more than one session in the instant messaging application, improving message synchronization efficiency.

In one embodiment, displaying at least one session identifier corresponding to each session in a sub-application includes: displaying a list of session identifiers in the sub-application, the list of session identifiers including session identifiers of sessions in the instant messaging application corresponding to a target user identifier; and, in response to a selection operation of a session identifier in the list of session identifiers, determining at least one session identifier and displaying each session identifier in the sub-application.

In one embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. The application page may include a list of session identifiers. In response to a selection operation of a session identifier in the list of session identifiers, at least one session identifier is determined, and each session identifier of the current group message is displayed in the sub-application.

For example, referring to Figure 12, which shows a schematic diagram of the session identifier selection page in one embodiment, it can be seen that a session identifier list 1202 is displayed in the sub-application. The session identifiers in the session identifier list 1202 can be session identifiers of sessions corresponding to target user identifiers in instant messaging applications. Users corresponding to target user identifiers can select the session identifier for this group message from the session identifier list 1202.

Referring to Figure 13, which shows a schematic diagram of the session identifier selection page in another embodiment, it can be seen that a session identifier list 1308 is displayed in the sub-application. The session identifiers in the session identifier list 1308 can be session identifiers of a portion of sessions in the instant messaging application that correspond to the target user identifier. The user corresponding to the target user identifier can select the session identifier for this group message from the session identifier list 1308.

In another embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. The application page may include a session identifier selection entry. In response to a trigger operation on the session identifier selection entry, a list of session identifiers is displayed. In response to a selection operation on a session identifier in the list of session identifiers, at least one session identifier is determined, and each session identifier of this mass message is displayed in the sub-application.

For example, referring to Figure 5, the mass messaging record display page can also include a session identifier selection entry 508. Users corresponding to the target user identifier can trigger the display of the session identifier list through the session identifier selection entry 508 and select the session identifier of the current mass messaging session from the session identifier list.

Referring again to Figure 13, it can be seen that the sub-application displays the group session identifier selection entry 1302, the contact identifier selection entry 1304, and/or the mass messaging group selection entry 1306. Group session identifier selection entry 1302 is the entry point for selecting a group session identifier, contact identifier selection entry 1304 is the entry point for selecting a contact identifier, and mass messaging group selection entry 1306 is the entry point for selecting a mass messaging group. A mass messaging group can be a set of at least one session identifier established by a target user identifier. The user corresponding to the target user identifier can select the session identifier for this mass messaging message through group session identifier selection entry 1302, contact identifier selection entry 1304, mass messaging group selection entry 1306, and/or session identifier list 1308.

In this embodiment, the sub-application can independently select the session to send group messages, which increases the freedom of message synchronization for more than one session in instant messaging applications.

In one embodiment, displaying a session identifier list in a sub-application, the session identifier list including session identifiers of sessions in the instant messaging application corresponding to a target user identifier, includes: displaying a group session identifier list in the sub-application consisting of session identifiers of group sessions in the instant messaging application corresponding to the target user identifier; in response to a selection operation of a session identifier in the session identifier list, determining at least one session identifier and displaying each session identifier in the sub-application, includes: in response to a selection operation of a session identifier in the group session identifier list, determining at least one group session identifier and displaying each group session identifier in the sub-application.

In one embodiment, the sending terminal can send a session message, including mass messaging information, to at least a portion of group sessions in an instant messaging application that correspond to a target user identifier via a sub-application.

In one embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. The application page may include a list of group session identifiers. In response to the selection operation of the session identifier in the list of group session identifiers, at least one group session identifier is determined, and each group session identifier of this group message is displayed in the sub-application.

In another embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. The application page may include a session identifier selection entry. In response to a trigger operation on the session identifier selection entry, a group session identifier list is displayed. In response to a selection operation on a session identifier in the group session identifier list, at least one group session identifier is determined, and each group session identifier of this group message is displayed in the sub-application.

In this embodiment, a sub-application sends session messages to at least a portion of group sessions in the instant messaging application that correspond to the target user identifier, thereby achieving message synchronization of at least one group session in the instant messaging application.

In one embodiment, displaying a list of session identifiers in a sub-application includes: sending a session retrieval request carrying a target user identifier to the application server corresponding to the instant messaging application; receiving a session identifier corresponding to the target user identifier returned by the application server in response to the session retrieval request; and displaying a list of session identifiers based on the received session identifiers.

The session retrieval request is used to request the session identifier of the session corresponding to the target user identifier in the instant messaging application.

In one embodiment, the sending terminal sends a session acquisition request carrying the target user identifier to the sub-application server through a sub-application. The sub-application server then forwards the session acquisition request to the application server corresponding to the instant messaging application. In response to the session acquisition request, the application server looks up the session identifier corresponding to the target user identifier and returns the session identifier corresponding to the target user identifier to the sending terminal. The sending terminal then displays a list of session identifiers based on the received session identifiers.

In this embodiment, the sending terminal requests the session identifier corresponding to the target user identifier from the application server corresponding to the instant messaging application, so as to display the session identifier corresponding to the target user identifier in the sub-application.

In one embodiment, the method further includes: determining the session message sending order of each session identifier according to the selection order of the session identifiers in the session identifier list; and in response to the sending operation of the mass message, sending the mass message as session messages to the sessions corresponding to each session identifier in the instant messaging application through a sub-application, including: in response to the sending operation of the mass message, sending the mass message as session messages to the sessions corresponding to each session identifier in the instant messaging application in sequence through a sub-application according to the session message sending order of each session identifier.

In one embodiment, the sending terminal enters a sub-application authorized by the target user identifier and displays the application page of the sub-application. This application page may include a list of session identifiers. In response to a selection operation of a session identifier in the list, at least one session identifier is determined, and the session message sending order for each session identifier is determined according to the selection order of the session identifiers in the list. In response to a mass messaging operation, the sending terminal, through the sub-application, sequentially sends the mass messaging information as session messages to the sessions corresponding to each session identifier in the instant messaging application according to the session message sending order of each session identifier.

For example, referring to Figure 14, which illustrates a framework diagram of the session message sending steps in one embodiment. Assume the session message sending order for at least one session identifier is "Group A, Group B, Group C, ...", and the session message generation order is "Session Message 1, Session Message 2, ...". Then, session message 1 is sent sequentially according to the order "Group A, Group B, Group C, ...". After session message 1 is sent, session message 2 is sent sequentially according to the order "Group A, Group B, Group C, ...", until all session messages are sent. It is understood that the instant messaging applications logged in by different session member identifiers may receive the same session message at different times.

In this embodiment, the order in which session identifiers are selected from the list of session identifiers is determined, and the session messages are sent sequentially to the sessions corresponding to each session identifier in the instant messaging application according to the order in which the session messages are sent, thereby achieving orderly mass sending of session messages and avoiding missed messages.

In one embodiment, after determining at least one session identifier in response to a selection operation of session identifiers in the session identifier list, the method further includes: when the determined at least one session identifier is a session identifier corresponding to more than one session, displaying a common session member identifier in a sub-application, wherein the common session member identifier is a user identifier corresponding to a session member that simultaneously belongs to more than one session; in response to a selection operation of any common session member identifier among the common session member identifiers, using the selected common session member identifier as the sender of the mass message; and in response to a mass message sending operation, sending the mass message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application, including: when the selected common session member identifier matches a target user identifier, using the target user identifier as the sender, sending the mass message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application.

Among them, the common session member identifier is a session member identifier that exists simultaneously in the sessions corresponding to each session identifier.

In one embodiment, the sending terminal obtains the session member identifiers corresponding to each session identifier, determines the common session member identifier based on the session member identifiers corresponding to each session identifier, and displays the common session member identifier. Referring to Figure 15, Figure 15 shows a schematic diagram of the interface for displaying the common session member identifier in a sub-application in one embodiment. It can be seen that the sending terminal displays the common session member identifier 1502 in the sub-application.

In one embodiment, in response to the selection operation of any common session member identifier among the common session member identifiers, the sending terminal uses the session member corresponding to the selected common session member identifier as the sender of the mass message. When the selected common session member identifier is a target user identifier, the target user identifier is used as the sender, and the mass message is sent as a session message to the session corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, the method further includes: when the selected common session member identifier does not match the target user identifier, sharing the sub-application used for mass messaging to the session constructed by the selected common session member identifier and the target session member identifier.

In one embodiment, when the selected common session member identifier is not the target user identifier, a sharing prompt window is displayed. This sharing prompt window is used to share the sub-application to the session constructed by the selected common session member identifier and the target session member identifier, so that the selected common session member identifier can log in to the sub-application and send group session messages. Referring to Figure 16, Figure 16 shows a schematic diagram of the sharing prompt window interface in one embodiment. It can be seen that the sending terminal displays the sharing prompt window 1602 in the sub-application, and the user corresponding to the target user identifier can share the sub-program with the session member corresponding to the selected common session member identifier through the sharing prompt window 1602.

In one embodiment, the method further includes: when the selected common session member identifier matches the target user identifier, displaying the session identifiers corresponding to more than one session in the sub-application; displaying the group message entered in response to the input operation in the information editing area commonly corresponding to each session identifier in the sub-application; and in response to the sending operation of the group message, using the selected common session member identifier as the sender of the group message, sending the group message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, when the selected common session member identifier is the target user identifier, the sending terminal displays a message mass sending page. The message mass sending page may include a session identifier corresponding to more than one session and a message editing area corresponding to each session identifier. The selected common session member identifier is used as the sender of the mass message, and the mass message is sent as a session message to the session corresponding to each session identifier in the instant messaging application through the message mass sending page.

In this embodiment, the ability of sub-applications to select the sender of session messages increases the flexibility of message synchronization for more than one session in instant messaging applications.

In one embodiment, the method further includes: obtaining session identifiers corresponding to more than one session; sending a session member acquisition request to the application server of the instant messaging application, the session member acquisition request carrying each session identifier; receiving session member identifiers corresponding to each session identifier returned by the application server in response to the session member acquisition request; and determining a common session member identifier based on the session member identifiers corresponding to each session identifier.

The session member retrieval request is used to request the session member identifier corresponding to each session identifier in the instant messaging application.

In one embodiment, the sending terminal sends a session member retrieval request carrying each session identifier to the sub-application server through a sub-application. The sub-application server then forwards the session member retrieval request to the application server corresponding to the instant messaging application. In response to the session member retrieval request, the application server looks up the session member identifier corresponding to each session identifier and returns the session member identifier corresponding to each session identifier to the sending terminal. The sending terminal determines the common session member identifier based on the session member identifier corresponding to each session identifier.

In this embodiment, the sending terminal requests the session member identifiers corresponding to each session identifier from the application server corresponding to the instant messaging application, so as to determine the sender of the session message from the session member identifiers corresponding to each session identifier.

In one embodiment, displaying a mass message in response to an input operation in a message editing area common to each session identifier in a sub-application includes: displaying a message editing area common to each session identifier in the sub-application; obtaining the mass message in response to an input operation in the message editing area; and displaying the mass message in the message editing area according to a message display format matching the message type of the mass message.

Among them, the information display format is the information display method that matches the information type of the mass-sent information.

In one embodiment, the mass message can be text, voice, image, emoji, file, or audio/video, etc.

In one embodiment, the receiving terminal responds to an input operation in the information editing area, acquires the mass message, and displays the mass message in the information editing area according to an information display format that matches the information type of the mass message.

In this embodiment, group sending of conversation messages of various information types can be supported, improving the applicability of group sending of conversation messages in instant messaging applications.

In one embodiment, the method further includes: entering a sub-application running in an instant messaging application, the instant messaging application being logged in with the target user identifier; displaying a login authorization window in the sub-application; and logging into the sub-application with the target user identifier in response to an authorization operation in the login authorization window.

In one embodiment, the sending terminal enters an instant messaging application logged in with the target user's identifier, displays an entry point for viewing sub-applications, and, in response to a trigger operation on the sub-application viewing entry point, displays a sub-application menu. In response to a selection operation within the sub-application menu, the sending terminal enters the sub-application corresponding to the selection operation. If the sub-application is not logged in, the sending terminal displays a login authorization window within the sub-application, and, in response to an authorization operation in the login authorization window, logs in to the sub-application with the target user's identifier. It can be understood that after authorizing login to the sub-application with the target user's identifier, the login status can be maintained for a specified period, avoiding the need for authorization login every time the sub-application is accessed, thus saving login steps.

In this embodiment, the sub-applications in the instant messaging application are authorized to log in using the target user's identifier. After logging into the instant messaging application, the user can quickly log into the sub-applications.

In one embodiment, the method further includes: when the session member corresponding to the target user identifier is removed from the session corresponding to the session identifier, displaying a prompt message in the sub-application about the failure to send the mass message in the session corresponding to the session identifier.

In one embodiment, the sending terminal enters a sub-application running within an instant messaging application and is authorized to log in with the target user's identifier. The sub-application then sends a group message to at least a portion of the sessions within the instant messaging application corresponding to the target user's identifier. When the user corresponding to the target user's identifier is removed from the session corresponding to that session identifier, the sending terminal displays a message in the sub-application indicating that the group message failed to be sent within that session. It is understood that the removal of the user from the session can occur when the group session corresponding to the session identifier is disbanded, when the user corresponding to the target user's identifier is removed from the group session, or when the user is deleted or blocked by a contact.

For example, referring to Figure 17, which shows a schematic diagram of an interface displaying prompt information in a sub-application in one embodiment. As can be seen, when the user corresponding to the target user identifier is removed from the group session, prompt information 1702 is displayed to indicate that the user corresponding to the target user identifier failed to send session messages in the group session.

In this embodiment, when sending a group message to a session in an instant messaging application through a sub-application, if the user corresponding to the target user identifier is removed from the session, a prompt message is displayed in the sub-application in a timely manner to indicate that the session message sent to the user corresponding to the target user identifier in that session has failed.

In one embodiment, the method further includes: returning from the sub-application to the instant messaging application logged in with the target user identifier; and displaying, in the sessions corresponding to each session identifier in the instant messaging application, session messages including mass messaging information pushed by the sub-application by other session member identifiers besides the target user identifier.

In one embodiment, the sending terminal returns from the sub-application to the instant messaging application logged in with the target user identifier. In the sessions corresponding to each session identifier within the instant messaging application, session messages including mass messaging information pushed by other session member identifiers (excluding the target user identifier) through the sub-application are displayed. Referring to Figure 18, Figure 18 shows a schematic diagram of the session page displayed by the receiving terminal through the instant messaging application in another embodiment. Message 1802 is a session message including mass messaging information pushed by other session member identifiers through the sub-application. It can be seen that when the target user identifier returns to the instant messaging application, the session messages including mass messaging information sent by the target user identifier through the sub-application are displayed in the sessions corresponding to each session identifier. Session messages including mass messaging information sent by other session member identifiers through the sub-application, as well as session messages sent by other session member identifiers through the instant messaging application, are also displayed normally.

In this embodiment, all members of the session can push session messages, including group messages, through the sub-application, and the group messages sent by the members of the session do not interfere with each other.

In one embodiment, sending mass messages as session messages to sessions corresponding to each session identifier in an instant messaging application via a sub-application includes: sending the mass messages, target user identifiers, and session identifiers to a sub-application server via the sub-application; forwarding the mass messages, target user identifiers, and session identifiers to the application server corresponding to the instant messaging application via the sub-application server; and displaying the session messages, including the mass messages, pushed by the target user identifier in the session page corresponding to each session identifier in the instant messaging application logged in with the session member identifier among the session identifiers.

In one embodiment, referring to Figure 19, which illustrates the architecture of a message processing system in one embodiment, it can be seen that the sending terminal can push the session message sent by the target user identifier to the instant messaging application logged in with the session member identifier through the sub-application, the sub-application server, and the application server corresponding to the instant messaging application. It can be understood that the session member identifier may also include the target user identifier.

In one embodiment, the sending terminal sends the mass message, the target user identifier, and each session identifier to the sub-application server through a sub-application. The sub-application server then forwards the mass message, the target user identifier, and each session identifier to the application server corresponding to the instant messaging application. The application server then sends the mass message as a session message to the sessions corresponding to each session identifier. The instant messaging application, which is logged in using the session member identifier in each session identifier, displays the session message, including the mass message, pushed by the target user identifier in the session page corresponding to each session identifier.

In one embodiment, the sending terminal sends the mass messaging information as a session message to the sessions with each session identifier through the application server. The instant messaging application logged in with the target user identifier displays the session message, which includes the mass messaging information, pushed by the target user identifier in the session page corresponding to each session identifier.

In this embodiment, the sending terminal pushes the session message sent by the target user identifier to the instant messaging application logged in with the session member identifier through the sub-application, the sub-application server and the application server corresponding to the instant messaging application, thereby realizing message synchronization of more than one session in the instant messaging application.

In one embodiment, as shown in Figure 20, a message processing method is provided. This embodiment can be applied to message grouping scenarios in instant messaging applications, such as sending group messages to group conversations, sending group messages to contact conversations, or sending group messages to both group conversations and contact conversations. The conversation members of a group conversation may include one or more social objects from an instant messaging application, and the conversation members of a contact conversation may be social objects from the same or different instant messaging applications. This embodiment mainly uses the application of this method to a computer device (the sending terminal 111 in Figure 1 above) as an example, and includes the following steps:

Step S2002: Enter the sub-application running in the instant messaging application. The instant messaging application logs in with the target user's identity, and the sub-application authorizes login with the target user's identity.

Step S2004: Display a session identifier list in the sub-application. The session identifier list includes session identifiers of sessions in the instant messaging application that correspond to the target user identifier. In response to the selection operation of session identifiers in the session identifier list, determine more than one session identifier and display each session identifier in the sub-application.

Step S2006: Determine the session message sending order for each session identifier according to the selection order of the session identifiers in the session identifier list.

Step S2008: Display the common session member identifier in the sub-application. The common session member identifier is the user identifier corresponding to a session member who belongs to more than one session at the same time. In response to the selection operation of any common session member identifier, the session member corresponding to the selected common session member identifier is used as the sender of the group message.

Step S2010: When the selected common session member identifier matches the target user identifier, display the session identifiers corresponding to more than one session in the sub-application; display the information editing area corresponding to each session identifier in the sub-application; in response to the input operation in the information editing area, obtain the mass message; and display the mass message in the information editing area according to the information display format that matches the information type of the mass message.

In one embodiment, when the selected common session member identifier does not match the target user identifier, the sub-application used for sending mass messages is shared to the session constructed by the selected common session member identifier and the target session member identifier.

In step S2012, in response to the sending operation of the mass message, the target user identifier is used as the sender, and the sub-application sends the mass message as a session message to the session corresponding to each session identifier in the instant messaging application in the order of sending session messages of each session identifier.

In one embodiment, after the sending terminal sends the mass messaging information as a session message to the instant messaging application logged in by the session member identifier corresponding to each session identifier, the receiving terminal displays the session message in the session page corresponding to each session identifier through the instant messaging application logged in by the session member identifier. The sending terminal returns from the sub-application to the instant messaging application logged in by the target user identifier, and displays the session message including the mass messaging information in the session corresponding to each session identifier in the instant messaging application.

The aforementioned message processing method, through a sub-application running within an instant messaging application and logged in with the target user's identifier, displays the session identifiers of at least a portion of the sessions within the instant messaging application corresponding to the target user's identifier, as well as the message editing area shared by all session identifiers. This allows the sub-application to independently edit group messages, thereby sending session messages, including group messages, to at least a portion of the sessions within the instant messaging application corresponding to the target user's identifier. The sub-application enables message synchronization across multiple sessions within the instant messaging application, improving message synchronization efficiency. Furthermore, this information synchronization method avoids missed or incorrect sending of session messages.

In one embodiment, as shown in FIG21, a message processing method is provided. This embodiment can be applied to sending group messages to a group chat in an instant messaging application. The members of the group chat may include one or more social contacts from the instant messaging application. This embodiment mainly illustrates the method by applying it to a computer device (the sending terminal 111 in FIG1 above), and includes the following steps:

Step S2102: Enter the sub-application running in the instant messaging application. The instant messaging application logs in with the target user's identity, and the sub-application authorizes login with the target user's identity.

Step S2104: Display a list of group session identifiers in the sub-application, which consists of session identifiers of group sessions corresponding to the target user identifier in the instant messaging application; in response to the selection operation of the session identifiers in the list of group session identifiers, determine more than one group session identifier and display each group session identifier in the sub-application.

Step S2106: Determine the message sending order for each group session identifier according to the selection order of the group session identifiers in the group session identifier list.

Step S2108: Display the common session member identifier in the sub-application. The common session member identifier is the user identifier corresponding to a session member who belongs to more than one group session at the same time. In response to the selection operation of any common session member identifier, the session member corresponding to the selected common session member identifier is used as the sender of the group message.

Step S2110: When the selected common session member identifier matches the target user identifier, display the group session identifiers corresponding to more than one group session in the sub-application; display the information editing area corresponding to the common group session identifiers in the sub-application; in response to the input operation in the information editing area, obtain the group message; and display the group message in the information editing area according to the information display format that matches the information type of the group message.

In one embodiment, when the selected common session member identifier does not match the target user identifier, the sub-application used for sending mass messages is shared to the session constructed by the selected common session member identifier and the target session member identifier.

Step S2112: In response to the sending operation of the mass message, the target user identifier is used as the sender, and the sub-application sends the mass message as a session message to the group session corresponding to each group session identifier in the instant messaging application in the order of the session message sending of each group session identifier.

In one embodiment, after the sending terminal sends the mass messaging information as a session message to the instant messaging application logged in by the session member identifier corresponding to each group session identifier, the receiving terminal displays the session message in the session page corresponding to each group session identifier through the instant messaging application logged in by the session member identifier. The sending terminal returns from the sub-application to the instant messaging application logged in by the target user identifier, and displays the session message including the mass messaging information in the group session corresponding to each group session identifier in the instant messaging application.

The aforementioned message processing method, through a sub-application running within the instant messaging application and logged in with the target user identifier, displays the group session identifiers of at least a portion of the group sessions in the instant messaging application corresponding to the target user identifier, as well as the message editing area shared by all group session identifiers. In this way, the sub-application can independently edit group messages, thereby sending session messages including group messages to at least a portion of the group sessions in the instant messaging application corresponding to the target user identifier. The sub-application enables message synchronization of more than one group session in the instant messaging application, improving message synchronization efficiency. Furthermore, this information synchronization method can avoid missed or incorrect sending of session messages.

It should be understood that although the steps in the flowcharts of Figures 4, 20, and 21 are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in Figures 4, 20, and 21 may include more than one step or more than one stage. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the steps or stages of other steps.

In one embodiment, as shown in FIG22, a message processing device is provided. This device may employ software modules or hardware modules, or a combination of both, as part of a computer device. Specifically, the device includes: an input module 2202, a display module 2204, and a sending module 2206, wherein:

Enter module 2202 is used to enter a sub-application running in an instant messaging application. The instant messaging application logs in with the target user's identity, and the sub-application authorizes login with the target user's identity.

Display module 2204 is used to display the session identifier corresponding to at least one session in the sub-application, wherein at least one session is a session created by an instant messaging application and corresponds to a target user identifier;

The display module 2204 is also used to display the group message input in response to the input operation in the information editing area that is common to each session identifier in the sub-application;

The sending module 2206 is used to respond to the sending operation of the mass message and send the mass message as a session message to the session corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, the display module 2204 is further configured to: display a list of session identifiers in a sub-application, the list of session identifiers including session identifiers of sessions in the instant messaging application corresponding to the target user identifier; and, in response to a selection operation of a session identifier in the list of session identifiers, determine at least one session identifier and display each session identifier in the sub-application.

In one embodiment, the display module 2204 is further configured to: display a list of group session identifiers in the instant messaging application that consist of session identifiers of group sessions corresponding to the target user identifier; and, in response to a selection operation of a session identifier in the list of group session identifiers, determine at least one group session identifier and display each group session identifier in the sub-application.

In one embodiment, the display module 2204 is further configured to: send a session acquisition request carrying a target user identifier to the application server corresponding to the instant messaging application; receive a session identifier corresponding to the target user identifier returned by the application server in response to the session acquisition request; and display a list of session identifiers based on the received session identifiers.

In one embodiment, the message processing device further includes a determining module, which is configured to: determine the session message sending order of each session identifier according to the selection order of the session identifiers in the session identifier list; the display module 2204 is further configured to: in response to the sending operation of the mass message, send the mass message as session messages to the sessions corresponding to each session identifier in the instant messaging application in sequence according to the session message sending order of each session identifier through the sub-application.

In one embodiment, the display module 2204 is further configured to: when the determined at least one session identifier is a session identifier corresponding to more than one session, display a common session member identifier in the sub-application, wherein the common session member identifier is a user identifier corresponding to a session member that simultaneously belongs to more than one session; the message processing device further includes a selection module, configured to: in response to a selection operation on any common session member identifier among the common session member identifiers, use the selected common session member identifier as the sender of the group message; the sending module 2206 is further configured to: when the selected common session member identifier matches a target user identifier, use the target user identifier as the sender, and send the group message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, the message processing apparatus further includes a sharing module, which is configured to: when the selected common session member identifier does not match the target user identifier, share the sub-application used for sending mass messages to the session constructed by the selected common session member identifier and the target session member identifier.

In one embodiment, the display module 2204 is further configured to: when the selected common session member identifier matches the target user identifier, display the session identifiers corresponding to more than one session in the sub-application; and display the group message input in response to the input operation in the information editing area commonly corresponding to each session identifier in the sub-application; the sending module 2206 is further configured to: in response to the sending operation of the group message, use the selected common session member identifier as the sender of the group message, and send the group message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application.

In one embodiment, the display module 2204 is further configured to: obtain session identifiers corresponding to more than one session; send a session member acquisition request to the application server of the instant messaging application, the session member acquisition request carrying each session identifier; receive the session member identifiers corresponding to each session identifier returned by the application server in response to the session member acquisition request; and determine a common session member identifier based on the session member identifiers corresponding to each session identifier.

In one embodiment, the display module 2204 is further configured to: display a message editing area common to each session identifier in a sub-application; obtain mass-sent messages in response to input operations in the message editing area; and display the mass-sent messages in the message editing area according to a message display format that matches the message type of the mass-sent messages.

In one embodiment, the entry module 2202 is further configured to: enter a sub-application running in an instant messaging application, the instant messaging application being logged in with the target user identifier; display a login authorization window in the sub-application; and log in to the sub-application with the target user identifier in response to an authorization operation in the login authorization window.

In one embodiment, the display module 2204 is further configured to: display a prompt message in the sub-application about the failure to send the mass message in the session corresponding to the session identifier when the session member corresponding to the target user identifier is removed from the session corresponding to the session identifier.

In one embodiment, the message processing apparatus further includes a return module, which is also configured to: return from the sub-application to the instant messaging application logged in with the target user identifier; and the display module 2204 is further configured to: display a session message including mass messaging information in the session corresponding to each session identifier in the instant messaging application.

In one embodiment, the return module is further configured to: return from the sub-application to the instant messaging application logged in with the target user identifier; the display module 2204 is further configured to: display, in the sessions corresponding to each session identifier in the instant messaging application, session messages including group messages pushed by the sub-application for other session member identifiers besides the target user identifier.

In one embodiment, the display module 2204 is further configured to: after sending the mass message as a session message to the instant messaging application logged in by the session member ID corresponding to each session ID, display the session message in the session page corresponding to each session ID through the instant messaging application logged in by the session member ID.

In one embodiment, the sending module 2206 is further configured to: send the mass message, the target user identifier, and each session identifier to the sub-application server via the sub-application; forward the mass message, the target user identifier, and each session identifier to the application server corresponding to the instant messaging application via the sub-application server; send the mass message as a session message to the session with each session identifier via the application server; and display the session message including the mass message pushed by the target user identifier in the session page corresponding to each session identifier via the instant messaging application logged in with the session member identifier in each session identifier.

In one embodiment, the sending module 2206 is further configured to: display, through an instant messaging application logged in with a target user identifier, a session message including group messaging information pushed by the target user identifier in the session page corresponding to each session identifier.

For specific limitations regarding the message processing device, please refer to the limitations on the message processing method above, which will not be repeated here. Each module in the aforementioned message processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in hardware or independently of the processor in the computer device, or stored in software in the memory of the computer device, so that the processor can call and execute the operations corresponding to each module.

In the aforementioned message processing device, a sub-application running in the instant messaging application and logged in with the target user identifier displays the session identifiers of at least a portion of the sessions in the instant messaging application corresponding to the target user identifier, as well as the information editing area commonly corresponding to each session identifier. In this way, the sub-application can independently edit group messages, thereby sending session messages including group messages to at least a portion of the sessions in the instant messaging application corresponding to the target user identifier. The sub-application enables message synchronization of more than one session in the instant messaging application, improving message synchronization efficiency.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in Figure 23. The computer device includes a processor, memory, network interface, and display screen connected via a system bus. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for wired or wireless network communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a message processing method. The display screen of the computer device may be a liquid crystal display (LCD) or an e-ink display.

Those skilled in the art will understand that the structure shown in Figure 23 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including 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 steps in the above method embodiments.

Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims (36)

1. A message processing method, characterized in that the method comprises: Enter a sub-application running within an instant messaging application. The sub-application runs in the runtime environment provided by the instant messaging application. The instant messaging application logs in with the target user identifier, and the sub-application is authorized to log in with the target user identifier. The sub-application is used to send session messages to the session corresponding to the target user identifier. The session identifiers corresponding to multiple sessions are displayed on the session message mass sending page of the sub-application. These multiple sessions are created by the instant messaging application and correspond to the target user identifier. Each session is a session in which the target user identifier participates. In the information editing area corresponding to each of the aforementioned session identifiers on the group message page, the group message input in response to the input operation is displayed; In response to the sending operation of the mass message, the target user identifier is used as the sender, and the mass message is sent as a session message to the session corresponding to each session identifier in the instant messaging application through the sub-application. 2. The method according to claim 1, characterized in that, displaying the session identifiers corresponding to each of the multiple sessions in the group message sending page of the sub-application includes: The sub-application displays a list of session identifiers, which includes session identifiers of the sessions in the instant messaging application that correspond to the target user identifier. In response to a selection operation of a session identifier in the list of session identifiers, multiple session identifiers are determined and each session identifier is displayed in the sub-application. 3. The method according to claim 2, characterized in that, the step of displaying a session identifier list in the sub-application, the session identifier list including session identifiers of the sessions corresponding to the target user identifier in the instant messaging application, includes: The sub-application displays a list of group session identifiers, which are composed of group session identifiers corresponding to the target user identifier in the instant messaging application. The step of responding to a selection operation of a session identifier in the session identifier list, determining multiple session identifiers, and displaying each session identifier in the sub-application includes: In response to a selection operation of a session identifier in the group session identifier list, multiple group session identifiers are determined and each of the group session identifiers is displayed in the sub-application. 4. The method according to claim 2, wherein displaying the session identifier list in the sub-application includes: Send a session acquisition request carrying the target user identifier to the application server corresponding to the instant messaging application; Receive the session identifier corresponding to the target user identifier returned by the application server in response to the session acquisition request; The list of session identifiers is displayed based on the received session identifiers. 5. The method according to claim 2, characterized in that the method further comprises: The order in which session messages are sent for each session identifier is determined according to the selection order of the session identifiers in the list of session identifiers; The step of responding to the sending operation of the mass message, using the target user identifier as the sender, and sending the mass message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application, includes: In response to the sending operation of the mass message, the target user identifier is used as the sender, and the sub-application sends the mass message as a session message to the session corresponding to each session identifier in the instant messaging application in the order of sending session messages of each session identifier. 6. The method according to claim 2, characterized in that, after determining multiple session identifiers in response to a selection operation of session identifiers in the session identifier list, the method further includes: The sub-application displays a common session member identifier, which is a user identifier corresponding to a session member who simultaneously belongs to the multiple sessions; In response to the selection operation of any common session member identifier among the common session member identifiers, the session member corresponding to the selected common session member identifier is used as the sender of the mass message; The step of responding to the sending operation of the mass message, using the target user identifier as the sender, and sending the mass message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application, includes: When the selected common session member identifier matches the target user identifier, the target user identifier is used as the sender, and the group message is sent as a session message to the sessions in the instant messaging application corresponding to each session identifier through the sub-application. 7. The method according to claim 6, characterized in that the method further comprises: When the selected common session member identifier does not match the target user identifier, the sub-application used to send the mass message will be shared to the session constructed by the selected common session member identifier and the target user identifier. 8. The method according to claim 6, characterized in that the method further comprises: When the selected common session member identifier matches the target user identifier, the session identifiers corresponding to each of the multiple sessions are displayed in the sub-application; In the information editing area that corresponds to the session identifier in each of the sub-applications, the group message input in response to the input operation is displayed; In response to the sending operation of the mass message, the selected common session member identifier is used as the sender of the mass message, and the mass message is sent as a session message to the session corresponding to each session identifier in the instant messaging application through the sub-application. 9. The method according to claim 6, characterized in that the method further comprises: Obtain the session identifier corresponding to each of the multiple sessions; Send a session member retrieval request to the application server of the instant messaging application, wherein the session member retrieval request carries each of the session identifiers; Receive the session member identifiers corresponding to each of the session identifiers, returned by the application server in response to the session member retrieval request. The common session member identifier is determined based on the session member identifier corresponding to each of the session identifiers. 10. The method according to claim 1, wherein the information editing area corresponding to each of the session identifiers in the group message sending page displays the group message input in response to the input operation, including: The group message sending page displays a common information editing area corresponding to each of the aforementioned session identifiers; In response to an input operation in the information editing area, the mass message is acquired; The mass message is displayed in the information editing area according to the information display format that matches the information type of the mass message. 11. The method according to claim 1, characterized in that the method further comprises: Access a sub-application running within the instant messaging application, which is logged in using the target user's identifier; The login authorization window is displayed in the sub-application; In response to the authorization operation in the login authorization window, log in to the sub-application with the target user identifier. 12. The method according to claim 1, wherein the method further comprises: When the session member corresponding to the target user identifier is removed from the session corresponding to the session identifier, a prompt message is displayed in the sub-application indicating that the mass message failed to be sent in the session corresponding to the session identifier. 13. The method according to claim 1, characterized in that the method further comprises: Return from the sub-application to the instant messaging application logged in with the target user's identifier; In the instant messaging application, in the sessions corresponding to each of the aforementioned session identifiers, a session message including the mass messaging information is displayed. 14. The method according to claim 1, wherein the method further comprises: Return from the sub-application to the instant messaging application logged in with the target user's identifier; In the instant messaging application, in the sessions corresponding to each of the aforementioned session identifiers, session messages including the mass messaging information are displayed, pushed by the sub-application through other session member identifiers besides the target user identifier. 15. The method according to claim 1, characterized in that the method further comprises: After the mass message is sent as a session message to the instant messaging application logged in by the session member ID corresponding to each session ID, the session message is displayed on the session page corresponding to each session ID through the instant messaging application logged in by the session member ID. 16. The method according to claim 1, wherein sending the mass messaging information as session messages to the sessions corresponding to each session identifier in the instant messaging application via the sub-application comprises: The sub-application sends the mass message, the target user identifier, and each session identifier to the sub-application server. The sub-application server forwards the mass message, the target user identifier, and each session identifier to the application server corresponding to the instant messaging application. The application server sends the mass messaging information as a session message to the sessions associated with each of the session identifiers. The instant messaging application, which logs in using the session member identifier among the session identifiers, displays the session message, which includes the mass message, pushed by the target user identifier, on the session page corresponding to each of the session identifiers. 17. The method according to claim 16, characterized in that the method further comprises: By logging into the instant messaging application with the target user identifier, the conversation message including the mass message pushed by the target user identifier is displayed on the conversation page corresponding to each of the conversation identifiers. 18. A message processing apparatus, characterized in that the apparatus comprises: The entry module is used to enter a sub-application running in an instant messaging application. The sub-application runs in the runtime environment provided by the instant messaging application. The instant messaging application logs in with a target user identifier, and the sub-application is authorized to log in with the target user identifier. The sub-application is used to send session messages to the session corresponding to the target user identifier. The display module is used to display the session identifiers corresponding to multiple sessions in the session message mass sending page of the sub-application. The multiple sessions are created by the instant messaging application and correspond to the target user identifier. Each session is a session in which the target user identifier participates. The display module is also used to display the mass message information input in response to the input operation in the information editing area corresponding to each of the session identifiers on the mass message page. The sending module is used to respond to the sending operation of the mass message, using the target user identifier as the sender, and sending the mass message as a session message to the sessions corresponding to each session identifier in the instant messaging application through the sub-application. 19. The apparatus according to claim 18, wherein the display module is further configured to display a session identifier list in the sub-application, the session identifier list including session identifiers of sessions in the instant messaging application corresponding to the target user identifier; and in response to a selection operation of a session identifier in the session identifier list, determine a plurality of session identifiers and display each of the session identifiers in the sub-application. 20. The apparatus according to claim 19, wherein the display module is further configured to display, in the sub-application, a list of group session identifiers consisting of session identifiers of group sessions corresponding to the target user identifier in the instant messaging application; and, in response to a selection operation of a session identifier in the list of group session identifiers, determine a plurality of group session identifiers and display each of the group session identifiers in the sub-application. 21. The apparatus according to claim 19, wherein the display module is further configured to send a session acquisition request carrying the target user identifier to the application server corresponding to the instant messaging application; receive a session identifier corresponding to the target user identifier returned by the application server in response to the session acquisition request; and display the session identifier list according to the received session identifier. 22. The apparatus according to claim 19, characterized in that the apparatus further comprises: The determining module is used to determine the session message sending order of each session identifier according to the selection order of the session identifiers in the session identifier list; in response to the sending operation of the mass message, using the target user identifier as the sender, the sub-application sequentially sends the mass message as session messages to the sessions corresponding to each session identifier in the instant messaging application according to the session message sending order of each session identifier. 23. The apparatus according to claim 19, wherein the display module is further configured to display a common session member identifier in the sub-application, the common session member identifier being a user identifier corresponding to a session member who simultaneously belongs to the multiple sessions; The device further includes: The selection module is used to respond to the selection operation of any common session member identifier among the common session member identifiers, and to use the session member corresponding to the selected common session member identifier as the sender of the mass message; The sending module is further configured to, when the selected common session member identifier matches the target user identifier, use the target user identifier as the sender and send the group message as a session message to the sessions in the instant messaging application corresponding to each session identifier, respectively, through the sub-application. 24. The apparatus according to claim 23, wherein the apparatus further comprises: The sharing module is used to share the sub-application used to send the mass message to the session constructed by the selected common session member identifier and the target user identifier when the selected common session member identifier does not match the target user identifier. 25. The apparatus according to claim 23, wherein the display module is further configured to, when the selected common session member identifier matches the target user identifier, display the session identifier corresponding to each of the plurality of sessions in the sub-application; and display the group message input in response to the input operation in the information editing area commonly corresponding to each of the session identifiers in the sub-application. The sending module is further configured to respond to the sending operation of the mass message by using the selected common session member identifier as the sender of the mass message, and sending the mass message as a session message to the sessions in the instant messaging application corresponding to each session identifier through the sub-application. 26. The apparatus according to claim 23, wherein the display module is further configured to: acquire session identifiers corresponding to each of the plurality of sessions; send a session member acquisition request to the application server of the instant messaging application, the session member acquisition request carrying each of the session identifiers; receive session member identifiers corresponding to each of the session identifiers returned by the application server in response to the session member acquisition request; and determine the common session member identifier based on the session member identifiers corresponding to each of the session identifiers. 27. The apparatus according to claim 18, wherein the display module is further configured to display an information editing area commonly corresponding to each of the session identifiers in the group message sending page; to obtain the group message in response to an input operation in the information editing area; and to display the group message in the information editing area according to an information display format matching the information type of the group message. 28. The apparatus according to claim 18, wherein the entry module is further configured to enter a sub-application running in the instant messaging application, the instant messaging application being logged in with the target user identifier; display a login authorization window in the sub-application; and log in to the sub-application with the target user identifier in response to an authorization operation in the login authorization window. 29. The apparatus according to claim 18, wherein the display module is further configured to display a prompt message in the sub-application indicating that the mass messaging information failed to be sent in the session corresponding to the session identifier when the session member corresponding to the target user identifier is removed from the session corresponding to the session identifier. 30. The apparatus according to claim 18, wherein the apparatus further comprises: The return module is used to return from the sub-application to the instant messaging application logged in with the target user's identifier; The display module is also used to display a session message including the mass message in the session corresponding to each of the session identifiers in the instant messaging application. 31. The apparatus according to claim 18, characterized in that the apparatus further comprises: The return module is used to return from the sub-application to the instant messaging application logged in with the target user's identifier; The display module is further configured to display, in the sessions corresponding to each of the session identifiers in the instant messaging application, session messages including the mass messaging information pushed by the sub-application by other session member identifiers besides the target user identifier. 32. The apparatus according to claim 18, wherein the display module is further configured to send the mass message as a session message to the instant messaging application logged in by the session member identifier corresponding to each session identifier, and then display the session message in the session page corresponding to each session identifier through the instant messaging application logged in by the session member identifier. 33. The apparatus according to claim 18, wherein the sending module is further configured to: send the mass messaging information, the target user identifier, and each of the session identifiers to the sub-application server via the sub-application; forward the mass messaging information, the target user identifier, and each of the session identifiers to the application server corresponding to the instant messaging application via the sub-application server; send the mass messaging information as a session message to the session with each of the session identifiers via the application server; and display the session message including the mass messaging information pushed by the target user identifier in the session page corresponding to each of the session identifiers via the instant messaging application logged in with the session member identifier among the session identifiers. 34. The apparatus according to claim 18, wherein the sending module is further configured to display, through an instant messaging application logged in with the target user identifier, a session message including the mass messaging information pushed by the target user identifier in a session page corresponding to each of the session identifiers. 35. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 17. 36. A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 17.