CN106059894B

CN106059894B - Message processing method and device

Info

Publication number: CN106059894B
Application number: CN201610348161.9A
Authority: CN
Inventors: 王青; 傅薇; 赵禹; 王佳
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2016-05-24
Filing date: 2016-05-24
Publication date: 2020-05-19
Anticipated expiration: 2036-05-24
Also published as: CN106059894A

Abstract

The embodiment of the invention discloses a message processing method and a device, wherein a history message sharing interface is generated when a first group where a user is located is detected to be added with a new member, then a history message sharing instruction triggered by the user through the history message sharing interface is received, a first history message set corresponding to the first group is obtained according to the history message sharing instruction, a target history message needing to be sent is selected from the first history message set to obtain a target history message set, a first group message comprising the target history message set and a first group identifier is sent to a server, so that the server sends the target history message to a terminal where the group member in the first group is located according to the first group identifier, wherein the first group identifier is the identifier of the first group; the scheme can improve the accuracy of sending the historical messages.

Description

Message processing method and device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a message processing method and apparatus.

Background

With the development of IM (Instant Message) technology, more and more users use IM tools to communicate; in order to meet the requirement of simultaneous communication of multiple users, IM provides a group chat mode capable of realizing simultaneous communication of multiple users, and all users in the same group communicate on the same group session interface. When a certain IM user needs to communicate with multiple people, a group can be created, and other IM users who the IM user wants to communicate with can be added to the group, and in the group, messages sent by any group member can be seen by other group members in the group.

At present, an IM client may record a message sent by a member in a group, so that the group member may view messages sent by itself and other members before, however, for a member entering the group (a new member for short), since the new member is not in the group before, and the IM client of the new member does not receive the message sent by the member in the group before, the IM client of the new member does not record the message sent by the member in the group before, and thus the new member cannot obtain the history message sent by the member in the group before.

In the research and practice process of the prior art, the inventor of the present invention finds that the existing history message sharing mode requires a series of tedious operations performed by the user, and therefore, the accuracy of sending the history message is relatively low.

Disclosure of Invention

The embodiment of the invention provides a message processing method and device, which can improve the accuracy of sending historical messages.

The embodiment of the invention provides a message processing method, which comprises the following steps:

when detecting that a new member is added into a first group where a user is located, generating a history message sharing interface;

receiving a history message sharing instruction triggered by a user through the history message sharing interface;

acquiring a first history message set corresponding to the first group according to the history message sharing instruction;

selecting target historical messages to be sent from the first historical message set to obtain a target historical message set;

and sending a first group message comprising the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where group members in the first group are located according to the first group identifier, wherein the first group identifier is the identifier of the first group.

Correspondingly, an embodiment of the present invention further provides a message processing apparatus, including:

the interface generating unit is used for generating a history message sharing interface when detecting that a new member is added into a first group where a user is located;

the receiving unit is used for receiving a history message sharing instruction triggered by a user through the history message sharing interface;

the acquisition unit is used for acquiring a first historical message set corresponding to the first group according to the historical message sharing instruction;

the selecting unit is used for selecting target historical messages to be sent from the first historical message set to obtain a target historical message set;

a sending unit, configured to send a first group message including the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where a group member in the first group is located according to the first group identifier, where the first group identifier is an identifier of the first group.

The present embodiment also provides another message processing method, including:

receiving a group message sent by a server, wherein the group message comprises: a historical message set and a group identifier;

acquiring a message abstract corresponding to a historical message set;

acquiring attribute information of a corresponding group according to the group identification;

generating corresponding message segments according to the attribute information and the message abstract, and displaying the message segments;

and receiving a historical message acquisition instruction triggered by a user through a terminal, and displaying the historical message set according to the historical message acquisition instruction.

Correspondingly, the present embodiment further provides another message processing apparatus, including:

a message receiving unit, configured to receive a group message sent by a server, where the group message includes: a historical message set and a group identifier;

the abstract acquiring unit is used for acquiring a message abstract corresponding to the historical message set;

the attribute information acquisition unit is used for acquiring the attribute information of the corresponding group according to the group identification;

the segment generating unit is used for generating corresponding message segments according to the attribute information and the message abstract and displaying the message segments;

and the message display unit is used for receiving a historical message acquisition instruction triggered by a user through a terminal and displaying the historical message set according to the historical message acquisition instruction.

The method includes the steps that when a first group where a user is located is detected to have a new member added, a history message sharing interface is generated, then a history message sharing instruction triggered by the user through the history message sharing interface is received, a first history message set corresponding to the first group is obtained according to the history message sharing instruction, a target history message needing to be sent is selected from the first history message set to obtain a target history message set, a first group message including the target history message set and a first group identifier is sent to a server, and the server sends the target history message to a terminal where the group members in the first group are located according to the first group identifier, wherein the first group identifier is the identifier of the first group; due to the adoption of the scheme, the user operation of sharing the historical message can be simplified, so that the sending accuracy of the historical message can be improved compared with the prior art.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart of a message processing method according to an embodiment of the present invention;

fig. 2 is a flowchart of a message processing method according to a second embodiment of the present invention;

fig. 3 is a flowchart of a message processing method according to a third embodiment of the present invention;

fig. 4a is a schematic structural diagram of a message interaction system according to a fourth embodiment of the present invention;

fig. 4b is a flowchart of a history message sharing method according to a fourth embodiment of the present invention;

fig. 4c is a schematic diagram of a group session interface according to a fourth embodiment of the present invention;

fig. 4d is a schematic diagram of a history message selection interface according to a fourth embodiment of the present invention;

fig. 4e is a schematic diagram of another group session interface provided in the fourth embodiment of the present invention;

fig. 4f is a schematic diagram of a history message detail interface provided in the fourth embodiment of the present invention;

fig. 5a is a schematic structural diagram of a first message processing apparatus according to a fifth embodiment of the present invention;

fig. 5b is a schematic structural diagram of a second message processing apparatus according to a fifth embodiment of the present invention;

fig. 5c is a schematic structural diagram of a third message processing apparatus according to a fifth embodiment of the present invention;

fig. 5d is a schematic structural diagram of a fourth message processing apparatus according to a fifth embodiment of the present invention;

fig. 5e is a schematic structural diagram of a fifth message processing apparatus according to a fifth embodiment of the present invention;

fig. 6 is a schematic structural diagram of a message processing apparatus according to a sixth embodiment of the present invention;

fig. 7 is a schematic structural diagram of a terminal according to a seventh embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The embodiment of the invention provides a message processing method and device. The details will be described below separately.

The first embodiment,

The embodiment will be described from the perspective of a message processing apparatus, which may be specifically integrated in a device such as a terminal, and the terminal may be specifically a device such as a mobile phone, a tablet computer, or a PC.

A method of message processing, comprising: when detecting that a new member is added to a first group where a user is located, generating a history message sharing interface, then receiving a history message sharing instruction triggered by the user through the history message sharing interface, acquiring a first history message set corresponding to the first group according to the history message sharing instruction, selecting a target history message needing to be sent from the first history message set to obtain a target history message set, and sending a first group message comprising the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where the group member in the first group is located according to the first group identifier, wherein the first group identifier is the identifier of the first group.

As shown in fig. 1, the flow chart of the message processing method may specifically be as follows:

101. and when detecting that a new member is added into the first group where the user is located, generating a history message sharing interface.

The first group may be an instant messaging group, or other communication groups, etc.

The method of this embodiment may detect whether a new member joins in a first group in which the user is located, and the detection manner may be various, for example, whether a new member joins in a first group may be determined by detecting whether a new member is in a member list corresponding to the current first group; that is, the step of "detecting whether there is a new member in the first group where the user is located" may include:

acquiring a member list corresponding to a first group where a user is located;

judging whether the member list has a new member;

if yes, determining that a new member is added to the first group;

if not, determining that no new members of the first group join.

Specifically, the step of determining whether there is a new member added by comparing the current member list with the historical member list, that is, "determining whether there is a new member in the member list" may include: and comparing the current member worship with the historical member list to obtain a comparison result, and determining whether a new member exists in the member list according to the comparison result.

For another example, since the server adds a new member to the group and sends a prompt message for prompting that the new member joins the group, at this time, it may be determined whether the new member joins based on the indication message; that is, the step of "detecting whether there is a new member in the first group where the user is located" may include:

receiving prompt information which is sent by a server and used for prompting that a new member joins the first group;

and detecting whether a new member is added to the first group according to the indication information.

In this embodiment, when it is detected that a new member is added to the first group in which the user is located, corresponding interface information may be acquired, a history message sharing interface is generated according to the interface information, and then a history message sharing instruction triggered by the user through the history message sharing interface is received.

For example, in order to facilitate user operation and save terminal system resources, a history message sharing interface may be generated on a session interface corresponding to the first group, so that a subsequent user may trigger a history message sharing instruction through the history message sharing interface; that is, the step "generating the history message sharing interface" may include: and generating the historical message sharing interface on a session interface corresponding to the first group.

The history message sharing interface may be represented in various forms, for example, in the form of an icon, an input box, a text, or a graphic, and the like, and optionally, when the history message sharing interface is represented in the form of a text, the text may be marked to remind the user of the text representation interface.

