Display method, device, terminal and storage medium of conversation message

Abstract

The embodiment of the application discloses a kind of display method, device, terminal and storage medium of conversation message, belong to communication technical field.The method includes: display conversation object selection interface, and the identification item of at least one conversation object is included in conversation object selection interface;Receive the message preview instruction for first conversation object in at least one conversation object;Response to the message preview instruction for first conversation object, based on the display position of the identification item of first conversation object, display the message preview window of first conversation object;In the message preview window of first conversation object, display the preview conversation message of first conversation object, and the preview conversation message is the conversation message that is filtered out from the conversation message of first conversation object for user preview.The embodiment of the application can realize preview conversation message without user switching interface, and it is simple and easy to operate, and high efficiency.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, terminal and storage medium for displaying session messages. Background Technology

[0002] With the development of communication technology, users can chat with friends through instant messaging applications installed on their devices.

[0003] In related technologies, users can edit conversation messages within an instant messaging application and send those messages to friends through the application. When a user wants to view conversation messages with a friend, they need to click on that friend's avatar in the message list interface to enter the corresponding chat conversation interface and browse the messages.

[0004] However, the operation of browsing session messages in the aforementioned technologies is cumbersome and inefficient. Summary of the Invention

[0005] This application provides a method, apparatus, terminal, and storage medium for displaying conversation messages. This embodiment allows users to preview conversation messages without switching interfaces, making it simple and efficient. The technical solution is as follows:

[0006] On one hand, embodiments of this application provide a method for displaying session messages, the method comprising:

[0007] Display a session object selection interface, which includes at least one identifier for a session object;

[0008] Receive a message preview instruction for the first session object in the at least one session object;

[0009] In response to a message preview command for the first session object, a message preview window for the first session object is displayed based on the display position of the identifier item of the first session object;

[0010] In the message preview window of the first session object, a preview session message of the first session object is displayed. The preview session message is a session message that is selected from the session messages of the first session object for the user to preview.

[0011] On the other hand, embodiments of this application provide a device for displaying session messages, the device comprising:

[0012] The interface display module is used to display a session object selection interface, which includes at least one identifier item for a session object.

[0013] The instruction receiving module is used to receive a message preview instruction for the first session object among the at least one session objects;

[0014] A window display module is used to respond to a message preview command for the first session object and display a message preview window for the first session object based on the display position of the identifier item of the first session object;

[0015] The message display module is used to display preview session messages of the first session object in the message preview window of the first session object. The preview session messages are session messages that are filtered from the session messages of the first session object for the user to preview.

[0016] On the other hand, embodiments of this application provide a terminal, the terminal including a processor and a memory, the memory storing at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the session message display method as described above.

[0017] In another aspect, embodiments of this application provide a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the session message display method as described above.

[0018] In another aspect, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. The processor of a terminal reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the terminal to perform the aforementioned method for displaying session messages.

[0019] The technical solution provided in this application can bring the following beneficial effects:

[0020] By receiving a message preview command for any session object in the session object selection interface, and displaying the message preview window of the session object based on the display position of the identifier item of the session object, the present application embodiment can preview session messages without the user switching interfaces, which is simple to operate and highly efficient.

[0021] In addition, in this embodiment of the application, the message preview window of the session object is displayed based on the display position of the identifier item of the session object. The display position of the message preview window is more targeted, making it easier for users to know that the message preview window corresponds to the session object, thereby improving the user's information browsing efficiency.

[0022] In addition, the conversation messages displayed in the message preview window provided in this application embodiment are filtered from the conversation messages of the conversation object, rather than simply displaying the conversation messages of the conversation object. Therefore, the preview conversation messages displayed in this application embodiment can better meet the user's preview needs and improve the user's information processing efficiency. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of an implementation environment provided in one embodiment of this application;

[0025] Figure 2 This is a flowchart of a method for displaying session messages according to an embodiment of this application;

[0026] Figure 3 This is a schematic diagram of a session object selection interface provided in one embodiment of this application;

[0027] Figure 4 This is a schematic diagram of a session object selection interface provided in another embodiment of this application;

[0028] Figure 5 This is a schematic diagram of a session object selection interface provided in another embodiment of this application;

[0029] Figure 6 This is a schematic diagram of a session object selection interface provided in another embodiment of this application;

[0030] Figure 7 This is a schematic diagram of a preview session message display process provided in one embodiment of this application;

[0031] Figure 8 This is a schematic diagram of the preview session message display process provided in another embodiment of this application;

[0032] Figure 9 This is a flowchart of a method for displaying session messages provided in another embodiment of this application;

[0033] Figure 10 This is a schematic diagram of a session object selection interface provided in another embodiment of this application;

[0034] Figure 11 This is a schematic diagram of a preview session message provided in one embodiment of this application;

[0035] Figure 12 This is a schematic diagram of a preview session message provided in another embodiment of this application;

[0036] Figure 13 This is a schematic diagram of a prompt message provided in one embodiment of this application;

[0037] Figure 14 This is a schematic diagram of a message preview window provided in one embodiment of this application;

[0038] Figure 15 This is a flowchart of a method for displaying session messages provided in another embodiment of this application;

[0039] Figure 16 This is a schematic diagram of the display process of preview session messages provided in another embodiment of this application;

[0040] Figure 17 This is a block diagram of a session message display device provided in one embodiment of this application;

[0041] Figure 18 This is a structural block diagram of a terminal provided in one embodiment of this application. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0043] Please refer to Figure 1 The diagram illustrates an implementation environment provided in one embodiment of this application. This implementation environment may include: a first terminal 10, a second terminal 20, and a server 30.

[0044] In this embodiment, a first client is installed and runs on the first terminal 10, and a second client is installed and runs on the second terminal 20. The first terminal 10 and the second terminal 20 can be electronic devices such as mobile phones, tablets, wearable devices, PCs (Personal Computers), or smart vehicle terminals. Exemplarily, the first terminal 10 and the second terminal 20 can have a display screen for displaying session messages.