In practical applications, the location of the history message sharing interface on the session interface may be various, such as, for example, the history message sharing interface may be displayed immediately after the display location of the response message indicating that the other user is successfully invited to enter the first group, such as displaying "XXX invitation XXX joined the sharing history message in the group" on the session interface.

Optionally, in order to save terminal system resources and network resources, in this embodiment, the sharer of the history message may be limited based on the association relationship between the user and the new member, that is, before generating the history message sharing interface after detecting that the new member joins in the first group where the user is located, the method in this embodiment may further include:

acquiring the incidence relation between the user and the new member;

judging whether the incidence relation meets a preset condition or not;

and if so, executing the step of generating the history message sharing interface.

The association relationship between the user and the new member may include various types, and may be set according to actual requirements, for example, the association relationship may be a friend relationship, a stranger relationship, a group member, an inviter for inviting the new member to join the group, a relationship between the user and the new member, and the like.

The manner of obtaining the association relationship between the user and the new member may also be various, for example, the association relationship between the user and the new member may be obtained through the contact information of the user, that is, the step "obtaining the association relationship between the user and the new member" may include:

acquiring user information of a contact of a user and user information of a new member;

and acquiring the association relationship between the user and the new member according to the user information of the contact and the user information of the new member.

The user information of the contact in this embodiment may include: at least one of user identification (such as instant messaging identification, nickname and the like) of the contact, remark information of the contact by the user, contact group information to which the contact belongs and the like; the user information of the new member may include: the user identification (e.g., instant messaging identification, nickname) of the new member.

For example, an instant messaging identifier g of a new member may be obtained, and an instant messaging identifier of a contact may be obtained to obtain an instant messaging identifier set, at this time, if an identifier identical to the instant messaging identifier g exists in the identifier set, the new member may be considered to be in a friend relationship with the user, and if an identifier identical to the instant messaging identifier g does not exist in the identifier set, the new member may be considered to be in a stranger relationship with the user.

For another example, after a user invites other users to join a group, the server may feed back an invitation response message indicating whether the invitation was successful; in this case, the embodiment may further obtain the association relationship between the user and the new member based on the response information sent by the server and indicating that the invitation is successful, that is, before the step "obtaining the association relationship between the user and the new member", the method of the embodiment further includes:

receiving response information sent by the server and used for indicating that the other users are successfully invited to enter the first group, wherein the response information comprises: user information of an inviter and user information of an invitee;

at this time, the step of "obtaining the association relationship between the user and the new member" may include: and acquiring the association relationship between the user and the new member according to the response information.

Wherein, the user information of the inviter may include: the user identification (such as an instant messaging identification or a nickname) of the inviter, the user information of the invitee may include: the user identification of the invitee (such as an instant messaging identification or nickname).

For example, when a user a invites a user B to join a group C, the server receives an invitation request sent by a terminal of the user a, where the invitation request carries a user identifier a of the user a, a user identifier B of the user B, and a group identifier C of the group C, the server adds the user identifier B of the user B to the group C corresponding to the group identifier C according to the invitation request, and then sends response information indicating that the user a successfully invites the user B to join the group C to all members in the group C, where the response information may include the user identifier a of the user a and the user identifier B of the user B, and at this time, the terminal of the group member may obtain an association relationship between the terminal and a new member, that is, the user B, based on the response information, for example, the terminal of the user a may determine that the user a is an inviter of the user B, the terminal where the other member is located may determine that the terminal is not an inviter of the user B based on the response information, and that the terminal and the user B are both members of the group C.

The preset conditions in this embodiment may be various, and may be set according to actual requirements, for example, the preset conditions may include: the association relation is that the user is an inviter of the new member, or the user and the new member are friends, or the user and the new member are members of other groups, and the like; at this time, the step "judging whether the association relation satisfies the preset condition" may include:

and determining whether the association relationship is an inviter of the new member, if so, judging that the preset condition is met, and if not, judging that the preset condition is not met.

102. And receiving a history message sharing instruction triggered by the history message sharing interface.

For example, after the history message sharing interface is generated on the session interface corresponding to the first group, the user may operate (e.g., click) the history message sharing interface on the session interface to trigger sending of the history message sharing instruction.

In practical applications, an instruction detection process may be configured to detect the history message sharing instruction triggered through the history message sharing interface.

103. And acquiring a first history message set corresponding to the first group according to the history message sharing instruction.

The first history message set may include at least one history message corresponding to the first group, such as one, two, or more history messages. The history message corresponding to the first group may be a message sent by a group member in the first group before the new member joins the first group; for example, group K originally includes: member 1, member 2 … …, member 5, the historical message for group K may be the message sent by group members 1, 2 … … 5 in group K before user 6 joins group K.

In this embodiment, there may be multiple ways of obtaining the history message set according to the history message sharing instruction, for example, the first history message set corresponding to the first group may be extracted from a corresponding local storage unit (e.g., a local database, a data storage segment, and the like) according to the history message sharing instruction, specifically, the history message sharing instruction may carry a group identifier of the first group, and in this embodiment, the storage unit corresponding to the first group may be determined according to the group identifier of the first group, and then, the history message and the like may be extracted from the storage unit.

In practical applications, after obtaining the first historical message set corresponding to the first group, the present embodiment may further display the historical message set, so that the user can view or select the historical message set, for example, an interface may be generated to display the historical message set.

104. And selecting target historical messages needing to be sent from the first historical message set to obtain a target historical message set.

Wherein the target historical message set may include at least one historical message corresponding to the first group.

In order to meet the user requirements, the method of the embodiment can be used for the user to selectively share the history messages, that is, the target history messages to be sent can be selected from the first history message set corresponding to the first group.

In this embodiment, there may be multiple selection manners for the target history message, for example, to conveniently select a message and improve the efficiency of message selection, a selection interface may be generated, and a message selection interface corresponding to the history message is set on the interface, so that the target history message to be sent may be selected through the message selection interface; that is, the step of "selecting the target history message to be sent from the first history message set" may include:

generating a historical message selection interface, wherein the historical message selection interface comprises the first historical message set and a message selection interface corresponding to the historical messages in the first historical message set;

receiving a message selection instruction triggered by a user through the message selection interface;

and selecting target historical messages to be sent from the first historical message set according to the message selection instruction.

Each historical message in the first historical message set can correspond to one message selection interface; the message selection interface can be represented in various forms, for example, in the form of an icon, an input box, text, a graphic (such as a check box), and the like.

For example, the history message selection interface may display history messages and message selection interfaces (such as check boxes) in a list form, where each entry includes a history message and a message selection interface (such as a check box) corresponding to the history message, and a user clicks the message selection interface (such as a check box) to trigger generation of a message selection instruction, where the message selection instruction indicates that the history message corresponding to the message selection interface (check box) is a target history message that needs to be sent, and at this time, the history message is determined to be the target history message according to the message selection instruction; after the user finishes selecting through the message selection interface (such as a check box), the target historical message set which needs to be sent or shared at this time can be obtained.

In practical application, in order to remind a user to select a certain historical message as a target historical message, the message selection interface may be marked, for example, the message selection interface may be marked in a manner of color marking or the like; for example, when the message selection interface is a check box, after the user clicks the check box, the check box turns blue, which indicates that the history message corresponding to the check box has been selected is the target history message.

Optionally, in order to save system resources, the history message selection interface may be generated based on the session interface corresponding to the first group, that is, the step "generating the history message selection interface" may include: interface information and interface configuration information of a session interface corresponding to the first group are obtained, and then a history message selection interface is generated according to the interface information, the interface configuration information and the first history message set.

Optionally, in order to improve the speed of generating the history message selection interface and acquiring the history message, the present embodiment may generate the interface and acquire the history message in an identification manner; that is, the history message sharing instruction may carry an interface identifier and a first group identifier of the first group, and at this time, the step "obtaining the first history message set corresponding to the first group according to the history message sharing instruction" may include:

acquiring a first historical message set corresponding to the first group according to the first group identifier;

at this time, the step of "generating a history message selection interface" may include: and generating a corresponding historical message selection interface according to the interface identifier and the first historical message set.

In this embodiment, the style of the history message selection interface and the style of the interface may be various, and various styles may be implemented by configuring interface style information and interface style information; that is, the step of "generating a corresponding history message selection interface according to the interface identifier and the first history message set" may include:

acquiring corresponding interface information according to the interface identifier, wherein the interface information comprises: interface style information and interface style information;

and generating a corresponding historical message selection interface according to the first historical message set and the interface information.

The interface style information is used for indicating the style of the interface, which can be configured according to actual requirements, such as a circle, a rectangle, a check box, and the like, and the interface style information is used for indicating the style of the interface, which can be configured according to actual requirements, such as a list-type interface, and the like. The interface information may include basic information for generating an interface and an interface, and the like, in addition to the style information.

105. And sending a first group message comprising the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where group members in the first group are located according to the first group identifier, wherein the first group identifier is the identifier of the first group.

In order to facilitate sharing of the historical messages of the group and improve sending speed of the historical messages, the historical messages can be shared by adopting a mode of sending the group messages, and the server can send the target historical messages to all members in the first group after receiving the group messages, so that the members in the first group can obtain the target historical messages.

The first group message may further include a user identifier (nickname or instant messaging identifier) corresponding to the target history message, and history time (e.g., history sending time, etc.) corresponding to the target history message; the user identifier corresponding to the target history message is the user identifier of the group member corresponding to the target history message (i.e. the user identifier of the target history message sender), the historical time corresponding to the target history message may be the time when the group member sent the target history message, and so on.

In order to facilitate the user to send the history message, improve the sending speed of the history message and save system resources, the embodiment may further set a corresponding message sending interface on the message selection interface, so that the user can send the history message through the message sending interface, that is, the message selection interface further includes: a message sending interface; at this time, the step of "sending a first group message including the set of target history messages and a first group identifier to the server" may include:

receiving a message sending instruction triggered by a user through the message sending interface;

generating a corresponding first group message according to the message sending instruction, wherein the first group message comprises: the target history message and the first group identification;

the first group message is sent to the server.

The messaging interface may be represented in various forms, for example, in the form of an icon (e.g., a button), an input box, text, a graphic, and the like. The position of the message sending interface on the message selection interface can be set according to actual requirements, for example, for convenience of user operation, the message sending interface can be arranged at the bottom of the message selection interface.

As can be seen from the above, in the embodiment of the present invention, when it is detected that a new member is added to a first group in which a user is located, a history message sharing interface is generated, then, a history message sharing instruction triggered by the user through the history message sharing interface is received, a first history message set corresponding to the first group is obtained according to the history message sharing instruction, a target history message to be sent is selected from the first history message set to obtain a target history message set, and a first group message including the target history message set and a first group identifier is sent to a server, so that the server sends the target history message to a terminal in which a group member in the first group is located according to the first group identifier, where the first group identifier is an identifier of the first group; the scheme can simplify the user operation of sharing the historical message and reduce the probability of the occurrence of misoperation of sharing the historical message, so that the sending accuracy of the historical message can be improved compared with the prior art; in addition, the scheme simplifies the user operation of sharing the history message, and reduces the response of the system to the user operation, thereby saving system resources.

Example II,

The above embodiment describes the process of sharing the history message by applying the method of the present invention from the perspective of the history message sharer, and since the history message sharer and the history message receiver can be mutually switched in practical application, that is, the history message sharer can also be the history message receiver, the present embodiment introduces the process of receiving and presenting the history message by applying the method of the present invention from the perspective of the history message receiver.

Referring to fig. 2, based on the description of the first embodiment, the method of this embodiment may further include:

201. receiving a second group message sent by the server, wherein the second group message comprises: and the second historical message set and a second group identifier corresponding to the second historical message.

Wherein the second set of historical messages may include at least one historical message.

In this embodiment, the second history message may be a history message corresponding to the second group, for example, the second history message may be a message sent by a group member in the second group before the user joins the second group; the second group identity is an identity of a second group.

The second group message may further include a user identifier (nickname or instant messaging identifier) corresponding to the historical message in the second historical message set, and a historical time (such as sending time) corresponding to the historical message in the second historical message set; in addition, the second group message may further include a user identifier as a message sharer, and the like. The user identifier corresponding to the history message in the second history message set may be a user identifier (nickname or instant messaging identifier) of a member in the second group that sends the history message before the user joins the second group, and the history time corresponding to the history message in the second history message set may be sending time of the member in the second group that sends the history message.

Optionally, the second group in this embodiment may be the same group as the first group in the first embodiment, or may be a different group; when the history messages are the same group, the second history message set may be the target history message set in the first embodiment, and the second group identifier is the first group identifier in the first embodiment.

In this embodiment, the second group message may be stored after being received, for example, the second group message may be stored in a history message database, and the like.

202. And acquiring a message abstract corresponding to the second historical message set.

In order to save resources, the present embodiment may not display all history messages, but display a message summary first, and then if the user wants to view the history messages, the user may view the history messages through corresponding operations.

The embodiment may adopt a predetermined digest extraction manner to extract the corresponding message digest from the second historical message set; for example, a keyword-based extraction method, or a sentence center position-based abstract extraction method, etc. are used.

The message digest may include: the message digest corresponding to each historical message in the second historical message set may further include: and the user identifier (nickname or instant messaging identifier) corresponding to each historical message in the second historical message set.

203. And acquiring the attribute information of the corresponding group according to the second group identifier.

The attribute information corresponding to the group may be a name of the group, a number of members of the group, and the like; in this embodiment, the attribute information corresponding to the second group may be acquired from the local storage according to the second group identifier; for example, the information storage area corresponding to the second group may be searched according to the second group identifier, and then the attribute information corresponding to the second group may be extracted from the information storage area.

The timing sequence of step 202 and step 203 is not limited, for example, step 203 may be executed before step 202 or simultaneously in practical applications.

204. And generating a corresponding message segment according to the attribute information and the message abstract, and displaying the message segment.

Specifically, the message segment may include a segment title that may include the attribute information and a segment content that may include the message digest; for example, the segment identifier may be "history message requiring synchronization", that is, the name of the group, and the segment content may include: and the summary corresponding to each historical message in the second historical message set and the user identification.

Optionally, in order to save resources, in this embodiment, the message fragment may be displayed in a group session interface corresponding to the second group identifier, and when the second group identifier is the same as the first group identifier in the first embodiment, the message fragment may be displayed in a session interface corresponding to the first group.

205. And receiving a history message acquisition instruction triggered by a user through a terminal.

The historical message obtaining instruction triggering mode may be various, for example, to facilitate user operation, an interface may be set in the group session interface corresponding to the second group identifier, so that the user may trigger the historical message obtaining instruction through the interface; that is, the step of "receiving the history message acquisition instruction triggered by the user through the terminal" may include: and receiving a message acquisition instruction triggered by the history message acquisition interface.

The history message acquiring interface may be represented in various forms, for example, in the form of an icon, an input box, text, a graphic, or the like.

In order to facilitate the user to obtain the history message and save system resources, the history message obtaining interface may be represented in the form of a message box, for example, the history message obtaining interface may be a message bubble, and the message segment is displayed in the message bubble.

206. And extracting the second history message according to the history message acquisition instruction, and displaying the second history message.

Specifically, the history message obtaining instruction may carry a second group identifier, and in this embodiment, the corresponding second history message may be extracted according to the second group identifier, and then the second history message is displayed; for example, after acquiring the history message acquisition instruction, the method of the present embodiment may extract the second history message from the corresponding storage according to the second group identifier.

In this embodiment, in order to facilitate the user to view the history messages, the history messages may be sorted and then displayed, for example, according to the size of the history messages, the time corresponding to the history messages, and the like, that is, the second group message may further include: the historical time corresponding to the historical message in the second historical message set, in this case, the step "displaying the second historical message" may include:

sorting the historical messages in the second historical message set according to the historical time corresponding to the historical messages in the second historical message set;

and displaying the sorted second historical message set.

The historical time may be a historical sending time corresponding to the second historical message, for example, a sending time when a member in the second group sends a message before the user joins the second group.

The embodiment may further display a user identifier corresponding to the history message in the second history message set (for example, a user identifier of a group member in the second group that sends the history message), a history time corresponding to the history message in the second history message set, and the like.

The manner of displaying the second historical message set in this embodiment may be various, for example, a historical message detail interface may be generated to display the second historical message set, the user identifier corresponding to the historical message of the second historical message set, and the historical time corresponding to the historical message in the second historical message set; optionally, the history message details interface may include a header area and a history message presentation area, the header area including: the second group identifies the attribute information (such as group name, group number, etc.) of the corresponding group and the type of the displayed message (such as historical message, etc.), and the historical message display area comprises a second historical message set, the user identification corresponding to each historical message in the set, the historical sending time corresponding to each historical message in the set, etc.

For example, the history message details interface may present the history message in a list, each entry may include the history message and its corresponding user identification, the history sending time, and so on, and the title of the list may include the name of the group and the message type, and so on.

As can be seen from the above, the implementation of the present invention may adopt a method of receiving a second group message sent by the server, where the second group message includes: a second history message set and a second group identifier corresponding to the second history message set, then, obtaining a message abstract corresponding to a second history message, obtaining attribute information of a corresponding group according to the second group identifier, generating a corresponding message segment according to the attribute information and the message abstract, displaying the message segment, receiving a history message obtaining instruction triggered by a user through a terminal, extracting the second history message according to the history message obtaining instruction, displaying the second history message, receiving a history message obtaining instruction triggered by the user through the terminal, extracting the second history message set according to the history message obtaining instruction, and displaying the second history message set; according to the scheme, the historical message abstract can be displayed after the historical message sent by the message sharer is received, then all the historical messages are extracted and displayed after the instruction triggered by the user is received, and whether all the historical messages are displayed or not can be selected according to actual requirements for the user.

Example III,

In this embodiment, a description will be given in terms of another message processing apparatus, where the message processing apparatus may be specifically integrated in a device such as a terminal, and the terminal may be specifically a device such as a mobile phone, a tablet computer, or a PC.