[0045] For example, the first client and the second client can be clients of the target application, such as clients of instant messaging applications, social applications, community applications, review applications, etc. The first client and the second client can be clients of the same application; for example, the first client and the second client can be clients of the same instant messaging application. The first client and the second client have the function of sending and receiving conversational messages. For example, the conversational message can be a text message, an image message, a voice message, etc., and in possible implementations, the conversational message can also be an emoticon. In one example, the first client can send conversational messages, and the second client can receive conversational messages; in another example, the second client can send conversational messages, and the first client can receive conversational messages. The first client corresponds to a first user account, and the second client corresponds to a second user account. In possible implementations, the first user account and the second user account have a friend relationship, that is, the first user account is in the friend list of the second client, and the second user account is in the friend list of the first client; in possible implementations, the first user account and the second user account do not have a friend relationship, that is, the first user account is not in the friend list of the second client, and the second user account is not in the friend list of the first client.

[0046] For example, server 30 can be the backend server for the first client and the second client described above. Server 30 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center. Server 30 can communicate with the first terminal 10 and the second terminal 20 via wired or wireless networks, such as relaying session messages sent and received between the first terminal 10 and the second terminal 20.

[0047] The following describes several embodiments of this application.

[0048] Please refer to Figure 2 The diagram illustrates a flowchart of a method for displaying session messages according to an embodiment of this application. This method can be applied to a terminal, and in a possible implementation, it can be executed by a client of a target application in the terminal. The method may include the following steps.

[0049] Step 201: Display the session object selection interface, which includes an identifier for at least one session object.

[0050] The session object selection interface is a user interface on the client side, used by the user to select a session object. The session object selection interface can be any user interface on the client side; for example, it could be... Figure 1The user interface of the first client described herein can also be the user interface of the second client; this application embodiment does not limit this. The client can be a client of an instant messaging application, a client of a social application, or a client of other applications; this application embodiment does not limit this.

[0051] The identifier of a session object is used to identify the session object. For example, the identifier of a session object may include at least one of the following: the session object's avatar, or the session object's name. A session object can be any object; for example, it can be a contact, such as a friend or a contact in a temporary session; it can also be a group. This embodiment of the application does not limit this.

[0052] In possible implementations, the session object selection interface can include any of the following: a friend list interface, a group chat list interface, a message list interface, or an object search interface. For example... Figure 3 As shown, the friend list interface 300 refers to the interface used to display each friend in a list format; for example... Figure 4 As shown, the group chat list interface 400 refers to the interface used to display various group chats in a list format; for example... Figure 5 As shown, message list interface 500 refers to the interface used to display the session objects corresponding to the received session messages in list form; for example... Figure 6 As shown, the object search interface 600 refers to the interface used to display the session objects determined based on the search keywords.

[0053] In possible implementations, when the conversation object selection interface includes a friend list interface, the friend list interface can be displayed in response to a trigger operation on the friend display control; when the conversation object selection interface includes a group chat list interface, the group chat list interface can be displayed in response to a trigger operation on the group chat display control; when the conversation object selection interface includes a message list interface, the message list interface can be displayed in response to a trigger operation on the message display control; when the conversation object selection interface includes an object search interface, the object search interface can be displayed in response to a trigger operation on the object search control.

[0054] Step 202: Receive a message preview instruction for the first session object in at least one session object.

[0055] The first session object can be any one or more session objects from at least one session object. For example, the first session object can be a friend, a group, or a temporary contact. This application embodiment does not limit this.

[0056] A message preview command is an instruction to preview the preview session messages between a logged-in user account and a session object. In possible implementations, the message preview command can be triggered via touch, gesture, voice, etc. For example, in response to a touch operation on an identifier item of the first session object, it is determined that a message preview command for the first session object has been received; or, in response to receiving a voice trigger operation from the user for the first session object, it is determined that a message preview command for the first session object has been received, and the user can trigger the client to receive the voice trigger operation by speaking to the client, "Show the preview session messages of the first session object"; or, in response to receiving a gesture trigger operation from the user for the first session object, it is determined that a message preview command for the first session object has been received, and the user can trigger the client to receive the gesture trigger operation by making the gesture corresponding to the message preview command towards the first session object in the client.

[0057] Step 203: In response to the message preview command for the first session object, display the message preview window of the first session object based on the display position of the identifier item of the first session object.

[0058] The display position of an identifier refers to its location on the interface. This position can be understood as a point, defined within a coordinate system (e.g., the bottom left corner as the origin, the horizontal x-axis, and the vertical y-axis). The display position is a point within that coordinate system. For example, if the identifier is an avatar, its display position can be understood as the center of gravity of the avatar on the interface. If the avatar is displayed as a circle, its display position can be understood as the center of the circle on the interface. Similarly, if the identifier is a name, its display position can be understood as the center of the name on the interface. If the name is displayed as a rectangle, its display position can be understood as the center of the rectangle on the interface.

[0059] A message preview window is a window used to display preview session messages. The display style of the message preview window can include any of the following: rectangle, rounded rectangle, ellipse, circle. Of course, the display style of the message preview window can also be other regular shapes or irregular shapes, which are not limited in this application embodiment.

[0060] In one possible implementation, based on the display position of the identifier of the first session object, a message preview window of the first session object is displayed on top of the session object selection interface.

[0061] In one possible implementation, a message preview window of the first session object is displayed around the display position of the first session object's identifier.

[0062] Step 204: In the message preview window of the first session object, display the preview session message of the first session object.

[0063] In this embodiment, the preview session message is a session message selected from the session messages of the first session object for the user to preview. The session messages of the first session object refer to the session messages exchanged between the first session object and the logged-in user account before receiving the message preview instruction. The session messages of the first session object may include at least one of the following: historical read session messages, unread session messages, and session messages related to the logged-in user account (e.g., session messages @login user account). For example, the client can select more important session messages from the session messages of the first session object as preview session messages and display them in the message preview window. The process of determining the preview session messages will be described in detail in the following embodiments.

[0064] In a possible implementation, in response to a message preview command for the first session object, a message preview window for the first session object is displayed based on the display position of the identifier item of the first session object, and a preview session message of the first session object is displayed in the message preview window of the first session object. That is, steps 203 and 204 can be executed simultaneously, displaying the preview session message of the first session object while simultaneously displaying the message preview window of the first object.

[0065] In a possible implementation, in response to a message preview command for the first session message, after displaying the message preview window of the first session object based on the display position of the identifier item of the first session object, the preview session message of the first session object is displayed in the message preview window of the first session object. That is, step 203 is executed first, followed by step 204.