A method of message processing, comprising: receiving a first group message sent by a server, wherein the first group message comprises: the method comprises the steps of acquiring a target historical message set and a first group identifier, then acquiring a message abstract corresponding to the target historical message set, acquiring attribute information of a first group according to the first group identifier, generating a corresponding message segment according to the attribute information and the message abstract, displaying the message segment, receiving a historical message acquisition instruction triggered by a user through a terminal, and displaying the target historical message set according to the historical message acquisition instruction.

As shown in fig. 3, the specific flow of the message processing method is as follows:

301. receiving a group message sent by a server, wherein the group message comprises: a set of historical messages, and a group identification.

Wherein, the history message set comprises history messages corresponding to at least one group (group corresponding to group identification); the historical message corresponding to the group may be a message sent by a group member in the group before the user joins the group; such as a message sent by a group member in the group "need to synchronize" before user T joins the group "need to synchronize".

Optionally, the history message set in this embodiment may be a target history message set sent by the message sharer in the first embodiment, at this time, the history message set may include at least one history message corresponding to the first group, and the group identifier is a group identifier corresponding to the first group in the first embodiment; of course, the historical message set may also be a historical message set sent by other message sharers.

The group message may further include a user identifier (nickname or instant messaging identifier) corresponding to the historical message in the historical message set, and historical time (such as sending time) corresponding to the historical message in the historical message set; in addition, the group message may further include a user identifier as a message sharer, and the like. The user identifier corresponding to the history message in the history message set may be a user identifier (nickname or instant messaging identifier) of a member in the group that sends the history message before the user joins the group corresponding to the group identifier, and the history time corresponding to the history message in the history message set may be the sending time of the member in the group that sends the history message.

In this embodiment, the group message may be stored after being received, for example, the group message may be stored in a history message database.

302. And acquiring a message abstract corresponding to the historical message set.

The message digest may include: the summary corresponding to each historical message in the historical message set, and the message summary may further include: and the user identifier (nickname or instant messaging identifier) corresponding to each historical message in the historical message set.

Specifically, there are various ways to obtain the message digest corresponding to the set, for example, the message digest corresponding to each historical message in the set may be obtained first, and then the digest corresponding to the set is generated based on all the digests; that is, the step of "obtaining the message digest corresponding to the historical message set" may include:

obtaining a summary corresponding to each historical message in a historical message set;

and acquiring the message digest corresponding to the historical message set according to the digest corresponding to each piece of historical message in the historical message set.

The method for obtaining the abstract corresponding to the historical message can also be various, and a preset abstract extracting method can be adopted to extract the corresponding abstract from the historical message; for example, a keyword-based extraction method, or a sentence center position-based abstract extraction method, etc. are used.

Optionally, for convenience of viewing by a user, the present embodiment may further sort the digests corresponding to each historical message in the historical message set, for example, based on time, that is, the step "obtaining the message digest corresponding to the historical message set according to the digest corresponding to each historical message in the historical message set" may include:

sorting the abstracts corresponding to the historical messages according to the historical sending time corresponding to the historical messages in the historical message set;

and acquiring the message digest corresponding to the historical message set according to the sorted digest.

303. And acquiring the attribute information of the corresponding group according to the group identifier.

The attribute information corresponding to the group may be a name of the group, a number of members of the group, and the like; in this embodiment, the attribute information corresponding to the group may be acquired from the corresponding local storage according to the group identifier; for example, an information storage area corresponding to a group may be searched according to the group identifier, and then the attribute information corresponding to the group may be extracted from the information storage area.

The timing sequence of step 302 and step 303 is not limited, for example, step 303 may be executed before step 302 or simultaneously in practical applications.

304. And generating a corresponding message segment according to the attribute information and the message abstract, and displaying the message segment.

Specifically, the message segment may include a segment title that may include the attribute information and a segment content that may include the message digest; that is, the step of "generating a corresponding message fragment according to the attribute information and the message digest" may include:

generating a corresponding segment title according to the attribute information;

generating corresponding segment content according to the message abstract;

and generating a corresponding message segment according to the segment title and the segment content.

For example, the segment header may be "history message requiring synchronization", which is the name of the group, and the segment content may include: and the summary corresponding to each historical message in the historical message set and the user identification.

Optionally, in order to save resources, in this embodiment, the message fragment may be displayed in a group session interface corresponding to the group identifier, specifically, a message dialog box containing the message fragment may be displayed in the group session interface, that is, the step "displaying the message fragment" may include:

acquiring message dialog box template information;

generating a corresponding message dialog box according to the message dialog box template information and the message fragment, wherein the message dialog box comprises the message fragment;

a message dialog box is presented in the group conversation interface.

305. And receiving a history message acquisition instruction triggered by a user through a terminal.

The historical message acquisition instruction triggering mode may be various, for example, to facilitate user operation, an interface may be set in the group session interface corresponding to the group identifier, so that the user may trigger the historical message acquisition instruction through the interface; that is, the step of "receiving the history message acquisition instruction triggered by the user through the terminal" may include: and receiving a message acquisition instruction triggered by the history message acquisition interface.

In order to facilitate the user to obtain the historical information and save system resources, the historical information obtaining interface can be represented in the form of an information dialog box, and the information dialog box can contain information segments; when a user operates the message dialog box, a historical message acquisition instruction is triggered and sent; the message dialog box may be in various forms, such as a bubble form, and may be specifically set according to actual requirements. For example, when the history message acquisition interface is presented in the form of a message bubble, a message bubble containing the message segment is displayed on the group session interface, and when the user clicks the message bubble, the history message acquisition instruction is triggered to be sent.

In practical applications, a detection process may be configured to detect the history message acquisition command triggered by the history message acquisition interface.

306. And extracting the historical message set according to the historical message acquisition instruction, and displaying the historical message set.

Specifically, the history message obtaining instruction may carry a group identifier, and in this embodiment, the corresponding history message may be extracted according to the group identifier, and then the history message is displayed; that is, the step of "extracting the history message set according to the history message obtaining instruction" may include:

determining a storage area for storing the historical message set according to the group identifier;

the set of history messages is extracted from the storage area.

In this embodiment, in order to facilitate the user to view the historical messages, the historical messages may be sorted and then displayed, for example, the size of the historical message, the time corresponding to the historical message, and the like may be determined, that is, the group message may further include: the step "displaying the history message" may include:

sorting the historical messages in the historical message set according to the historical time corresponding to the historical messages in the historical message set;

and displaying the sorted historical message set.

The historical time may be historical sending time corresponding to the historical message, for example, sending time when a member of the group sends a message before the user joins the group.

The embodiment may further display a user identifier corresponding to the history message in the history message set (for example, a user identifier of a group member in the group that sends the history message), a history time corresponding to the history message in the history message set, and the like.

The historical message set may be displayed in various ways in this embodiment, for example, a historical message detail interface may be generated to display the historical message set, the user identifier corresponding to the historical message of the historical message set, and the historical time corresponding to the historical message in the historical message set; optionally, the history message details interface may include a header area and a history message presentation area, the header area including: the group identifier corresponds to the attribute information of the group (such as group name, group number, etc.) and the type of the displayed message (such as historical message, etc.), and the historical message display area comprises a historical message set, a user identifier corresponding to each historical message in the set, a historical sending time corresponding to each historical message in the set, etc.

As can be seen from the above, the implementation of the present invention may adopt receiving a group message sent by the server, where the group message includes: the method comprises the steps of collecting historical information and group identification corresponding to the historical information, then obtaining information abstract corresponding to the historical information, obtaining attribute information of a corresponding group according to the group identification, generating corresponding information segment according to the attribute information and the information abstract, displaying the information segment, receiving a historical information obtaining instruction triggered by a user through a terminal, extracting the historical information according to the historical information obtaining instruction, displaying the historical information, receiving a historical information obtaining instruction triggered by the user through the terminal, extracting the historical information set according to the historical information obtaining instruction, and displaying the historical information set; according to the scheme, after the historical messages sent by the message sharer are received, the historical message abstract is displayed firstly, then all the historical messages are extracted and displayed after the instructions triggered by the user are received, and whether all the historical messages are displayed or not can be selected according to actual requirements for the user.

Example four,

The methods described in the first, second and third embodiments are described in further detail below by way of example.

As shown in fig. 4a, the present embodiment provides a message interaction system, which includes: a server 40, a terminal 41 of a user a, a terminal 42 of a user B, a terminal 43 of a user C, a terminal 44 of a user D; the terminal may be a mobile phone, a tablet Computer, a Personal Computer (PC), or the like, the server 40 may be a network device such as an instant messaging server, and the terminal and the server 40 are connected through a network, such as a wireless network.

In this embodiment, a message processing apparatus according to the first embodiment is specifically integrated in the terminal 41, and a message processing apparatus according to the third embodiment is integrated in the terminal 43.

As shown in fig. 4b, the specific flow of the message processing method is as follows:

401. the terminal 41 sends an invite request to the server 40, the invite request carrying the user identity of user C and the group identity of the user group.

In this embodiment, the current members of the user group include a user a, a user B, and a user D, at this time, the user a may invite the user C to join the user group, specifically, when detecting an instruction for inviting the user C to join the user group, the terminal 41 may send an invitation request to the server according to the instruction, where the request may carry a user identifier (such as an instant messaging identifier) of the target user C to be invited, so as to identify the group of the user group.

402. The server 40 adds the user identifier of the user C to the user group corresponding to the group identifier according to the invitation request, and sends response information indicating that the user C is successfully invited to join the user group to the terminals (i.e., the terminal 41, the terminal 42, and the terminal 43) where all group members of the user group are located.

Specifically, the server 40 needs to add the user identifier of the user C into the identifier set corresponding to the user group, so as to add the user C into the user group.

404. When the terminal 41 detects that a new member is added to the user group, it determines the association relationship between the user a and the user C according to the response information, that the user a is an inviter of the user C.

Specifically, the terminal 41 may detect that a new member joins the user group in various ways, for example, may obtain a member list corresponding to the user group, detect whether the member list has the new member, and if so, determine that the new member joins the user group; for another example, the terminal 41 may directly determine that a new member of the user group joins when receiving the response message.

Wherein the response information may include: a user identification of inviter user a (e.g., an instant messaging identification or nickname of user a) and a user identification of invitee user C (e.g., an instant messaging identification or nickname of user C); at this time, when detecting that a new member joins the user group, the terminal 41 may determine an association relationship between the user a and the new member user C according to the response information, where the association relationship is: user a is an inviter to user C.

Similarly, the terminal 42 of the user B, the terminal 43 of the user C, and the terminal 44 of the user D also determine the association relationship between the user B and the user C (which may be an inviter other than the user C), and the association relationship between the user C and the user C (which may be an inviter other than the user C) according to the response information.

404. The terminal 41 determines whether the association relationship satisfies a preset condition, if so, step 405 is executed, and if not, the process is ended.

The preset condition may include that the association relationship between the user and the new member is: the user is an inviter of the new member, at this time, the terminal 41 may determine that the association relationship between the user a and the new member, user C, satisfies the preset condition, and may execute step 405.

It should be understood that the preset condition is not limited to the user being an inviter of the new member, but may be other conditions, such as a friend relationship between the user and the new member, and so on.

405. The terminal 41 generates a history message sharing interface in the session interface corresponding to the user group.

The history message sharing interface may be represented in various forms, for example, in the form of an icon, an input box, or text, or may also be in the form of a graphic, and the like, and optionally, when the history message sharing interface is represented in the form of a button, the button may be marked to remind the user.

In this embodiment, the historical message sharing interface may have a plurality of positions on the session interface, for example, the historical message sharing interface may be immediately behind the display position of the response message; for example, referring to fig. 4c, after the user a invites the user B to join the user group with the group name "technical traffic group", the terminal 41 may display invitation prompt information (e.g., "you invite wang two to join the group chat" in fig. 4 c) and a history message sharing interface (e.g., "share history message" in fig. 4 c) in a session interface corresponding to the user group, where the history message sharing interface is represented in a text form and bolded for prompt.

406. The terminal 41 receives a history message sharing instruction triggered by the history message sharing interface by the user a, and generates a history message selection interface according to the history message sharing instruction, where the history message selection interface includes a history message set corresponding to the user group, a message selection interface corresponding to the history message in the history set, and a message sending interface.

The history message set may include at least one history message corresponding to a user group, and the history message corresponding to the user group may be a message sent by a member (e.g., user a, user B, or user D) in the user group before user C joins the user group. Specifically, after receiving the history message sharing instruction, the terminal 41 may obtain a history message set corresponding to the user group according to the history message sharing instruction, and then generate a history message selection interface based on the history message set, that is, the step "generating the history message selection interface according to the history message sharing instruction" may include:

acquiring a historical message set and interface information corresponding to a user group according to the historical message sharing instruction, wherein the interface information comprises: interface configuration information and interface configuration information;

generating a history message sharing interface according to the history message set and the interface information, wherein the history message sharing interface comprises: the system comprises a history message set, a message sending interface and a message selection interface corresponding to history messages in the history set.

The interface configuration information may include basic information for generating an interface and interface style information, and the interface information may include basic information for generating an interface and interface style information.

For example, the terminal 41 may extract a history message set corresponding to the user group from a database corresponding to the instant messaging client, after obtaining the history message set, the terminal 41 may generate a history message selection interface to display the history message, and may further provide a message selection interface in the interface, so that the user a may select the history message that needs to be sent.

The message selection interface may be represented in various forms, for example, in the form of an icon, an input box, text, a graphic (checkbox), or the like.

Optionally, in order to facilitate selection and save resources, the history message selection interface may be generated based on a conversation interface of the user group, that is, the interface configuration information may include: interface information of the session interface.

For example, referring to fig. 4d, after the user a clicks the button "share history message", a history message sharing instruction is triggered to be generated, at this time, the terminal 41 may generate a history message sharing interface corresponding to the "technical traffic group" according to the history message sharing instruction, where the history message sharing interface includes a plurality of history messages, a user identifier corresponding to each history message, a message selection interface (i.e., a checkbox in front of the history message in fig. 4 d) corresponding to each history message, and a message sending interface (i.e., a "send" button in the bottom in fig. 4 d).

The messaging interface may be represented in various forms, for example, in the form of an icon, an input box, text, a graphic, and the like. The position of the message sending interface on the message selection interface can be set according to actual requirements, for example, for convenience of user operation, the message sending interface can be arranged at the bottom of the message selection interface, for example, the "send" button in fig. 4d is located at the bottom of the conversation interface.

407. The terminal 41 receives a message selection instruction triggered by the user a through the message selection interface, and selects a target history message to be sent from the history message set according to the message selection instruction to obtain a target history message set.

Referring to fig. 4d, the user a clicks the check box corresponding to the history message to trigger generation of a corresponding message selection instruction, and the terminal 41 may determine that the history message is the target history message that needs to be sent according to the message selection instruction, for example, in fig. 4d, the user a may click the check box in front of the history message "hello" to select the history message "hello" as the target history message that needs to be sent.

In practical applications, the user may be reminded that the history message has been selected by color-marking the checkbox, for example, clicking the checkbox and turning the checkbox into blue to indicate that the history message is selected.

408. The terminal 41 receives a message sending instruction triggered by the user a through the message sending interface, and sends a group message to the server 40 according to the message sending instruction, where the group message includes: a target history message set, a group identification of a user group.

For example, referring to fig. 4d, when the user a clicks the "send" button, a message sending instruction is triggered to be generated, and the terminal 41 may send a group message to the server 40 according to the message sending instruction, where the group message may include: a target historical message set, a group identifier, historical sending time corresponding to the historical message in the target historical message set, a user identifier corresponding to the historical message in the target historical message set, and the like.

409. The server 40 sends the group message to the terminals (i.e. the terminal 41, the terminal 42, the terminal 43 and the terminal 44) of all the group members of the user group according to the group identity.

410. The terminal 43 obtains the message digest corresponding to the target historical message set, and obtains the attribute information of the user group according to the group identifier.

In this embodiment, the terminal 41, the terminal 42, the terminal 43 and the terminal 44 perform the same steps after receiving the group message, and therefore, the terminal 43 is taken as an example to describe the processing procedure after receiving the group message.

Specifically, the terminal 43 may extract a digest corresponding to each historical message in the target historical message set to obtain a message digest corresponding to the target historical message set.

There are various ways in which the terminal 43 obtains the digest corresponding to the history message, for example, a predetermined digest extraction manner may be adopted to extract the corresponding digest from the history message; for example, a keyword-based extraction method, or a sentence center position-based abstract extraction method, etc. is adopted.

In addition, the message digest may further include: the user identification (nickname or instant messaging identification) corresponding to each historical message in the target historical message set, or the historical sending time corresponding to each historical message in the target historical message set.

In this embodiment, the attribute information of the user group includes a name of the user group, the number of members of the group, and the like. For example, the terminal 43 may obtain the attribute information corresponding to the user group from the corresponding local storage unit according to the group identifier; for example, an information storage area corresponding to a user group may be searched according to the group identifier, and then, the attribute information corresponding to the group may be extracted from the information storage area.

411. The terminal 43 generates a corresponding message fragment according to the attribute information and the message abstract, and displays the message fragment in a session interface corresponding to the user group, where the session interface includes a message obtaining interface.

Specifically, the message section may include a section title that may include the attribute information and a section content that may include the message digest. That is, the step of "generating a corresponding message fragment according to the attribute information and the message digest" may include:

generating corresponding segment content according to the message abstract;

and generating a corresponding message segment according to the segment title and the segment content. The history message acquiring interface may be represented in various forms, for example, in the form of an icon, an input box, text, a graphic, or the like.

In order to facilitate the user to obtain the historical information and save resources, the historical information obtaining interface can be represented in the form of an information dialog box, and the information dialog box can contain information segments; when a user operates the message dialog box, a historical message acquisition instruction is triggered and sent; the message dialog box may be in various forms, such as a bubble form, and may be specifically set according to actual requirements. For example, referring to fig. 4e, when the history message capture interface is presented in the form of a message bubble, a message bubble containing the message segment is displayed on the group session interface, and when the user clicks the message bubble, the history message capture command is triggered to be sent.