[0066] In a possible implementation, the size of the message preview window can be adjusted based on the length of the preview session message; that is, the size of the message preview window is adapted to the length and / or number of preview session messages.

[0067] In possible implementations, the preview session message display mode can include a bubble mode and a text mode. Bubble mode displays the session message as a bubble, while text mode displays the session message only as text. This preview session message display mode can be the default, can be set by the user, or can be determined by the session message display mode in the chat interface of the first session object before the client receives the message preview instruction (for example, the preview session message display mode is consistent with the session message display mode in the chat interface of the first session object).

[0068] For example, such as Figure 7 As shown, the example uses a message list interface as the conversation object selection interface and avatars as the identifier. The message list interface 700 includes avatars of at least one conversation object: the avatar of "Group A", the avatar of "M", the avatar of "Q", and the avatar of "K". If a user wants to preview the conversation messages of "Group A", the user long-presses the avatar 710 of "Group A" to cause the client to receive a message preview command for "Group A". In response to the message preview command for "Group A", the client displays a message preview window 720 for "Group A" based on the display position of the avatar 710 of "Group A". The preview conversation messages of "Group A" are displayed in the message preview window 720. In related technologies, users can only see one conversation message in the message list interface, prioritizing content retrieval and failing to achieve efficient message processing / browsing capabilities. In this embodiment, the client provides message preview capabilities, allowing users to view selected important messages directly in the message preview window. Switching from the message list interface to the message preview window is simple and has a low browsing threshold.

[0069] For example, such as Figure 8As shown, the example of the conversation object selection interface serving as the object search interface will be used for explanation. When a user enters "voice" in the search box 810, the client identifies the following conversation objects based on the keyword "voice": "Voice PPT Design," "Voice Assistant Solution Group," and "Voice Control Design." To preview the conversation messages for the "Voice Assistant Solution Group," the user long-presses the avatar 820 of the "Voice Assistant Solution Group," causing the client to receive a message preview command for that group. In response to this command, the client displays a message preview window 830 for the "Voice Assistant Solution Group," based on the display position of the avatar 820. The preview conversation messages for the "Voice Assistant Solution Group" are then displayed in the message preview window 830. When a user searches for a conversation object, they need conversation messages to help remember whether the target conversation object is the one being searched. In this case, the user can long-press the avatar of the conversation object to quickly preview important conversation messages, improving search efficiency.

[0070] In summary, the technical solution provided in this application embodiment receives a message preview instruction for any session object in the session object selection interface, displays the message preview window of the session object based on the display position of the identifier item of the session object, and displays the preview session message of the session object in the message preview window of the session object. This application embodiment can preview session messages without the user switching interfaces, which is simple to operate and highly efficient.

[0071] In addition, in this embodiment of the application, the message preview window of the session object is displayed based on the display position of the identifier item of the session object. The display position of the message preview window is more targeted, making it easier for users to know that the message preview window corresponds to the session object, thereby improving the user's information browsing efficiency.

[0072] In addition, the conversation messages displayed in the message preview window provided in this application embodiment are filtered from the conversation messages of the conversation object, rather than simply displaying the conversation messages of the conversation object. Therefore, the preview conversation messages displayed in this application embodiment can better meet the user's preview needs and improve the user's information processing efficiency.

[0073] Please refer to Figure 9 The diagram illustrates a flowchart of a method for displaying session messages according to another embodiment of this application. This method can be applied to a terminal, and in a possible implementation, it can be executed by a client of a target application in the terminal. The method may include the following steps.

[0074] Step 901: Display the session object selection interface, which includes an identifier for at least one session object.

[0075] For a description of step 901, please refer to the above embodiment; it will not be repeated here.

[0076] Step 902: Receive a message preview instruction for the first session object in at least one session object.

[0077] In one example, in response to a long press on the identifier item of the first session object, it is determined that a message preview instruction for the first session object has been received.

[0078] For example, taking the avatar of the session object as the identifier, the description is as follows: in response to a long press operation on the avatar of the first session object, it is determined that a message preview instruction for the first session object has been received.

[0079] For example, taking the name of the session object as the identifier, in response to a long press operation on the name of the first session object, it is determined that a message preview instruction for the first session object has been received.

[0080] In another example, in response to a triggering operation of the message preview control in the session object selection interface, the system enters message preview mode, which is a mode for previewing preview session messages between the logged-in user account and the session object; in response to a selection operation of the identifier item of the first session object, the system determines that a message preview instruction for the first session object has been received.

[0081] like Figure 10 As shown, the session object selection interface 1010 includes a message preview control 1011. When a user clicks on the message preview control 1011, the client receives a trigger operation for the message preview control 1011 and enters the message preview mode. When a user clicks on the "Group" identifier 1012 in the session object selection interface, the client receives a selection operation for the "Group" identifier, and the client confirms that it has received a message preview instruction for the "Group".

[0082] Step 903: In response to the message preview command for the first session object, display a mask overlay on top of the session object selection interface.

[0083] A mask is a semi-transparent layer.

[0084] In response to a message preview command for the first session object, the client overlays a mask on top of the session object selection screen. For example, the mask's size is the same as the size of the session object selection screen.

[0085] Step 904: Based on the overlay, display the identifier of the first session object at a display position consistent with the target display position.

[0086] The target display position refers to the display position of the identifier item of the first session object in the session object selection interface. Consistent with the target display position can be understood as the display position of the identifier item within, above, or below the overlay when the user looks at the overlay coinciding with its display position in the session object selection interface.

[0087] In one example, a target overlay region is removed from the overlay to reveal the identifier of the first session object; where the target overlay region refers to the portion of the overlay region that matches the display area of ​​the identifier of the first session object.

[0088] The display area for the identifier of the first session object refers to the area where the identifier of the first session object is displayed, and the size of the display area for the identifier of the first session object is the same as the size of the identifier of the first session object.

[0089] Matching the display area of ​​the identifier item of the first session object can be understood as having the same size as, being larger than, or being smaller than, the display area of ​​the identifier item of the first session object. Generally speaking, the size of the target overlay area is the same as the size of the display area of ​​the identifier item of the first session object.

[0090] By removing the target overlay area, when the user looks at the area corresponding to the target overlay area, that area will not be semi-transparent but fully transparent. Therefore, the identifier of the first session object can be seen by the user through the fully transparent area, while the identifiers of other session objects on the session object selection interface are semi-transparent.