As shown in fig. 4e, after receiving the group message, the terminal 43 may obtain a message digest of the history message and a name corresponding to the user group, then generate a history message fragment based on the message digest and the name, and display the history message fragment in a session interface corresponding to the "technical traffic group", where the message fragment is in a message bubble with reference to fig. 4e, and at this time, the message bubble may be the history message obtaining interface.

412. The terminal 43 receives a history message acquisition instruction triggered by the user C through the message acquisition interface, and displays a history message detail interface according to the history message acquisition instruction, wherein the history message detail interface comprises the target history message set.

Referring to fig. 4e and 4f, when the user C clicks the message bubble of the history message segment, the generation of the history message acquiring instruction is triggered, at this time, the terminal 43 extracts the target history information according to the history message acquiring instruction, and then, a history message detail interface (refer to fig. 4f) may be generated to display the target history message set; referring to fig. 4f, the history message detail interface may further show the user identifier and the history time corresponding to the history message in the target history message set.

Referring to fig. 4f, the history message detail interface may include a title area for presenting title information including: the name of the user group (e.g., "technical traffic group") and the type of message displayed (e.g., historical message, etc.); the historical message display area is used for displaying each piece of historical message in the target historical message set, and the historical sending time, the user identification and the like corresponding to each piece of historical message in the target historical message set.

The step of displaying the history message detail interface according to the history message obtaining instruction may include:

extracting a target historical message set according to a historical message acquisition instruction;

and generating a history message detail interface according to the target history message set and preset interface configuration information, and displaying the history message detail interface.

For example, the history message detail interface may be generated according to the history message in the target history message set, the user identifier corresponding to the history message in the set, the history sending time corresponding to the history message in the set, and the preset interface configuration information.

Optionally, the history message may be displayed in the history message detail interface according to a history time sequence (e.g., history sending time) corresponding to the history message, that is, the step "generating the history message detail interface according to the target history message set and the preset interface configuration information" may include:

sorting the historical messages in the set according to the historical sending time corresponding to the historical messages in the target historical message set;

and generating a corresponding history detail interface according to the sorted target history message set and preset interface configuration information. As can be seen from the above, in the embodiment of the present invention, a terminal may obtain an association relationship between the user and the new member, and then determine whether the association relationship satisfies a preset condition, if yes, generate a history message sharing interface, receive a history message sharing instruction triggered by the user through the history message sharing interface, send a group message including a target history message and a group identifier corresponding to the group to a server according to the history message sharing instruction, send the group message to a terminal where the group member in the group is located according to the group identifier by the server, receive the target history message by the terminal, generate a message fragment for displaying, receive a message obtaining instruction, and display the target history message according to the instruction; according to the scheme, the user operation of sharing the historical messages can be simplified, so that compared with the prior art, the accuracy of sending the historical messages can be improved, terminal system resources are saved, and the user experience is improved.

In addition, the terminal of the embodiment can limit the sharer of the history message through the preset condition, that is, the terminal can share the message to the new member through the subsequent steps as long as the incidence relation between the terminal and the new member meets the preset condition, so that the terminal resource and the network resource are saved.

Further, the terminal of the embodiment may display the summary of the history message first, and then extract and display all the history messages after receiving the instruction triggered by the user, so that, compared with the prior art, the terminal resource may be saved and the user experience may be improved.

Example V,

In order to better implement the above method, an embodiment of the present invention further provides a message processing apparatus, as shown in fig. 5a, the message processing apparatus includes an interface generating unit 501, a receiving unit 502, an obtaining unit 503, a selecting unit 504, and a sending unit 505, as follows:

(1) an interface generation unit 501;

the interface generating unit 501 is configured to generate a history message sharing interface when it is detected that a new member is added to a first group in which a user is located.

For example, in order to facilitate user operation and save terminal system resources, a history message sharing interface may be generated on a session interface corresponding to the first group, so that a subsequent user may trigger a history message sharing instruction through the history message sharing interface; that is, the interface generating unit 501 may be specifically configured to generate the history message sharing interface on the session interface corresponding to the first group.

In practical applications, the location of the history message sharing interface on the session interface may be various, such as, for example, may be immediately followed by a display location of response information indicating that the other users are successfully invited to enter the first group.

(2) A receiving unit 502;

a receiving unit 502, configured to receive a history message sharing instruction triggered by the history message sharing interface.

(3) An acquisition unit 503;

an obtaining unit 503 is configured to obtain a first history message set corresponding to the first group according to the history message sharing instruction.

The first history message set may include at least one history message corresponding to the first group, such as one, two, or more history messages. The history message corresponding to the first group may be a message sent by a group member in the first group before the new member joins the first group.

In this embodiment, the obtaining unit 503 may obtain the history message set according to the history message sharing instruction, for example, the obtaining unit 503 may extract the first history message set corresponding to the first group from a corresponding local storage unit (e.g., a local database, a data storage segment, and the like) according to the history message sharing instruction, specifically, the history message sharing instruction may carry a group identifier of the first group, and this embodiment may obtain the first history message set corresponding to the first group according to the group identifier of the first group, for example, may determine the history message storage unit corresponding to the first group according to the group identifier, and then extract the history message from the storage unit, and the like.

(4) A selecting unit 504;

a selecting unit 504, configured to select a target history message to be sent from the first history message set, so as to obtain a target history message set.

For example, the selecting unit 504 may specifically include: the interface generation subunit, the instruction receiving subunit and the message selection subunit;

the interface generating subunit is configured to generate a history message selection interface, where the history message selection interface includes the first history message set and a message selection interface corresponding to a history message in the first history message set;

the instruction receiving subunit is used for receiving a message selection instruction triggered by the user through the message selection interface;

the message selection subunit is configured to select, according to the message selection instruction, a target historical message that needs to be sent from the first historical message set.

The history message sharing instruction can carry an interface identifier and a first group identifier of the first group;

at this time, the interface generating subunit is specifically configured to generate a corresponding history message selection interface according to the interface identifier and the first history message set.

For example, the interface generation subunit may be specifically configured to:

(5) A transmission unit 505;

a sending unit 505, configured to send a first group message including the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where a group member in the first group is located according to the first group identifier, where the first group identifier is an identifier of the first group.

The message selection interface further comprises: in the case of a message sending interface, the sending unit 505 may specifically be configured to:

generating a corresponding first group message according to the message sending instruction, wherein the first group message comprises: the set of target historical messages and the first group identification;

the first group message is sent to the server.

Optionally, in order to save system resources, referring to fig. 5b, the apparatus of this embodiment may further include: a judgment unit 506;

the determining unit 506 is configured to, before the interface generating unit 501 generates the history message sharing interface, obtain an association relationship between the user and a new member when it is detected that the new member is added to the first group where the user is located, and determine whether the association relationship meets a preset condition;

the interface generating unit 501 is specifically configured to execute the step of generating the history message sharing interface when the determining unit determines that the association relation satisfies the preset condition.

For example, the association relationship between the user and the new member may be obtained through contact information of the user, or the association relationship between the user and the new member may be obtained based on invitation response information fed back by the server, that is, referring to fig. 5c, the apparatus of this embodiment further includes an information receiving unit 507;

an information receiving unit 507, configured to receive response information sent by the server and used to indicate that the other users are successfully invited to join the first group before the determining unit 506 obtains the association relationship between the user and the new member, where the response information includes: user information of an inviter and user information of an invitee;

the determining unit 506 is specifically configured to obtain an association relationship between the user and the new member according to the response information, and determine whether the association relationship satisfies a preset condition.

The preset conditions may be various, and may be set according to actual requirements, for example, the preset conditions may include: the association relation is that the user is an inviter of the new member, or the user and the new member are friends, or the user and the new member are members of other groups, and the like; at this time, the determining unit 506 may be specifically configured to:

and determining whether the association relationship is an inviter of the new member, if so, judging that the preset condition is met, and if not, judging that the preset condition is not met. Optionally, the apparatus of this embodiment may further receive history messages sent by other users or by themselves, and perform corresponding display, for example, referring to fig. 5d, the apparatus of this embodiment may further include: a message receiving unit 508, a digest acquisition unit 509, an attribute acquisition unit 510, and a fragment generation unit 511;

the message receiving unit 508 is configured to receive a second group message sent by the server, where the second group message includes: a second historical message set and a second group identifier corresponding to the second historical message set;

the digest obtaining unit 509 is configured to obtain a message digest corresponding to the second historical message set;

the attribute obtaining unit 510 is configured to obtain attribute information of a corresponding group according to the second group identifier;

the fragment generating unit 511 is configured to generate a corresponding message fragment according to the attribute information and the message digest, and display the message fragment.

Optionally, referring to fig. 5e, the apparatus of this embodiment may further include: an instruction receiving unit 512 and a message presentation unit 513;

the instruction receiving unit 512 is configured to receive a history message obtaining instruction triggered by a user through a terminal after the segment generating unit displays the message segment;