[0091] In one possible implementation, the client removes the target overlay area from the overlay using an eraser to reveal the identifier of the first session object.

[0092] By removing the target overlay area to reveal the display identifier, the operation is simple, and the client does not need to re-render the identifier of the first session object, reducing client processing overhead. In this way, the identifier of the first session object seen by the user is actually the identifier in the session object selection interface. In this way, the display layer of the identifier of the first session object is lower than the display layer of the overlay.

[0093] In another example, the identifier of the first session object is rendered and displayed in a target area above or within the overlay; where the target area refers to the area corresponding to the display position of the identifier of the first session object.

[0094] In a possible implementation, the display position of the target area is consistent with the display position of the identifier item of the first session object. The display position of the target area can be understood as the display position of the target area on the top layer or in the top layer. The display position of the target area can be understood as a point, that is, a coordinate system is determined based on the top layer or the top layer (for example, the top layer or the lower left corner of the top layer or the top layer is taken as the origin, the horizontal direction is the x-axis, and the vertical direction is the y-axis). The display position of the target area is a coordinate point in this coordinate system.

[0095] In the target area above the overlay, the identifier of the first session object is rendered. The client only needs to determine the display position of the identifier of the first session object in the overlay, and then render the identifier of the first session object based on that display position. In this way, the display level of the rendered identifier of the first session object is higher than the display level of the overlay.

[0096] In the target area of ​​the overlay, the identifier of the first session object is rendered and displayed. The client needs to remove the portion of the overlay corresponding to the target area so that the identifier of the first session object can be rendered and displayed in that target area. In this way, the display hierarchy of the rendered identifier of the first session object is consistent with the display hierarchy of the overlay.

[0097] By rendering the identifier of the first session object, the size of the identifier can be flexibly adjusted. For example, the size of the rendered identifier can be the same as the size of the identifier in the session object selection interface; or, the size can be larger than the size in the session object selection interface; or, the size can be smaller than the size in the session object selection interface. When the identifier of the first session object includes an avatar and a name, the sizes of the rendered avatar and name can both be larger than the sizes of the avatar and name in the session object selection interface; or, the size of the rendered avatar is the same as the size of the avatar in the session object selection interface, and the size of the rendered name is larger than the size of the name in the session object selection interface; or, the size of the rendered avatar is larger than the size of the avatar in the session object selection interface, and the size of the rendered name is the same as the size of the name in the session object selection interface; or, the sizes of the rendered avatar and name are the same as the sizes of the avatar and name in the session object selection interface. This application embodiment does not limit this.

[0098] It should be noted that after the overlay is displayed on top of the conversation object selection interface, the identification items of other conversation objects, except for the identification item of the first conversation object, are displayed in a semi-transparent state. That is, the identification items of other conversation objects seen by the user will not be as clear as the identification item of the first conversation object. The attached figure does not show this effect. The attached figure is only illustrative and the text description should prevail.

[0099] Step 905: Display the message preview window of the first session object near the identifier of the first session object.

[0100] The proximity position of the identifier of the first session object refers to the position at a preset distance around the identifier of the first session object. The periphery of the identifier of the first session object can refer to the top, bottom, left, and right sides of the identifier of the first session object. The preset distance can be a default distance, or the preset distance can be adjusted according to the size of the overlay, which is not limited in this embodiment.

[0101] In one example, a message preview window for the first session object is displayed near the identifier of the first session object in the upper layer of the overlay. This approach simplifies the process by requiring the client to determine the location of the identifier of the first session object in the upper layer and then display the message preview window near that location. This reduces the client's processing overhead.

[0102] In another example, a message preview window for the first session object is displayed in the overlay, near the identifier of the first session object. In this approach, the client needs to remove a portion of the overlay that matches the size of the message preview window, thereby displaying the message preview window of the first session object in the corresponding display area.

[0103] Step 906: Select a fixed number of session messages from the session messages of the first session object as preview session messages.

[0104] The preset quantity can be a default quantity or a quantity set by the user. For example, the preset quantity can be 2, or it can be set by the user in the client, which can provide multiple values ​​for the user to choose from. By allowing users to set the preset quantity themselves, their preview needs can be better met. For example, if user 1 only needs to preview short conversation messages, then user 1 can set the preset quantity to a smaller value; conversely, if user 2 needs to preview as many conversation messages as possible, then user 2 can set the preset quantity to a larger value.

[0105] For example, a set number of session messages are selected as preview session messages from the session messages of the first session object based on a priority order. The priority order is used to indicate the priority of a session message as a preview session message.

[0106] It should be noted that if there are not enough session messages in the specified number, the client can choose to combine the session messages before or after the session messages that match the priority to make up the specified number of session messages as preview session messages. When the session messages before or after the session messages that match the priority cannot be combined to make up the specified number of session messages, the client can choose to display the largest number of session messages that is closest to the specified number as preview session messages and display a prompt message to inform the user that there are not enough session messages in the preview session messages.

[0107] In possible implementations, the priority order includes first priority and second priority, with the second priority being lower than the first priority. The client can determine the preview session message in the following way:

[0108] Step 906a: Determine the session message that matches the first priority from the session messages of the first session object.

[0109] In one possible implementation, the client searches for the session message of the first session object in the message cache. If the session message of the first session object exists, it determines the session message with the first priority from the session messages of the first session object; if the session message of the first session object does not exist, it displays a prompt message in the message preview window indicating that the session message of the first session object does not exist.

[0110] Message caching can refer to in-memory message caching. The client first searches for the session message of the first session object in the in-memory message cache. If the corresponding message is not cached in memory, the client will search the corresponding session message database (generally, this session message database caches a maximum of 200 data entries) and cache the result in memory. Since caching the result in memory is a time-consuming operation, the client can display a loading prompt message to inform the user that the client is searching for the session message of the first session object, avoiding the abrupt feeling of the preview session message suddenly appearing after a long period of blankness in the message preview window.

[0111] Step 906b: If the first session object's session messages include session messages that match the first priority, select a fixed number of session messages that match the first priority as preview session messages.

[0112] For a prepared first session object, the client first looks for session messages that match the first priority. If the first session object includes session messages that match the first priority, a set number of session messages that match the first priority are selected as preview session messages.