the message displaying unit 513 is configured to extract the second history message according to the history message obtaining instruction, and display the second history message.

For example, the second group message further includes: in the case of the historical time corresponding to the historical message in the second historical message set, the message display unit 513 may be specifically configured to:

the message display unit is specifically configured to:

extracting the second historical message set according to the historical message acquisition instruction;

sorting the historical messages in the second historical message set according to the historical time;

and displaying the sorted second historical message set.

In a specific implementation, the above units may be implemented as independent entities, or may be combined arbitrarily to be implemented as the same or several entities, and the specific implementation of the above units may refer to the foregoing method embodiments, which are not described herein again.

The message processing apparatus may be specifically integrated in a device such as a terminal, for example, installed in the terminal in the form of a client or software, and the terminal may be specifically a device such as a mobile phone, a tablet computer, or a PC.

As can be seen from the above, in the embodiment of the present invention, when the obtaining unit 501 detects that a new member is added to the first group where the user is located, a history message sharing interface is generated, then, the receiving unit 502 receives a history message sharing instruction triggered by the user through the history message sharing interface, the obtaining unit 503 obtains a first history message set corresponding to the first group according to the history message sharing instruction, the selecting unit 504 selects a target history message to be sent from the first history message set, to obtain a set of target history messages, a first group message comprising the set of target history messages and a first group identification is sent by the sending unit 505 to the server, so that the server sends the target history message to the terminal where the group member in the first group is located according to the first group identifier, wherein the first group identifier is the identifier of the first group; according to the scheme, the user operation of sharing the historical message can be simplified, so that compared with the prior art, the accuracy of sending the historical message can be improved, and the terminal system resources can be saved.

In addition, according to the embodiment, sharers of the history message can be limited through the preset condition, that is, the message can be shared to the new member through subsequent steps as long as the incidence relation between the sharers and the new member meets the preset condition, so that terminal resources and network resources are saved.

Example six,

In order to better implement the above method, an embodiment of the present invention further provides another message processing apparatus, as shown in fig. 6, the message processing apparatus includes a message receiving unit 601, a digest obtaining unit 602, an attribute information obtaining unit 603, a fragment generating unit 604, and a message presenting unit 605, as follows:

(1) a message receiving unit 601;

a message receiving unit 601, configured to receive a group message sent by a server, where the group message includes: a set of historical messages, and a group identification.

(2) Abstract acquisition unit 602

A digest obtaining unit 602, configured to obtain a message digest corresponding to the historical message set.

For example, the abstract obtaining unit 602 is specifically configured to:

(3) An attribute information acquisition unit 603;

an attribute information obtaining unit 603, configured to obtain attribute information of a corresponding group according to the group identifier.

The attribute information corresponding to the group may be a name of the group, a number of members of the group, and the like; the embodiment may acquire the attribute information corresponding to the group from the corresponding local storage according to the group identifier.

(4) A segment generation unit 604;

the fragment generating unit 604 is configured to generate a corresponding message fragment according to the attribute information and the message digest, and display the message fragment.

Specifically, the message segment may include a segment title and a segment content, the segment title may include the attribute information, and the segment generating unit 604 may be specifically configured to:

generating corresponding segment content according to the message abstract;

(5) A message display unit 605;

the message display unit 605 is configured to receive a history message acquisition instruction triggered by the user through the terminal, and display the history message set according to the history message acquisition instruction.

For example, in order to facilitate user operation, an interface may be set in a group session interface corresponding to the group identifier, so that the user may trigger the history message obtaining instruction through the interface, that is, the message display unit 605 is specifically configured to receive the message obtaining instruction triggered by the user through the history message obtaining interface, and display the history message set according to the history message obtaining instruction.

Specifically, the history message obtaining instruction may carry a group identifier, and in this embodiment, the corresponding history message may be extracted according to the group identifier, and then the history message is displayed, that is, the message displaying unit 605 may be specifically configured to:

extracting the set of history messages from the storage area;

and displaying the historical message set.

In this embodiment, in order to facilitate the user to view the history messages, the history messages may be sorted and then displayed, that is, the step "displaying the history message set" may include:

and displaying the sorted historical message set.

The message display unit 605 of this embodiment may further display a user identifier corresponding to the historical message in the historical message set (for example, a user identifier of a group member in the group that sends the historical message), a historical time corresponding to the historical message in the historical message set, and the like.

As can be seen from the above, the implementation of the present invention may employ the message receiving unit 601 to receive the group message sent by the server, where the group message includes: a history message set and a group identifier corresponding to the history message set, then, a message digest corresponding to the history message is obtained by a digest obtaining unit 602, attribute information of a corresponding group is obtained by an attribute information obtaining unit 603 according to the group identifier, a corresponding message fragment is generated by a fragment generating unit 604 according to the attribute information and the message digest and displayed, a history message obtaining instruction triggered by a user through a terminal is received, the history message is extracted according to the history message obtaining instruction and displayed, a history message obtaining instruction triggered by the user through the terminal is received by a message displaying unit 605, the history message set is extracted according to the history message obtaining instruction and displayed; according to the scheme, after the historical messages sent by the message sharer are received, the historical message abstract is displayed firstly, then all the historical messages are extracted and displayed after the instructions triggered by the user are received, and whether all the historical messages are displayed or not can be selected according to actual requirements for the user.

Example seven,

Accordingly, an embodiment of the present invention further provides a terminal, as shown in fig. 7, which may include Radio Frequency (RF) circuit 701, memory 702 including one or more computer-readable storage media, an input unit 703, a display unit 704, a sensor 705, an audio circuit 706, a Wireless Fidelity (WiFi) module 707, a processor 708 including one or more processing cores, and a power supply 709. Those skilled in the art will appreciate that the terminal structure shown in fig. 7 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:

the RF circuit 701 may be used for receiving and transmitting signals during a message transmission or communication process, and in particular, for receiving downlink information of a base station and then sending the received downlink information to the one or more processors 708 for processing; in addition, data relating to uplink is transmitted to the base station. In general, RF circuitry 701 includes, but is not limited to, an antenna, at least one Amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, RF circuit 701 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), and the like.

The memory 702 may be used to store software programs and modules, and the processor 708 executes various functional applications and data processing by operating the software programs and modules stored in the memory 702. The memory 702 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the terminal, etc. Further, the memory 702 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 702 may also include a memory controller to provide the processor 708 and the input unit 703 access to the memory 702.

The input unit 703 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. In particular, in a particular embodiment, the input unit 703 may include a touch-sensitive surface as well as other input devices. The touch-sensitive surface, also referred to as a touch display screen or a touch pad, may collect touch operations by a user (e.g., operations by a user on or near the touch-sensitive surface using a finger, a stylus, or any other suitable object or attachment) thereon or nearby, and drive the corresponding connection device according to a predetermined program. Alternatively, the touch sensitive surface may comprise two parts, a touch detection means and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 708, and can receive and execute commands sent by the processor 708. In addition, touch sensitive surfaces may be implemented using various types of resistive, capacitive, infrared, and surface acoustic waves. The input unit 703 may include other input devices in addition to the touch-sensitive surface. In particular, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 704 may be used to display information input by or provided to the user and various graphical user interfaces of the terminal, which may be made up of graphics, text, icons, video, and any combination thereof. The Display unit 704 may include a Display panel, and optionally, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch-sensitive surface may overlay the display panel, and when a touch operation is detected on or near the touch-sensitive surface, the touch operation is communicated to the processor 708 to determine the type of touch event, and the processor 708 provides a corresponding visual output on the display panel according to the type of touch event. Although in FIG. 7 the touch-sensitive surface and the display panel are two separate components to implement input and output functions, in some embodiments the touch-sensitive surface may be integrated with the display panel to implement input and output functions.

The terminal may also include at least one sensor 705, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel according to the brightness of ambient light, and a proximity sensor that may turn off the display panel and/or the backlight when the terminal is moved to the ear. As one of the motion sensors, the gravity acceleration sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when the mobile phone is stationary, and can be used for applications of recognizing the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured in the terminal, detailed description is omitted here.

Audio circuitry 706, a speaker, and a microphone may provide an audio interface between the user and the terminal. The audio circuit 706 can transmit the electrical signal converted from the received audio data to a loudspeaker, and the electrical signal is converted into a sound signal by the loudspeaker and output; on the other hand, the microphone converts the collected sound signal into an electric signal, which is received by the audio circuit 706 and converted into audio data, which is then processed by the audio data output processor 708, and then transmitted to, for example, another terminal via the RF circuit 701, or the audio data is output to the memory 702 for further processing. The audio circuitry 706 may also include an earbud jack to provide communication of peripheral headphones with the terminal.

WiFi belongs to short-distance wireless transmission technology, and the terminal can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the WiFi module 707, and provides wireless broadband internet access for the user. Although fig. 7 shows the WiFi module 707, it is understood that it does not belong to the essential constitution of the terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The processor 708 is a control center of the terminal, connects various parts of the entire handset using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in the memory 702 and calling data stored in the memory 702, thereby performing overall monitoring of the handset. Optionally, processor 708 may include one or more processing cores; preferably, the processor 708 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 708.