[0113] Step 906c: If the session messages of the first session object do not include a session message matching the first priority, determine the session message matching the second priority from the session messages of the first session object.

[0114] Once the client determines that the session messages of the first session object do not contain a session message matching the first priority, the client determines the session message matching the second priority from the session messages of the first session object.

[0115] Step 906d: Select a set number of session messages that match the second priority as preview session messages.

[0116] If the client determines that the session messages of the first session object include session messages that match the second priority, the client selects a fixed number of session messages that match the second priority as preview session messages.

[0117] In possible implementations, assuming the priority order also includes a third priority or even more priorities, if the client determines that the session messages of the first session object do not include a session message matching the second priority, the client can continue to select session messages matching each priority in sequence according to the priority order.

[0118] In possible implementations, the first priority refers to the session message related to the logged-in user account, and the second priority refers to the latest session message. The session message related to the logged-in user account can be a session message mentioning the logged-in user account, or a session message from a user who mentions the logged-in user account. Of course, in other possible implementations, the session message related to the logged-in user account can also be other session messages; this application embodiment does not limit this. The second priority refers to the latest session message, which is the session message in the first session object that is closest to the current time. The current time can refer to the time when the message preview instruction was received. The rules for determining the first and second priorities can be preset by a technician or set by the user; this application embodiment does not limit this.

[0119] In one possible implementation, taking the session message with the first priority being @login user account as an example, the client can use the latest session message with the @login user account and the session messages before, after, or including the messages before and after it as preview session messages from the session messages of the first session object.

[0120] like Figure 11 As shown, this example uses a session message with the highest priority being @login user account and a maximum quantity of 2 as an example for explanation. Figure 11 The message preview window 1100 in the middle displays the session messages of the @login user account.

[0121] like Figure 12 As shown, this example uses the latest session message as the second priority and a fixed quantity of 2 as an example for explanation. Figure 12 The message preview window 1200 in the middle displays the latest session messages.

[0122] like Figure 13 As shown, in the absence of a session message from the first session object, Figure 13 The message preview window 1300 displays a prompt message indicating that a session message for a first session object does not exist. Of course, in other possible implementations, if a session message for a first session object does not exist, the message preview window may not be displayed, or the message preview window may be displayed but the prompt message may not be displayed; that is, only a message preview window may be displayed, but the message preview window may not contain any content.

[0123] In one possible implementation, the client determines the preview session message in the following way:

[0124] 1. Display priority selection options in the message preview window, which include multiple priorities.

[0125] 2. Obtain the target priority selected in the priority selection options.

[0126] 3. Determine the session message that matches the target priority from the session messages of the first session object.

[0127] 4. Select a set number of session messages that match the target priority as preview session messages.

[0128] like Figure 14As shown, the message preview window 1410 displays a priority selection option 1411, which includes multiple priorities: first priority, second priority, etc. (first priority has the highest priority, second priority is next, and so on). When the user selects first priority as the target priority in priority selection option 1411, the client retrieves the target priority selected by the user: first priority. The client then determines the session messages matching the first priority from the session messages of the first session object and selects a predetermined number of session messages matching the first priority as preview session messages. By allowing the user to select a target priority, the preview session messages displayed in the message preview window can better meet the user's preview needs.

[0129] In a possible implementation, the client displays a predetermined number of the latest session messages matching the target priority in a message preview window; receives a message switching instruction, which is an instruction to switch the currently displayed session messages in the message preview window to session messages at the target time point; and, in response to the message switching instruction, displays a predetermined number of preview session messages at the target time point matching the target priority in the message preview window.

[0130] For example, in response to receiving a swipe down or swipe left on the message preview window, it is determined that a message switching instruction has been received. This message switching instruction is an instruction to switch the currently displayed session message in the message preview window to the session message at the most recent time before the current time. For instance, if the currently displayed session message is the session message at time point 1, then in response to the message switching instruction, the client displays a predetermined number of preview session messages at time point 2 that match the target priority in the message preview window. Time point 2 is the time point before time point 1 where the session message with the target priority exists.

[0131] For example, in response to receiving an up or right swipe operation triggered on the message preview window, it is determined that a message switching instruction has been received. This message switching instruction is an instruction to switch the currently displayed session message in the message preview window to the session message at the most recent time after the current time. For instance, if the currently displayed session message is the session message at time point 1, then in response to the message switching instruction, the client displays a predetermined number of preview session messages at time points 3 that match the target priority in the message preview window. Time points 3 are the most recent time points after time point 1 where a session message with the target priority exists.

[0132] Of course, in other possible implementations, a first message switching control and a second message switching control can be displayed in the message preview window or around the message preview window. The first message switching control is a control used to trigger the switching of the currently displayed session message to the session message of the most recent moment before the current moment, and the second message switching control is a control used to trigger the switching of the currently displayed session message to the session message of the most recent moment after the current moment.

[0133] It should be noted that if there are no preview session messages at time point 2 matching the target priority, the client can display a first prompt message indicating that the current time is the earliest time point where a set number of session messages matching the target priority exists. If there are no preview session messages at time point 3 matching the target priority, the client can display a second prompt message indicating that the current time point is the latest time point where a set number of session messages matching the target priority exists. Alternatively, in a possible implementation, if there are no preview session messages at time point 2 or time point 3 matching the target priority, the client can display a third prompt message indicating whether to switch to a preview session message at the current time point matching the set number of messages matching the next or previous priority.

[0134] Step 907: In the message preview window of the first session object, display the preview session message of the first session object.

[0135] In this embodiment of the application, the preview session message is a session message that is selected from the session messages of the first session object for the user to preview.

[0136] For a description of step 907, please refer to the above embodiment; it will not be repeated here.

[0137] In summary, the technical solution provided in this application embodiment, by removing the target overlay area to reveal the display identifier, is simple to operate, and the client does not need to re-render the identifier of the first session object, thus reducing the client's processing overhead.

[0138] The size of the identifier of the first session object can be flexibly adjusted by rendering and displaying it in or on top of the mask.

[0139] By selecting a fixed number of session messages from the first session object's session messages based on priority, the preview session messages displayed in the message preview window can be more focused, improving the user's preview efficiency. On the other hand, displaying only a fixed number of session messages can highlight the key points, making it easier for users to preview quickly.

[0140] The following example illustrates this application using the first priority being the session message of the logged-in user account (hereinafter referred to as @ message), and the second priority being the latest session message with a fixed quantity of 2. Figure 15 As shown, it illustrates a flowchart of a method for displaying session messages provided in another embodiment of this application.

[0141] This method may include the following steps:

[0142] Step 1501: The user triggers a message preview command on the client.

[0143] Receiving a message preview command on the client side can be understood as the client entering message preview mode, meaning the client has the ability to quickly preview messages. For example, a user can trigger the client to receive a message preview command by long-pressing the avatar of a conversation object.

[0144] Step 1502: The client searches for the session message of the first session object. If it is determined that the session message of the first session object does not exist, proceed to step 1503; if it is determined that the session message of the first session object exists, proceed from step 1504.

[0145] The session messages of the first session object can also be called message records.

[0146] Step 1503: The client displays a prompt message.

[0147] The prompt message is used to indicate that a session with a non-existent first session object is present.

[0148] Step 1504: The client determines whether there is an @ message in the session messages of the first session object. If it determines that there is an @ message in the session messages of the first session object, proceed to step 1505; if it determines that there is no @ message in the session messages of the first session object, proceed to step 1506.

[0149] Step 1505: The client displays the latest @ message and the previous message.

[0150] Step 1506: The client displays the two latest messages.

[0151] In an illustrative embodiment, the client receives a preview exit instruction for a first session object, which is an instruction to exit the preview session message between the logged-in user account and the session object; in response to the preview exit instruction, the message preview window is canceled.

[0152] In one possible implementation, after the client displays a preview session message of the first session object in the message preview window of the first session object, it cancels the display of the message preview window in response to a touch removal operation on the identifier item of the first session object.

[0153] For example, when a user removes their finger from the identifier of the first session object, the client receives a touch removal operation for the identifier of the first session object, and the client cancels the display of the message preview window. After canceling the display of the message preview window, the client can display the session object selection interface. The user can cancel the display of the message preview window simply by removing their finger from the identifier of the first session object, making the operation simple.

[0154] Users can enter message preview mode by long-pressing the avatar of a conversation partner in the message list interface. Once in this mode, they can view important information about that conversation partner. When they release their finger, they exit the mode and return to the message list interface, allowing users to quickly preview important message content on the home page without having to enter the chat conversation interface.

[0155] In one possible implementation, a preview exit control is displayed on or around the message preview window, and the message preview window is canceled in response to a triggering operation on the preview exit control.

[0156] In an illustrative embodiment, the client receives a session interface display instruction, which is an instruction for displaying the chat session interface; in response to the session interface display instruction, the message preview window is canceled; and the chat session interface between the logged-in user account and the first session object is displayed.

[0157] For example, after the client displays the preview session message of the first session object in the message preview window of the first session object, it cancels the display of the message preview window and displays the chat session interface of the first session object in response to a swipe operation from the identifier item of the first session object to the message preview window.

[0158] For example, when a user slides their finger from the identifier of the first conversation object to the message preview window, the client cancels the display of the message preview window and displays the chat conversation interface of the first conversation object. The user only needs to slide their finger from the identifier of the first conversation object to the message preview window to display the chat conversation interface of the first conversation object; the operation is simple and the interface switching is more natural and smooth.

[0159] In the illustrative embodiment, the client may also perform the following steps:

[0160] 1. Receive a selection instruction for the identifier item of a second session object in at least one session object.

[0161] The second session object refers to any one or more session objects other than the first session object in the session object selection interface.

[0162] The identifier of the second session object may include at least one of the following: the avatar of the second session object, and the name of the second session object.

[0163] In one example, in response to a click on an identifier item of a second session object, it is determined that a selection instruction for an identifier item of the second session object has been received.

[0164] For example, when a user clicks on the avatar of the second session object, the client receives a click operation on the avatar of the second session object, thereby determining that a selection instruction for the identifier item of the second session object has been received.

[0165] In one possible implementation, when the client enters message preview mode, the user can click on the identifier item of a session object, triggering the client to receive a click operation for that session object's identifier item, thus confirming that a selection instruction for that session object's identifier item has been received. In message preview mode, the user only needs to click on the identifier items of different session objects to allow the client to switch between displaying message preview windows for different session objects, making the operation simple.

[0166] In another example, in response to a swipe operation from an identifier item of a first session object to an identifier item of a second session object, it is determined that a selection instruction for an identifier item of the second session object has been received.

[0167] In a possible implementation, in response to a long press and slide operation from the identifier item of the first session object to the identifier item of the second session object, it is determined that a selection instruction for the identifier item of the second session object has been received.

[0168] For example, when a user's finger slides from the avatar of the first session object to the avatar of the second session object, the client receives a sliding operation from the identifier item of the first session object to the identifier item of the second session object, thereby determining that a selection instruction for the identifier item of the second session object has been received.

[0169] 2. In response to the selection command for the identifier item of the second session object, display the message preview window of the second session object based on the display position of the identifier item of the second session object.

[0170] The display method of the message preview window of the second session object is the same as or similar to the display method of the message preview window of the first session object. For the description of how to display the message preview window of the second session object, please refer to the description of the message preview window of the first session object in the above embodiment, which will not be repeated here.

[0171] 3. In the message preview window of the second session object, the preview session message of the second session object is displayed.

[0172] For details on how to determine the preview session message of the second session object, please refer to the above embodiment for the description of the preview session message of the first session object, which will not be repeated here.

[0173] Let's take the profile picture as an example for explanation, such as... Figure 16 As shown, when a user's finger moves from the avatar 1610 of the first session object "Group" to the avatar 1620 of the second session object "Q", the client receives a swipe operation from the avatar of the first session object to the avatar of the second session object, thus confirming that a selection instruction for the avatar of the second session object has been received. The client then displays a message preview window 1630 for the second session object "Q" and displays a preview session message for the second session object "Q" in the message preview window 1630.

[0174] This application embodiment allows the client to display preview session messages of the second session object by switching from the identifier of the first session object to the identifier of the second session object, which is simple to operate.

[0175] It should be noted that the above embodiments are only described using the example of the first session object and the second session object including one session object. In practical applications, the first session object and / or the second session object may include multiple session objects, and this application embodiment does not limit this.