The terminal also includes a power source 709 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 708 via a power management system that may be configured to manage charging, discharging, and power consumption. The power supply 709 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.

Although not shown, the terminal may further include a camera, a bluetooth module, and the like, which will not be described herein. Specifically, in this embodiment, the processor 708 in the terminal loads the executable file corresponding to the process of one or more application programs into the memory 702 according to the following instructions, and the processor 708 runs the application programs stored in the memory 702, so as to implement the following functions:

Optionally, before generating the history message sharing interface, the method may further include:

when detecting that a new member is added into a first group in which a user is located, acquiring an association relationship between the user and the new member;

judging whether the incidence relation meets a preset condition or not;

Optionally, before obtaining the association relationship between the user and the new member, the method further includes: receiving response information sent by the server and used for indicating that the other users are successfully invited to join the first group, wherein the response information comprises: user information of an inviter and user information of an invitee;

the step of obtaining the association relationship between the user and the new member specifically includes: optionally, the step of obtaining the association between the user and the new member according to the response information, and selecting the target history message to be sent from the first history message set specifically includes:

selecting target historical messages to be sent from the first historical message set according to the message selection instruction

Optionally, the message selection interface further includes: a message sending interface;

the step of sending the first group message including the target history message set and the first group identifier to the server specifically includes:

the first group message is sent to the server.

Optionally, on the basis of the foregoing implementation, the following functions may also be implemented:

receiving a second group message sent by the server, wherein the second group message comprises: a second historical message set and a second group identifier corresponding to the second historical message set;

acquiring a message abstract corresponding to the second historical message set;

acquiring attribute information of the corresponding group according to the second group identifier;

and generating a corresponding message segment according to the attribute information and the message abstract, and displaying the message segment.

Optionally, after presenting the message segment, the message processing method further includes:

receiving a history message acquisition instruction triggered by a user through a terminal;

and extracting the second historical message set according to the historical message acquisition instruction, and displaying the second historical message set.

Optionally, the step of presenting the message fragment specifically includes: displaying the message segment in a group session interface corresponding to the second group identifier, wherein the group session interface comprises a historical message acquisition interface;

the step of receiving the historical message acquisition instruction triggered by the user through the terminal specifically comprises the following steps: and receiving a message acquisition instruction triggered by the history message acquisition interface.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.

The above detailed description is provided for a message processing and device provided by the embodiment of the present invention, and the principle and the embodiment of the present invention are explained by applying a specific example, and the above description of the embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for those skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A message processing method, comprising:

when detecting that a first group where a user is located has a new member to join and the association relationship between the user and the new member is that the user is an inviter of the new member, generating and displaying a history message sharing interface on a session interface corresponding to the first group of the inviter;

displaying a historical message selection interface, wherein the historical message selection interface comprises the first historical message set and a message selection interface corresponding to the historical message in the first historical message set;

selecting target historical messages to be sent from the first historical message set according to the message selection instruction to obtain a target historical message set;

and sending a first group message comprising the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where the new member is located in the first group according to the first group identifier, wherein the first group identifier is the identifier of the first group.

2. The message processing method according to claim 1, wherein when it is detected that a new member joins in a first group in which a user is located and an association relationship between the user and the new member is that the user is an inviter of the new member, generating and displaying a history message sharing interface on a session interface corresponding to the first group of the inviter comprises:

receiving response information sent by a server and used for indicating that other users are successfully invited to join the first group, wherein the response information comprises: user information of an inviter and user information of an invitee;

when detecting that a new member is added into a first group in which a user is located, acquiring an association relationship between the user and the new member according to the response information;

and when the association relationship between the user and the new member is that the user is an inviter of the new member, generating and displaying a history message sharing interface on a session interface corresponding to a first group of the inviter.

3. The message processing method according to claim 1, wherein the history message sharing instruction carries an interface identifier and a first group identifier of the first group;

the step of obtaining the first history message set corresponding to the first group according to the history message sharing instruction specifically includes:

acquiring a first history message set corresponding to the first group according to the first group identifier;

the step of generating the history message selection interface specifically includes:

and generating a corresponding historical message selection interface according to the interface identifier and the first historical message set.

4. The message processing method according to claim 3, wherein the step of generating a corresponding historical message selection interface according to the interface identifier and the first historical message set specifically comprises:

5. The message processing method of claim 1, wherein the message selection interface further comprises: a message sending interface;

the step of sending a first group message including the target history message set and a first group identifier to a server specifically includes:

sending the first group message to the server.

6. The message processing method of claim 1, wherein the message processing method further comprises:

7. The message processing method of claim 6, wherein after presenting the message fragment, the message processing method further comprises:

8. The message processing method of claim 7, wherein the second group message further comprises: historical time corresponding to the historical messages in the second historical message set; the step of displaying the second history message specifically includes:

and displaying the sorted second historical message set.

9. The message processing method according to claim 7, wherein the step of presenting the message fragment specifically comprises: displaying the message segment in a group session interface corresponding to the second group identifier, wherein the group session interface comprises a historical message acquisition interface;

the step of receiving the historical message acquisition instruction triggered by the user through the terminal specifically includes: and receiving a message acquisition instruction triggered by the user through the history message acquisition interface.

10. A message processing method, comprising:

receiving a group message sent by a server, wherein the group message comprises: a history message set and a group identifier, wherein the history message set is a first history message set which is sent to the server by an inviter terminal by adopting the method of claim 1;

acquiring a message abstract corresponding to a historical message set;

generating corresponding message segments according to the attribute information and the message abstract, and displaying the message segments in a group session interface corresponding to the group identification;

11. A message processing apparatus, comprising:

the device comprises an interface generating unit, a history message sharing unit and a history message sharing unit, wherein the interface generating unit is used for generating and displaying a history message sharing interface on a session interface corresponding to a first group of an inviter when a first group where a user is located is detected to have new members to join and the association relationship between the user and the new members is that the user is the inviter of the new members;

the selecting unit comprises: the interface generation subunit, the instruction receiving subunit and the message selection subunit;

the interface generating subunit is configured to display a history message selection interface, where the history message selection interface includes the first history message set and a message selection interface corresponding to a history message in the first history message set;

the message selection subunit is configured to select, according to the message selection instruction, a target historical message to be sent from the first historical message set to obtain a target historical message set

A sending unit, configured to send a first group message including the target history message set and a first group identifier to a server, so that the server sends the target history message to a terminal where the new member is located in the first group according to the first group identifier, where the first group identifier is an identifier of the first group.

12. The message processing apparatus according to claim 11, further comprising an information receiving unit;

the information receiving unit is configured to receive response information sent by the server and used for indicating that other users are successfully invited to join the first group, where the response information includes: user information of an inviter and user information of an invitee;

the interface generating unit is specifically configured to, when it is detected that a new member is added to a first group in which a user is located, obtain an association relationship between the user and the new member according to the response information; and when the association relationship between the user and the new member is that the user is an inviter of the new member, generating and displaying a history message sharing interface on a session interface corresponding to a first group of the inviter.

13. The message processing apparatus according to claim 11, wherein the history message sharing instruction carries an interface identifier and a first group identifier of the first group;

the obtaining unit is specifically configured to obtain a first history message set corresponding to the first group according to the first group identifier;

the interface generating subunit is specifically configured to generate a corresponding history message selection interface according to the interface identifier and the first history message set.

14. The message processing apparatus of claim 11, wherein the historical message selection interface further comprises: a message sending interface;

the sending unit is specifically configured to:

sending the first group message to the server.

15. The message processing apparatus of claim 11, further comprising: the device comprises a message receiving unit, a summary acquiring unit, an attribute acquiring unit and a fragment generating unit;

the message receiving unit is configured to receive a second group message sent by the server, where the second group message includes: a second historical message set and a second group identifier corresponding to the second historical message set;

the abstract acquiring unit is used for acquiring a message abstract corresponding to a second historical message set;

the attribute obtaining unit is used for obtaining attribute information of the corresponding group according to the second group identifier;

and the segment generating unit is used for generating a corresponding message segment according to the attribute information and the message abstract and displaying the message segment.

16. The message processing apparatus of claim 15, further comprising: the device comprises an instruction receiving unit and a message display unit;

the instruction receiving unit is used for receiving a historical message acquisition instruction triggered by a user through a terminal after the message segment is displayed by the segment generating unit;

and the message display unit is used for extracting the second historical message according to the historical message acquisition instruction and displaying the second historical message.

17. The message processing apparatus of claim 16, wherein the second group message further comprises: historical time corresponding to the historical messages in the second historical message set;

the message display unit is specifically configured to:

and displaying the sorted second historical message set.

18. A message processing apparatus, comprising:

a message receiving unit, configured to receive a group message sent by a server, where the group message includes: a history message set and a group identifier, wherein the history message set is a first history message set which is sent to the server by an inviter terminal by adopting the method of claim 1;

the segment generating unit is used for generating corresponding message segments according to the attribute information and the message abstract and displaying the message segments in a group session interface corresponding to the group identification;

19. A computer-readable storage medium storing a computer program for message processing, wherein the computer program causes a computer to perform the method of any one of claims 1-10.