[0176] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0177] Please refer to Figure 17 This diagram illustrates a block diagram of a session message display device according to an embodiment of this application. The device has the functionality to implement the above-described session message display method example; this functionality can be implemented in hardware or by hardware executing corresponding software. The device can be a terminal or can be installed within a terminal. The device 1700 may include:

[0178] The interface display module 1710 is used to display a session object selection interface, which includes at least one identifier item for a session object.

[0179] Instruction receiving module 1720 is used to receive a message preview instruction for the first session object among the at least one session object;

[0180] The window display module 1730 is used to display a message preview window of the first session object in response to a message preview command for the first session object, based on the display position of the identifier item of the first session object;

[0181] The message display module 1740 is used to display preview session messages of the first session object in the message preview window of the first session object, wherein the preview session messages are session messages selected from the session messages of the first session object for user preview.

[0182] In summary, the technical solution provided in this application embodiment receives a message preview instruction for any session object in the session object selection interface, displays the message preview window of the session object based on the display position of the identifier item of the session object, and displays the preview session message of the session object in the message preview window of the session object. This application embodiment can preview session messages without the user switching interfaces, which is simple to operate and highly efficient.

[0183] In addition, in this embodiment of the application, the message preview window of the session object is displayed based on the display position of the identifier item of the session object. The display position of the message preview window is more targeted, making it easier for users to know that the message preview window corresponds to the session object, thereby improving the user's information browsing efficiency.

[0184] In addition, the conversation messages displayed in the message preview window provided in this application embodiment are filtered from the conversation messages of the conversation object, rather than simply displaying the conversation messages of the conversation object. Therefore, the preview conversation messages displayed in this application embodiment can better meet the user's preview needs and improve the user's information processing efficiency.

[0185] In an illustrative embodiment, the window display module 1730 includes:

[0186] A mask display unit (not shown in the figure) is used to overlay a mask on the top layer of the session object selection interface;

[0187] The identifier display unit (not shown in the figure) is used to display the identifier of the first session object at a display position consistent with the target display position based on the overlay; wherein, the target display position refers to the display position of the identifier of the first session object in the session object selection interface;

[0188] A window display unit (not shown in the figure) is used to display a message preview window of the first session object in a position adjacent to the identifier item of the first session object.

[0189] In an illustrative embodiment, the identifier display unit is used for:

[0190] Remove the target overlay area from the overlay to reveal the identifier of the first session object;

[0191] The target overlay region refers to the portion of the overlay region that matches the display area of ​​the identifier item of the first session object.

[0192] In an illustrative embodiment, the identifier display unit is used for:

[0193] The identifier item of the first session object is rendered and displayed in the target area above the overlay or in the overlay.

[0194] The target area refers to the area corresponding to the display position of the identifier item of the first session object.

[0195] In an illustrative embodiment, the instruction receiving module 1720 is further configured to receive a selection instruction for the identifier item of the second session object in the at least one session object;

[0196] The window display module 1730 is also configured to, in response to a selection instruction for the identifier item of the second session object, display a message preview window of the second session object based on the display position of the identifier item of the second session object;

[0197] The message display module 1740 is also used to display the preview session message of the second session object in the message preview window of the second session object.

[0198] In an illustrative embodiment, the instruction receiving module is configured to:

[0199] In response to a click operation on an identifier item of the second session object, it is determined that a selection instruction for an identifier item of the second session object has been received;

[0200] or,

[0201] In response to a swipe operation from the identifier of the first session object to the identifier of the second session object, it is determined that a selection instruction for the identifier of the second session object has been received.

[0202] In an illustrative embodiment, the device further includes:

[0203] A message determination module (not shown in the figure) is used to select a fixed number of session messages from the session messages of the first session object as the preview session messages based on a priority order, wherein the priority order is used to indicate the priority of the session messages as the preview session messages.

[0204] In an illustrative embodiment, the priority order includes a first priority and a second priority, wherein the second priority is lower than the first priority;

[0205] The message determination module is used for:

[0206] Determine the session message that matches the first priority from the session messages of the first session object;

[0207] If the first session object's session messages include session messages that match the first priority, then a fixed number of session messages that match the first priority are selected as the preview session messages.

[0208] If the session messages of the first session object do not include a session message matching the first priority, determine the session message matching the second priority from the session messages of the first session object;

[0209] Select a set number of session messages that match the second priority as the preview session messages.

[0210] In an illustrative embodiment, the first priority refers to session messages related to the logged-in user account, and the second priority refers to the latest session message.

[0211] In an illustrative embodiment, the message determination module is configured to:

[0212] The message preview window displays priority selection options, which include multiple priorities.

[0213] Obtain the target priority selected in the priority selection options;

[0214] Determine the session message that matches the target priority from the session messages of the first session object;

[0215] Select a set number of session messages that match the target priority as the preview session messages.

[0216] In an illustrative embodiment, the window display module 1730 is further configured to:

[0217] In response to a touch removal operation on the identifier item of the first session object, the message preview window is canceled from display.

[0218] In an illustrative embodiment, the interface display module 1710 is further configured to:

[0219] In response to a swipe operation from the identifier of the first conversation object to the message preview window, the message preview window is de-displayed, and the chat conversation interface of the first conversation object is displayed.

[0220] In an illustrative embodiment, the instruction receiving module 1720 is configured to:

[0221] In response to a long press operation on the identifier item of the first session object, it is determined that a message preview instruction for the first session object has been received;

[0222] or,

[0223] In response to a trigger operation on the message preview control in the selection interface for the session object, the system enters the message preview mode, which is a mode for previewing preview session messages between the logged-in user account and the session object; in response to a selection operation on the identifier item of the first session object, the system determines that a message preview instruction for the first session object has been received.

[0224] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0225] Please refer to Figure 18 This diagram illustrates a structural block diagram of a terminal 1800 provided in one embodiment of this application. The terminal 1800 can be a mobile phone, tablet computer, smart TV, multimedia playback device, PC, etc. Figure 1 The first terminal or the second terminal described in the embodiments.

[0226] Typically, terminal 1800 includes a processor 1801 and a memory 1802.

[0227] Processor 1801 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1801 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1801 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1801 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 1801 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0228] The memory 1802 may include one or more computer-readable storage media, which may be non-transitory. The memory 1802 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices.

[0229] In some embodiments, the terminal 1800 may also optionally include a peripheral device interface 1803 and at least one peripheral device. The processor 1801, memory 1802, and peripheral device interface 1803 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1803 via a bus, signal line, or circuit board. Specifically, the peripheral device may include at least one of a display screen 1804, audio circuitry 1805, communication interface 1806, and power supply 1807.

[0230] Those skilled in the art will understand that Figure 18 The structure shown does not constitute a limitation on terminal 1800 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0231] In an illustrative embodiment, a terminal is also provided, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set, or instruction set. The at least one instruction, at least one program, code set, or instruction set is configured to be executed by one or more processors to implement the aforementioned method for displaying session messages.

[0232] In an illustrative embodiment, a computer-readable storage medium is also provided, which stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set implements the above-described method for displaying session messages when executed by the processor of a terminal.

[0233] Optionally, the aforementioned computer-readable storage medium may be ROM (Read-Only Memory), RAM (Random Access Memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk, and optical data storage device, etc.

[0234] In an exemplary embodiment, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. The processor of the terminal reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the terminal to perform the aforementioned method for displaying session messages.

[0235] It should be understood that "multiple" as used herein refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. Furthermore, the step numbers described herein are merely illustrative of one possible execution order. In some other embodiments, the steps may not be executed in numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0236] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0237] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for displaying conversation messages, characterized in that, The method includes: Display a session object selection interface, which includes at least one identifier for a session object; In response to a touch operation on the identifier of the first session object in the at least one session object, a mask is overlaid on the top layer of the session object selection interface; Based on the overlay, the identifier of the first session object is displayed at a display position consistent with the target display position; wherein, the target display position refers to the display position of the identifier of the first session object in the session object selection interface; A message preview window for the first session object is displayed near the identifier of the first session object. In the message preview window of the first session object, a preview session message of the first session object is displayed. The preview session message is a session message that is selected from the session messages of the first session object and matches the first priority. The first priority refers to the session messages related to the logged-in user account. In response to a swipe operation from the identifier of the first session object to the identifier of the second session object, a message preview window of the second session object is displayed based on the display position of the identifier of the second session object.

2. The method according to claim 1, characterized in that, The step of displaying the identifier of the first session object at a display position consistent with the target display position based on the overlay includes: Remove the target overlay area from the overlay to reveal the identifier of the first session object; The target overlay region refers to the portion of the overlay region that matches the display area of ​​the identifier item of the first session object.

3. The method according to claim 1, characterized in that, The step of displaying the identifier of the first session object at a display position consistent with the target display position based on the overlay includes: The identifier item of the first session object is rendered and displayed in the target area above the overlay or in the overlay. The target area refers to the area corresponding to the display position of the identifier item of the first session object.

4. The method according to claim 1, characterized in that, The method further includes: In response to a click operation on the identifier item of the second session object, the step of displaying the message preview window of the second session object based on the display position of the identifier item of the second session object is performed.

5. The method according to claim 1, characterized in that, Before displaying the preview session message of the first session object in the message preview window of the first session object, the method further includes: Based on a priority order, a fixed number of session messages are selected from the session messages of the first session object as the preview session messages, wherein the priority order is used to indicate the priority of the session messages as the preview session messages.

6. The method according to claim 5, characterized in that, The priority order includes a first priority and a second priority, wherein the second priority is lower than the first priority; The step of selecting a predetermined number of session messages as the preview session messages from the session messages of the first session object based on priority order includes: Determine the session message that matches the first priority from the session messages of the first session object; If the first session object's session messages include session messages that match the first priority, then a fixed number of session messages that match the first priority are selected as the preview session messages. If the session messages of the first session object do not include a session message matching the first priority, determine the session message matching the second priority from the session messages of the first session object; Select a set number of session messages that match the second priority as the preview session messages.

7. The method according to claim 6, characterized in that, The second priority refers to the latest session message.

8. The method according to claim 5, characterized in that, The step of selecting a predetermined number of session messages as the preview session messages from the session messages of the first session object based on priority order includes: The message preview window displays priority selection options, which include multiple priorities. Obtain the target priority selected in the priority selection options; Determine the session message that matches the target priority from the session messages of the first session object; Select a set number of session messages that match the target priority as the preview session messages.

9. The method according to claim 1, characterized in that, After displaying the preview session message of the first session object in the message preview window of the first session object, the method further includes: In response to a swipe operation from the identifier of the first conversation object to the message preview window, the message preview window is de-displayed, and the chat conversation interface of the first conversation object is displayed.

10. The method according to any one of claims 1 to 9, characterized in that, The step of overlaying a mask on top of the session object selection interface in response to a touch operation on the identifier of a first session object among the at least one session object includes: In response to a long press operation on the identifier item of the first session object, an overlay is displayed on top of the session object selection interface; or, In response to a trigger operation on the message preview control in the session object selection interface, the system enters the message preview mode, which is a mode for previewing preview session messages between the logged-in user account and the session object; in response to a selection operation on the identifier item of the first session object, a mask is overlaid on the top layer of the session object selection interface.

11. A device for displaying conversation messages, characterized in that, The device includes: The interface display module is used to display a session object selection interface, which includes at least one identifier item for a session object. A window display module is used to overlay a mask on the top layer of the session object selection interface in response to a touch operation on the identifier item of the first session object in the at least one session object. The window display module is further configured to display the identifier of the first session object at a display position consistent with the target display position based on the mask; wherein, the target display position refers to the display position of the identifier of the first session object in the session object selection interface; The window display module is also used to display a message preview window of the first session object near the identifier item of the first session object; The message display module is used to display preview session messages of the first session object in the message preview window of the first session object. The preview session messages are session messages that are filtered from the session messages of the first session object and match a first priority. The first priority refers to session messages related to the logged-in user account. The message display module is further configured to respond to a sliding operation from the identifier of the first session object to the identifier of the second session object, and display a message preview window of the second session object based on the display position of the identifier of the second session object.

12. A terminal, characterized in that, The terminal includes a processor and a memory, the memory storing at least one program, which is loaded and executed by the processor to implement the method for displaying session messages as described in any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that, The storage medium stores at least one program, which is loaded and executed by a processor to implement the method for displaying session messages as described in any one of claims 1 to 10.

14. A computer program product, characterized in that, The computer program product includes a computer program that is loaded and executed by a processor to implement the method for displaying session messages as described in any one of claims 1 to 10.

Images