Session message processing method, device, equipment, storage medium and program product
Patent Information
- Application Number
- CN202210889534.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-25
- Publication Date
- 2026-10-27
- Estimated Expiration
- 2042-07-25
AI Technical Summary
[0003]相关技术中,用户基于会话界面进行会话过程中,会话消息按照发送时间在会话界面中排序,会出现自己要发的连续消息被别人的消息穿插的现象,消息的传达效率低
[0078]在目标对象的会话界面中,当目标对象触发指示合并第一会话消息及第二会话消息的消息合并指令时,在会话界面中,显示第一会话消息与第二会话消息合并得到的第三会话消息;如此,目标对象触发消息合并指令,由于消息合并指令指示合并第一会话消息及第二会话消息,也即目标对象指定对第一会话消息与第二会话消息进行合并,电子设备能够响应该消息合并指令,在会话界面中,实现对目标对象指定的第一会话消息与第二会话消息的合并,提高了消息的传达效率,同时,相较于相关技术中仅依据消息的发送时间,在会话界面中进行消息展示,提高了电子设备硬件处理资源及显示资源的利用率。
Smart Images

Figure CN117499356B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the fields of artificial intelligence and Internet technology, and in particular to a method, apparatus, device, storage medium and program product for processing conversational messages. Background Technology
[0002] Artificial intelligence (AI) is a comprehensive technology in computer science that attempts to understand the nature of intelligence and produce a new kind of intelligent machine that can react in a way similar to human intelligence. With the continuous development of AI technology, it has been increasingly applied to fields such as instant messaging.
[0003] In related technologies, during a user's conversation based on a chat interface, the chat messages are sorted in the chat interface according to the sending time. This can lead to a situation where the user's consecutive messages are interrupted by other users' messages, resulting in low message delivery efficiency. Summary of the Invention
[0004] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for processing conversation messages, which can realize message merging during a conversation and improve message transmission efficiency.
[0005] The technical solution of this application embodiment is implemented as follows:
[0006] This application provides a method for processing session messages, including:
[0007] In the target object's session interface, at least two session messages are displayed, including a first session message and a second session message;
[0008] The system receives a message merging instruction triggered by the target object, the message merging instruction being used to instruct the merging of the first session message and the second session message.
[0009] In response to the message merging instruction, a third session message, obtained by merging the first session message and the second session message, is displayed in the session interface.
[0010] This application embodiment also provides a session message processing apparatus, including:
[0011] The first display module is used to display at least two conversation messages in the conversation interface of the target object, wherein the at least two conversation messages include a first conversation message and a second conversation message;
[0012] The receiving module is configured to receive a message merging instruction triggered by the target object, wherein the message merging instruction is used to instruct the merging of the first session message and the second session message;
[0013] The second display module is used to respond to the message merging instruction and display the third session message obtained by merging the first session message and the second session message in the session interface.
[0014] In the above scheme, the first display module is further configured to respond to the drag operation of the target object on the first session message, and when the operation duration of the drag operation reaches the duration threshold, display the process of the first session message being dragged in the session interface;
[0015] The receiving module is further configured to receive the message merging instruction in response to the release of the drag operation when the first session message is dragged to the second session message.
[0016] In the above scheme, the first display module is further configured to obtain a first time interval between the sending time of the first session message and the current time when the operation duration of the drag operation reaches a duration threshold;
[0017] When the first time interval is less than or equal to the time interval threshold, the process of dragging the first session message is displayed in the session interface.
[0018] In the above scheme, the receiving module is further configured to, in response to the release of the drag operation, obtain a second time interval between the sending time of the second session message and the current time when the first session message is dragged to the second session message;
[0019] The message merging instruction is received when the second time interval is less than or equal to the time interval threshold.
[0020] In the above scheme, the receiving module is further configured to, in response to the release of the drag operation, obtain the sending time interval between the first session message and the second session message when the first session message is dragged to the second session message;
[0021] The message merging instruction is received when the sending time interval is less than or equal to the sending time interval threshold.
[0022] In the above scheme, the first display module is also used to display the message merging function item in the conversation interface;
[0023] The receiving module is also configured to control the at least two session messages to be in a candidate state in response to a trigger operation for the message merging function item;
[0024] In response to the selection operation for the first session message and the second session message in the candidate state, the message merging instruction is received.
[0025] In the above scheme, the second display module is further configured to display the process of the first session message automatically moving to the second session message when the sending time of the first session message is earlier than the sending time of the second session message, and to display the third session message obtained by merging the first session message and the second session message.
[0026] In the above scheme, the device further includes:
[0027] The first position adjustment module is used to move the position of the third session message in the session interface in response to the sorting adjustment instruction for the third session message, so as to change the message sorting of the third session message in the session interface.
[0028] In the above scheme, the receiving module is further configured to respond to the drag operation of the third session message, and when the operation duration of the drag operation reaches the duration threshold, trigger the sorting adjustment instruction of the third session message;
[0029] The first position adjustment module is also used to control the third session message to move synchronously in the session interface along with the execution of the drag operation, so as to change the message order of the third session message in the session interface.
[0030] In the above scheme, the second display module is also used to display the target area during the process of moving the position of the third session message;
[0031] When the third session message moves to the edge of the target area, a movement prompt message is displayed;
[0032] The movement prompt information is used to prompt the user to adjust the order of the third session messages within the target area.
[0033] In the above scheme, the second display module is further configured to, during the process of moving the position of the third session message, when the third session message moves to the target position, the target position makes the third session message adjacent to the target historical session message, and the sending time interval between the third session message and the target historical session message reaches a time interval threshold,
[0034] An intercept line is displayed between the third session message and the target historical session message. The intercept line is used to intercept the third session message when it moves to the intercept line.
[0035] In the above scheme, the third session message includes the first content corresponding to the first session message and the second content corresponding to the second session message; the device further includes:
[0036] The second position adjustment module is used to adjust the position of at least one of the first content and the second content in the third session message in response to the position adjustment instruction for the content in the third session message, so as to change the order of the first content and the second content in the third session message.
[0037] In the above scheme, when the first session message is sent to the target object and the second session message is sent to the session object of the target object,
[0038] The second display module is further configured to display a copy of the second session message;
[0039] The session interface displays a third session message obtained by merging the message copies of the first session message and the second session message.
[0040] In the above scheme, when the sending object of at least one of the first session message and the second session message is the session object of the target object, the first display module is also used to display authorization prompt information and corresponding confirmation function items;
[0041] The authorization prompt information is used to prompt for authorization to perform a merging operation on the session messages of the session object;
[0042] In response to a trigger operation for the determined function item, an authorization request is sent to the session object, the authorization request being used to request authorization to perform a merging operation of session messages for the session object;
[0043] The second display module is further configured to, when authorized to perform a merging operation on the session messages of the session object, display a third session message obtained by merging the first session message and the second session message in the session interface.
[0044] In the above scheme, when the first session message is sent to the target object and the second session message is sent to the session object of the target object,
[0045] The second display module is further configured to control the first session message to be in a selected state in response to a press operation on the first session message;
[0046] During the execution of the press operation, in response to the drag operation of the second session message, a copy of the second session message is displayed, and the process of dragging the copy of the second session message is displayed in the session interface;
[0047] The receiving module is further configured to receive the message merging instruction in response to the release of the drag operation when the second session message is dragged to the first session message.
[0048] In the above scheme, the second display module is also used to display the process of the fourth session message being dragged in the session interface in response to the drag operation of the fourth session message during the execution of the pressing operation;
[0049] When the fourth session message is dragged to the position of the third session message, in response to the release of the drag operation, the fifth session message, which is a combination of the fourth session message and the third session message, is displayed.
[0050] In the above scheme, the second display module is also used to display the number of merged session messages during the pressing operation.
[0051] In the above scheme, the first display module is also used to display merge guidance information in the session interface of the target object;
[0052] The merge guidance information is used to guide the target object to perform the target operation in order to trigger the message merge instruction.
[0053] In the above scheme, the device further includes a message processing module;
[0054] The second display module is further configured to display at least one message processing function item corresponding to the third session message after displaying the third session message obtained by merging the first session message and the second session message;
[0055] The message processing module is configured to, in response to a trigger operation on a target message processing function item among the at least one message processing function items, perform the target processing operation indicated by the target message processing function item on the third session message.
[0056] In the above scheme, the third session message includes at least two sub-contents;
[0057] The message processing module is further configured to, when the target message processing function item is a voting function item, display the voting message corresponding to the third session message in the session interface, wherein the voting message includes: options corresponding to each of the sub-contents and voting operation controls;
[0058] The voting control is used to vote on the sub-content selected based on the options.
[0059] In the above scheme, the message processing module is also used to display the voting results of the corresponding sub-contents in the associated areas of each sub-content in the voting message;
[0060] The voting result indicates the number of session objects that voted on the corresponding sub-content.
[0061] In the above scheme, the message processing module is further configured to, after displaying the voting message corresponding to the third session message, cancel the display of the voting operation control when the display duration of the voting message reaches a display duration threshold, and
[0062] The voting message displays an end indication message to indicate that the voting has ended.
[0063] In the above scheme, the message processing module is further configured to display at least one forwarding object for selection when the target message processing function item is a forwarding function item, wherein the forwarding object has a social association relationship with the target object;
[0064] In response to a selection instruction for a target forwarding object among the at least one forwarding objects, the third session message is sent to the target forwarding object.
[0065] In the above scheme, the message processing module is further configured to generate meeting minutes corresponding to the third session message in response to a trigger operation for the meeting minutes function when the target message processing function is a meeting minutes function.
[0066] In response to a storage instruction for the meeting minutes, the meeting minutes are stored.
[0067] In the above scheme, the third session message includes at least two sub-contents;
[0068] The message processing module is also used to perform semantic analysis on the content of the third session message and generate the title of the meeting minutes based on the analysis results;
[0069] Obtain the sending time corresponding to each of the sub-contents, and determine the summary time of the meeting minutes based on the obtained sending time;
[0070] Using the content of the third session message as the body of the meeting minutes, a meeting minutes including the title, the minutes time, and the body is generated.
[0071] In the above scheme, the second display module is further configured to, after displaying the third session message obtained by merging the first session message and the second session message in the session interface, in response to a message merging instruction for the third session message and the sixth session message, display the seventh session message obtained by merging the third session message and the sixth session message in the session interface.
[0072] This application also provides an electronic device, including:
[0073] Memory, used to store executable instructions;
[0074] The processor, when executing executable instructions stored in the memory, implements the session message processing method provided in the embodiments of this application.
[0075] This application also provides a computer-readable storage medium storing executable instructions, which, when executed by a processor, implement the session message processing method provided in this application.
[0076] This application also provides a computer program product, including a computer program or instructions, characterized in that, when the computer program or instructions are executed by a processor, they implement the session message processing method provided in this application.
[0077] The embodiments of this application have the following beneficial effects:
[0078] In the target object's session interface, when the target object triggers a message merging command that indicates merging the first and second session messages, the third session message resulting from the merging of the first and second session messages is displayed in the session interface. Thus, when the target object triggers a message merging command, since the message merging command indicates merging the first and second session messages, that is, the target object specifies that the first and second session messages should be merged, the electronic device can respond to the message merging command and realize the merging of the first and second session messages specified by the target object in the session interface, thereby improving the efficiency of message transmission. At the same time, compared with related technologies that only display messages in the session interface based on the message sending time, the utilization rate of the electronic device's hardware processing resources and display resources is improved. Attached Figure Description
[0079] Figure 1 This is a schematic diagram of the interface for message conversations in related technologies;
[0080] Figure 2 This is a schematic diagram of the architecture of the session message processing system 100 provided in the embodiments of this application;
[0081] Figure 3This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;
[0082] Figure 4 This is a flowchart illustrating the session message processing method provided in an embodiment of this application;
[0083] Figure 5 This is a schematic diagram of the interface for implementing message merging by dragging and dropping session messages, provided in an embodiment of this application.
[0084] Figure 6 This is a schematic diagram of the interface for timeout prompts during the message merging process provided in an embodiment of this application;
[0085] Figure 7 This is a schematic diagram of the trigger interface for the message merging instruction provided in this application embodiment;
[0086] Figures 8A to 8C This is a schematic diagram of the interface for sorting and adjusting merged session messages provided in an embodiment of this application;
[0087] Figures 9A to 9F A schematic diagram of an interface for merging different types of session messages provided in an embodiment of this application;
[0088] Figures 10A to 10C A schematic diagram of the interface for merging session messages from different session objects, provided as an embodiment of this application;
[0089] Figure 11 A schematic diagram of the interface for performing a merging operation provided in an embodiment of this application;
[0090] Figure 12 A schematic diagram of an interface showing the number of merged session messages provided for an embodiment of this application;
[0091] Figure 13A and Figure 13B A schematic diagram of an interface for message processing based on message processing function items provided in an embodiment of this application;
[0092] Figure 14 A schematic diagram of the interface for displaying voting results provided in an embodiment of this application;
[0093] Figure 15 This is a flowchart illustrating the session message processing method provided in an embodiment of this application;
[0094] Figure 16 This is a schematic diagram of the session message sending process provided in an embodiment of this application;
[0095] Figure 17 This is a schematic diagram of message composition provided in an embodiment of this application;
[0096] Figure 18This is a schematic diagram illustrating the composition of a protocol request packet provided in an embodiment of this application;
[0097] Figure 19 This is a schematic diagram illustrating the composition of the response packet provided in an embodiment of this application;
[0098] Figure 20 This is a schematic diagram of the preprocessing flow for message merging provided in an embodiment of this application;
[0099] Figure 21 This is a schematic diagram of the interaction process between the client and the server provided in the embodiments of this application;
[0100] Figure 22 This is a schematic diagram of the preprocessing flow for adjusting the position of the merge message provided in an embodiment of this application;
[0101] Figure 23 This is a schematic diagram of the interaction process when moving merged messages, provided in an embodiment of this application.
[0102] Figure 24 This is a schematic diagram comparing message signaling provided in an embodiment of this application;
[0103] Figure 25 This is a schematic diagram of the preprocessing flow for merging other people's messages provided in an embodiment of this application;
[0104] Figure 26 This is a schematic diagram of the message content structure provided in an embodiment of this application;
[0105] Figure 27 This is a schematic diagram of the message merging process provided in the embodiments of this application. Detailed Implementation
[0106] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0107] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0108] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.
[0109] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.
[0110] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.
[0111] 1) In response to, used to indicate the conditions or states on which the operation performed depends. When the conditions or states on which it depends are met, one or more operations performed may be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.
[0112] 2) Client: An application running on a terminal to provide various services. In this article, it refers to an instant messaging client or a client with session functionality, such as a video playback client, a game client, an educational client, etc.
[0113] Figure 1 This is a schematic diagram of the interface for message conversations in related technologies. See [link / reference]. Figure 1 During their research, the inventors discovered that in related technologies, messages in the chat interface are displayed in order of their sending time, which can lead to situations where one's own consecutive messages are interrupted by other people's messages. In group chats, when it is necessary to summarize the discussion content of multiple people in the group, one can only copy and summarize them one by one, resulting in very low message processing efficiency.
[0114] Based on the above explanation of the nouns and terms involved in the embodiments of this application, the session message processing system provided in the embodiments of this application is described below. See also: Figure 2 , Figure 2This is a schematic diagram of the architecture of the session message processing system 100 provided in the embodiments of this application. In order to support an exemplary application, the terminal (terminal 400-1 and terminal 400-2 are shown as examples, wherein client 410-1 is provided on terminal 400-1 and client 410-2 is provided on terminal 400-2) connects to server 200 through network 300. Network 300 can be a wide area network or a local area network, or a combination of the two, and data transmission is achieved using wireless or wired links.
[0115] In the scenario of conducting a message session, we will take terminal 400-1 as the target object's terminal and terminal 400-2 as the target object's session object's terminal as an example for explanation. In actual implementation, the number of session objects (terminals 400-2) of the target object can be one or more (i.e., at least two).
[0116] Server 200 is used to distribute messages sent by each member (target object or target object's session object) in the session to each member in the session;
[0117] Terminals 400-1 and 400-2 are used to display messages received from the server in the session interface.
[0118] Terminal 400-1 is also configured to, when the session messages displayed in the session interface are at least two session messages, including a first session message and a second session message, respond to a message merging instruction triggered by a target object, wherein the message merging instruction is used to instruct the merging of the first session message and the second session message.
[0119] The third session message, which is the result of merging the first and second session messages, is displayed in the session interface.
[0120] In practical applications, the terminal 400-1 is equipped with a client, such as an instant messaging client. The terminal runs the instant messaging client, enabling the target object to conduct message conversations based on the conversation interface displayed by the instant messaging client. In some embodiments, when the target object conducts a message conversation based on the conversation interface, the conversation interface displays at least two conversation messages, including a first conversation message and a second conversation message. The instant messaging client responds to the message merging instruction triggered by the target object. When the message merging instruction is used to indicate the merging of the first conversation message and the second conversation message, the third conversation message obtained by merging the first conversation message and the second conversation message is displayed in the conversation interface.
[0121] In practical applications, server 200 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminals (such as terminal 400-1) can be smartphones, tablets, laptops, desktop computers, smart home appliances (such as smart speakers and smart TVs), smartwatches, smart voice interaction devices, vehicle terminals, aircraft, etc., but are not limited to these. Terminals (such as terminal 400-1) and server 200 can be directly or indirectly connected via wired or wireless communication, which is not limited herein.
[0122] The hardware structure of the electronic device for the session message processing method provided in this application embodiment will be described in detail below. The electronic device includes, but is not limited to, a server or a terminal. For example, the electronic device may be... Figure 2 The terminals in the document (including terminal 400-1 and terminal 400-2). See also... Figure 3 , Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Figure 3 The illustrated electronic device 400 includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in the electronic device 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 3 The general labeled all buses as Bus System 440.
[0123] The processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.
[0124] User interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.
[0125] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.
[0126] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.
[0127] In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.
[0128] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;
[0129] The network communication module 452 is used to reach other computing devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.
[0130] Presentation module 453 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 (e.g., a display screen, a speaker, etc.) associated with user interface 430;
[0131] The input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.
[0132] In some embodiments, the session message processing apparatus provided in this application can be implemented in software. Figure 3A processing device 455 for session messages stored in memory 450 is shown. It may be software in the form of programs and plug-ins, including the following software modules: a first display module 4551, a receiving module 4552, and a second display module 4553. These modules are logically related and can therefore be arbitrarily combined or further divided according to the functions they implement. The functions of each module will be described below.
[0133] In other embodiments, the session message processing apparatus provided in this application can be implemented using a combination of hardware and software. As an example, the session message processing apparatus provided in this application can be a processor in the form of a hardware decoding processor, which is programmed to execute the session message processing method provided in this application. For example, the processor in the form of a hardware decoding processor can be one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), or other electronic components.
[0134] Based on the above description of the session message processing system and electronic device according to the embodiments of this application, the session message processing method provided by the embodiments of this application will be described below. See also Figure 4 , Figure 4 This is a flowchart illustrating the session message processing method provided in this application embodiment. In some embodiments, the session message processing method can be implemented by the server or terminal alone, or by the server and terminal working together. Taking terminal implementation as an example, the session message processing method provided in this application embodiment includes:
[0135] Step 101: The terminal displays at least two session messages, including a first session message and a second session message, in the session interface of the target object.
[0136] In practical applications, terminals typically have a client installed, such as an instant messaging client. Users (i.e., the target) can use the installed client to communicate instantly with other users, such as sending conversational messages in the form of voice, text, pictures, and animations, and making voice or video calls.
[0137] Here, the target object engages in message conversations with other conversation objects based on the conversation interface displayed by the client. The conversation corresponding to this conversation interface can be a group conversation (i.e., a conversation that includes at least three members) or a one-person conversation.
[0138] During the conversation, the target object's conversation interface displays conversation messages sent by the target object itself and those sent by other members in the conversation. In some embodiments, the target object's conversation interface displays multiple conversation messages, including a first conversation message and a second conversation message. The first conversation message and the second conversation message can both be sent by the target object, or one of them can be sent by the target object and the other by the target object's conversation object, or both can be sent by the target object's conversation object.
[0139] Step 102: In response to the message merging instruction triggered by the target object, the message merging instruction is used to indicate the merging of the first session message and the second session message. In the session interface, the third session message obtained by merging the first session message and the second session message is displayed.
[0140] In practical applications, the target user can trigger a message merging command to instruct the merging of two or more messages (e.g., three or more) in the conversation interface. In some embodiments, the message merging command is used to merge two messages selected by the target user (e.g., a first conversation message and a second conversation message). When the target user needs to merge three or more conversation messages, this can be achieved by triggering the message merging command multiple times. Thus, when multiple consecutive messages sent by the user (target user) are interrupted, merging the interrupted messages can prevent missed readings. When the user needs to summarize messages from multiple conversation objects in a group chat, message merging can be used to combine messages from different conversation objects, allowing messages from different conversation objects to be presented as a single message. This improves the efficiency of conversation message delivery and the user's message processing efficiency.
[0141] The triggering method of the message merging command is described below. In some embodiments, the target object can trigger the message merging command by dragging a session message in the session interface. Taking the target object dragging the first session message in the session interface and merging the session messages sent by the target object itself as an example, specifically, in response to the target object's drag operation on the first session message, when the drag operation meets the message movement conditions, the terminal displays the process of the first session message being dragged in the session interface. When the first session message is dragged to the second session message, in response to the release of the drag operation, the message merging command is triggered. Figure 5 This is a schematic diagram of the interface for implementing message merging by dragging and dropping session messages according to an embodiment of this application. See also... Figure 5Figure (1) shows the conversation interface that displays conversation messages based on the sending time of the messages. In Figure (1), it can be seen that the continuous messages "Let's go camping" and "The weather is so nice!" sent by the user are interrupted by the conversation object. Figure (2) shows the process of the user (target object) dragging the conversation message "Let's go camping" in the conversation interface. Figure (3) shows the interface when the user (target object) drags the conversation message "Let's go camping" to the conversation message "The weather is so nice!". Figure (4) shows the conversation message "Let's go camping" and the conversation message "The weather is so nice!" merged into one conversation message after the user (target object) releases the drag operation on the conversation message "Let's go camping" (i.e., releases the hand).
[0142] Here, the drag operation for the first session message can include continuously executed selection operations (such as click operation, long press operation, i.e., press operation when the press duration reaches the duration threshold) and pull operation for the first session message. The message movement condition can include at least one of the following: the operation duration reaches the duration threshold, or the operation trajectory length of the pull operation reaches the length threshold.
[0143] In practical applications, when a drag operation meets the message movement conditions, the terminal controls the first session message to be in a floating state, and displays the process of the first session message being dragged in the session interface as the drag operation is executed. Here, the terminal can display the first session message using a bubble card. When the terminal receives the first session message, it displays the first session message using a bubble card. When the target object's drag operation on the first session message meets the message movement conditions, it controls the bubble card carrying the first session message to be in a floating state, and displays the process of the bubble card being dragged in the session interface.
[0144] In some embodiments, a first session message is determined to be dragged to a second session message when at least one of the following conditions is met: the first session message is dragged to an associated area outside the display area of the second session message; or the bubble card carrying the first session message overlaps with the bubble card carrying the second session message. Here, in practical applications, when the target object drags the first session message, it means the target object has selected the first session message as the session message to be merged. Dragging the first session message to the second session message means the target object has selected the second session message as the session message to be merged with the first session message.
[0145] In scenarios where message merging commands are triggered by dragging session messages, in some embodiments, the target object can only drag session messages whose sending duration (i.e., the time interval from the message's sending time to the current time) is within a target duration range (which can be set according to actual needs). For example, if the target duration is one minute, the target object can only drag session messages whose sending time is within one minute of the current time. In actual implementation, when the drag operation meets the message movement conditions, the terminal obtains the first time interval between the sending time of the first session message and the current time. When the first time interval is less than or equal to the time interval threshold (i.e., the target duration), the dragging process of the first session message is displayed in the session interface. When the first time interval is greater than the time interval threshold, a timeout prompt is displayed. This timeout prompt indicates that the duration for merging the first session message has been exceeded. When the target object releases the drag operation based on the timeout prompt, the first session message is reset, i.e., returned to its position before dragging.
[0146] In other embodiments, the target object can only merge and send session messages whose duration is within the target duration. That is, the sending duration of both the first session message and the second session message must be within the target duration. Specifically, when the first session message is dragged to the second session message, in response to the release of the drag operation, the first sending duration of the first session message and the second sending duration of the second session message are obtained. When at least one of the first sending duration and the second sending duration exceeds the target duration, a timeout prompt message is displayed to remind the user that only session messages whose sending duration is within the target duration can be merged and sent, and the first session message is moved to the position before the above drag operation was executed. Figure 6 This is a schematic diagram of the interface for timeout prompts during the message merging process provided in this application embodiment. See also: Figure 6 When a user drags the conversation message "Let's go camping" to "The weather is so nice!" and releases the drag, because there are messages between "Let's go camping" and "The weather is so nice!" whose duration exceeds the target duration (1 minute in this case), a timeout message "Only messages within 1 minute can be merged" is displayed, and the dragged conversation message "Let's go camping" is reset to its original position before being dragged.
[0147] In other embodiments, the time interval between the first and second session messages indicated by the target object to be merged needs to be within a certain time range. That is, when the first session message is dragged to the second session message, in response to the release of the drag operation, the sending time interval between the sending time of the first session message and the sending time of the second session message is obtained. When the sending time interval is less than or equal to the sending time interval threshold, a message merging instruction is triggered. When the time interval is greater than the time interval threshold, an interval prompt message is displayed, and the first session message is moved to the position before the drag operation was executed. The interval prompt message is used to indicate that the sending time interval between the first and second session messages has exceeded the sending time interval threshold, and can further indicate the sending time interval at which message merging can be performed, such as indicating that the sending time interval at which message merging can be performed is 1 minute.
[0148] In some embodiments, the message merging instruction can also be triggered by a message merging function item. Specifically, the terminal displays a message merging function item in the session interface; in response to a triggering operation on the message merging function item, at least two session messages are controlled to be in a candidate state; in response to a selection operation on the first and second session messages in the candidate state, the message merging instruction is triggered. For example, Figure 7 This is a schematic diagram of the trigger interface for the message merging instruction provided in this application embodiment. See also: Figure 7 The message merging function 72 is displayed in the conversation interface 71. When the target object triggers the message merging function 72 (e.g., by clicking the message merging function 72), the conversation messages in the conversation interface are in a candidate state, as shown in the conversation interface 73. When the target object selects "Let's go camping" and "The weather is so nice!" based on the conversation interface 73 and clicks the OK control 75, as shown in the conversation interface 74, the message merging instruction is triggered.
[0149] Here, we will explain the message merging process after the message merging command is triggered based on the message merging function item.
[0150] In some embodiments, the terminal may display a third session message obtained by merging a first session message and a second session message in the following manner: when the sending time of the first session message is earlier than the sending time of the second session message, the terminal displays the process of the first session message automatically moving to the end of the second session and merging with the second session message to obtain the third session message; or, when the sending time of the first session message is earlier than the sending time of the second session message, the terminal displays the process of the first session message automatically moving to the end of the second session and displays the third session message obtained by merging the first session message and the second session message. That is, after the first session message automatically moves to the end of the second session, the terminal may display the process of merging the first session message and the second session message, or it may only display the merged state, that is, only display the merged result.
[0151] In other embodiments, the terminal may also display a third session message obtained by merging the first session message and the second session message in the following manner: when the first session message and the second session message are not the session messages sent at the latest time in the session interface, the terminal displays the process of merging the first session message into a third session message by automatically moving the first session message to the position of the second session message or automatically moving the second session message to the position of the first session message, and the third session message is moved below the session message sent at the latest time.
[0152] Here, when the first session message and the second session message are not the session messages sent latest in the session interface, the terminal can also display the process of automatically moving the first session message to the second session message or automatically moving the second session message to the first session message, and display the third session message obtained by merging the first session message and the second session message, with the third session message located below the session message sent latest.
[0153] In some embodiments, after the terminal displays the third session message obtained by merging the first session message and the second session message, the position of the merged third session message in the session interface can be adjusted, that is, the order of the third session message in the session interface can be adjusted. In response to the order adjustment instruction for the third session message, the terminal moves the position of the third session message in the session interface to change the message order of the third session message in the session interface.
[0154] In practical applications, the target object can adjust the order of third-session messages by dragging them. Specifically, in response to the drag operation of the third-session message, when the operation duration of the drag operation reaches the duration threshold, the terminal triggers the order adjustment instruction for the third-session message. Along with the execution of the drag operation, the third-session message is controlled to move synchronously in the session interface to change the message order of the third-session message in the session interface.
[0155] For example, Figure 8A This is a schematic diagram of the interface for sorting and adjusting merged session messages provided in an embodiment of this application. See also: Figure 8AIn Figure (1), the message dragged by the target object is the third conversation message obtained by merging "The weather is so nice!" and "Let's go camping". When the drag duration of the target object on this message reaches the duration threshold, the message is triggered to move in the conversation interface. When the target object drags the third conversation message below the conversation message "Haha, great! I just want to go out and relax this weekend" and releases the drag operation, as shown in Figure (2), the sorting of the third conversation message is adjusted. As shown in Figure (3), after the drag operation is released, the third conversation message is sorted after "Haha, great! I just want to go out and relax this weekend" in the conversation interface.
[0156] In practical applications, the target object can also adjust the sorting of the third session messages using the sorting controls in the session interface. Specifically, after the terminal displays the third session message obtained by merging the first and second session messages, it controls the third session message to be in a sorting pending state and displays sorting controls in the session interface. These sorting controls include an upward adjustment control and a downward adjustment control. The target object can trigger (e.g., click) the upward adjustment control to move the third session message in the session interface from bottom to top, such as moving it up one position with each click. Similarly, the target object can trigger (e.g., click) the downward adjustment control to move the third session message in the session interface from top to bottom, such as moving it down one position with each click.
[0157] For example, Figure 8B This is a schematic diagram of the interface for sorting and adjusting merged session messages provided in an embodiment of this application. See also: Figure 8B In Figure (1), after merging "The weather is nice!" and "Let's go camping", the third conversation message 81 is in a state of sorting pending adjustment. The terminal displays a sorting control 82 in the conversation interface. The sorting control includes an upward adjustment control and a downward adjustment control, as shown in Figure (1). When the target object clicks the downward adjustment control, the third conversation message 81 is triggered to move down one position, that is, to the bottom of the conversation message adjacent to the third conversation message in the conversation interface, and a confirmation control 83 is displayed. When the target object clicks the confirmation control 83 to trigger the confirmation command, the sorting of the third conversation message is adjusted, as shown in Figure (3).
[0158] In some embodiments, when the target object adjusts the sorting of merged session messages (such as a third session message), the adjustment can only be made within the target area of the session interface. Specifically, the terminal displays the target area while moving the position of the third session message; when the third session message moves to the edge of the target area, a movement prompt message is displayed, which indicates that the sorting of the third session message can only be adjusted within the target area.
[0159] In some embodiments, since the third session message is obtained by merging the first session message with the second session message, the sending time of the merged third session message is the same as the sending time of the second session message. When the target object sorts and adjusts the merged session message (such as the third session message), the adjusted position can only be within a certain period of time (such as 1 minute). For example, if the sending time of the third session message is 11:15, then the position movement range of the third session message is between 11:14 and 11:16. Specifically, during the process of moving the position of the third session message, when the third session message moves to the target position, the target position makes the third session message adjacent to the target historical session message, and the sending time interval between the third session message and the target historical session message reaches the time interval threshold, an interception line is displayed between the third session message and the target historical session message. This interception line is used to intercept the third session message when it moves to the interception line.
[0160] For example, Figure 8C This is a schematic diagram of the interface for sorting and adjusting merged session messages provided in an embodiment of this application. See also: Figure 8C Session message 84 is the third session message obtained after message merging. When the user drags session message 84 to adjust its sorting in the session interface, when session message 84 moves to be adjacent to session message 85 (i.e. target historical session message), and the time interval between the sending of session message 84 and session message 85 reaches the time interval threshold, an interception line 86 is displayed between session message 84 and session message 85, as shown in Figure (2). When the user continues to drag session message 84 downward, session message 84 is intercepted, so that the user cannot move session message 84 below session message 85. When the user releases the drag operation at the position shown in Figure (2), session message 84 is controlled to be displayed at the release position corresponding to the drag operation, as shown in Figure (3).
[0161] In practical applications, after merging the first and second session messages to obtain the third session message, the target object can also adjust the order of the content of the first session message and the corresponding content of the second session message in the merged message. Specifically, the content corresponding to the first session message is the first content, and the content corresponding to the second session message is the second content. In the session interface, after displaying the third session message obtained by merging the first and second session messages, the terminal responds to the instruction to adjust the position of the content in the third session message, and adjusts the position of at least one of the first and second content in the third session message to change the order of the first and second content in the third session message. For example, after the terminal displays the third session message obtained by merging the first and second session messages, the first and second contents in the third session message are kept in a pending sorting state. If the user does not need to adjust the sorting of the first and second contents, a confirmation command is triggered, such as clicking on a blank area in the session interface. If the user needs to adjust the sorting of the first and second contents, the corresponding position adjustment command can be triggered by dragging the first or second contents. For example, when the first content "The weather is so nice!" is sorted first and the second content "Let's go camping" is sorted later, the position of the first content can be dragged to the position after the position of the second content.
[0162] The types of merged session messages are described below. In some embodiments, the types of the first and second session messages to be merged as specified by the target object can be at least one of the following: text message, voice message, image message, video message, emoticon message, and rich media message. Figures 9A to 9F This application provides an example of an interface diagram illustrating the merging of different types of session messages. (See attached diagram.) Figure 9A Users can merge image and text messages by dragging the image message to the text message area; see also Figure 9B Users can merge video and text messages by dragging the video message to the text message area; see also Figure 9C Users can merge voice and text messages by dragging the voice message to the text message area; see also Figure 9D Users can merge image and voice messages by dragging the image message to the voice message area; see also Figure 9E Users can merge image and video messages by dragging them to the video message area. In practice, users can merge multiple conversation messages by dragging them multiple times; see [link to relevant documentation]. Figure 9FUsers first merge voice messages and text messages by dragging them to the text message area to obtain a merged message. Then, by dragging image messages to the merged message area, image messages are merged with the merged message. In this way, voice messages, text messages, and image messages can be merged. Of course, in practical applications, users can trigger the message merging command multiple times to merge conversation messages of two or more message types.
[0163] In practical applications, users can merge not only their own sent session messages, but also session messages sent by themselves and other session objects, or only session messages sent by other session objects. In some embodiments, when the sender of the first session message is the target object and the sender of the second session message is the session object of the target object, the terminal can display the third session message obtained by merging the first session message and the second session message in the following ways: the terminal displays a copy of the second session message; in the session interface, the third session message obtained by merging the copy of the first session message and the copy of the second session message is displayed, or the process of merging the copy of the first session message and the copy of the second session message to obtain the third session message is displayed.
[0164] Here, when a user triggers a message merging command by dragging a session message, if the session message dragged by the user is a session message sent by the user himself, the movement of the session message itself is triggered. If the session message dragged by the user is a session message sent by the user's session object, the movement of a copy of the session message is triggered. Of course, in some embodiments, if the session message dragged by the user is a session message sent by the user's session object, the movement and merging of the session message itself may also be triggered.
[0165] The triggering of the message merging instruction is explained when the recipient of the first session message is the target object and the recipient of the second session message is the session object of the target object. In some embodiments, the message merging instruction can be triggered in the following manner: the terminal responds to a press operation on the first session message and controls the first session message to be in a selected state; during the execution of the press operation, in response to a drag operation on the second session message, a copy of the second session message is displayed, and the process of dragging the copy of the second session message is displayed in the session interface; when the second session message is dragged to the location of the first session message, in response to the release of the drag operation, the message merging instruction is triggered.
[0166] For example, Figure 10A This is a schematic diagram of the interface for merging session messages from different session objects provided in an embodiment of this application. See also: Figure 10AWhen a user presses a conversation message "Location A" sent by themselves with one finger, the terminal determines that this conversation message is one to be merged and keeps it in a selected state. While the user is pressing "Location A," they drag another conversation message "Location B Day Trip" sent by someone else with another finger. In response to the dragging operation on "Location B Day Trip," the terminal generates and displays a copy of the "Location B Day Trip" message, showing the dragging process in the conversation interface. When the copy of "Location B Day Trip" is dragged to the location of "Location A," the dragging operation is released, triggering a message merging command. The process of displaying "Location B Day Trip" and "Location A" in the conversation interface is then observed.
[0167] In practical applications, when a user performs a press operation on the first conversation message, they can repeatedly drag conversation messages sent by others to merge multiple conversation messages sent by themselves with their own. That is, after the terminal displays the third conversation message resulting from the merging of the first and second conversation messages, during the target user's press operation on the first conversation message, in response to a drag operation on the fourth conversation message, the process of dragging the fourth conversation message is displayed in the conversation interface. When the fourth conversation message is dragged to the position of the third conversation message, in response to the release of the drag operation, the fifth conversation message resulting from the merging of the fourth and third conversation messages is displayed, or the process of merging the fourth and third conversation messages to obtain the fifth conversation message is displayed. For example... Figure 10B As shown, Figure 10B This is a schematic diagram of an interface for merging session messages from different session objects, provided in an embodiment of this application. The diagram continues... Figure 10A Among them, the user-pressed session message "Location A, Location B day trip" is the execution... Figure 10A The third session message obtained during the operation, and other session messages obtained when the user drags the button while continuing to perform the press operation, such as... Figure 10B The “Location C” shown (i.e., the fourth session message) will be displayed when a copy of “Location C” is dragged to “Location A, Location B Day Trip”. This will show the process of merging the fourth session message with the third session message to obtain the fifth session message (Location A, Location B Day Trip, Location C).
[0168] Here, as the user continuously performs a pressing operation and repeatedly drags other people's conversation messages to merge them, the number of merged conversation messages can be displayed in the conversation interface. This makes it easy for the user to clearly know the number of merged conversation messages.
[0169] When the first session message is sent to the target object and the second session message is sent to the session object of the target object, in some embodiments, the message merging instruction can be triggered in the following manner: the terminal responds to a press operation on the first session message, and when the press operation meets the press condition, controls the session message in the session interface to be in a candidate state; during the execution of the press operation, in response to a trigger operation on the second session message in the candidate state, the message merging instruction is triggered; accordingly, after the message merging instruction is triggered, the third session message obtained by merging the first session message and the second session message is displayed in the following manner: the process of automatically moving a copy of the second session message to the first session message is displayed, and the third session message obtained by merging the copy of the second session message and the first session message is displayed; or, the process of automatically moving a copy of the second session message to the first session message and merging it with the first session message to obtain the third session message is displayed. During the user's press operation, multiple conversation messages can be merged by clicking on other people's messages multiple times. Specifically, during the press operation, in response to the trigger operation for the sixth conversation message, the terminal displays a copy of the sixth conversation message that is automatically moved to the third conversation message and merged with the third conversation message to obtain the seventh conversation message.
[0170] Here, in some embodiments, the pressing condition is determined to be satisfied when at least one of the following conditions is met: the pressing duration of the pressing operation reaches a duration threshold, and the pressing pressure reaches a pressure magnitude threshold.
[0171] For example, Figure 10C This is a schematic diagram of the interface for merging session messages from different session objects provided in an embodiment of this application. See also: Figure 10CWhen a user presses the conversation message "Location A" sent by themselves with one finger, the terminal controls other conversation messages in the conversation interface to be in a candidate state. While the user is pressing the conversation message "Location A", they use another finger to click on the conversation message "Location C" sent by someone else. The terminal responds to the click operation on the conversation message "Location C", triggers a message merging command, generates and displays a message copy of the conversation message "Location C", and displays the process of the message copy of "Location C" automatically moving to the conversation message "Location A" and merging with "Location A" in the conversation interface. During the continuous pressing action, the user can merge multiple messages by clicking on other users' messages. For example, after merging the conversation messages "Location C" and "Location A" to obtain "Location A, Location C", if the user clicks on "Location D" during the continuous pressing action, it triggers the merging of "Location D" with "Location A, Location C". This generates and displays a copy of the conversation message "Location D", and the copy of "Location D" automatically moves to the "Location A, Location C" conversation message and merges with it. It should be noted that the above-mentioned clicking action on other users' conversation messages can be performed multiple times during the continuous pressing action.
[0172] Here, to facilitate user operation, guidance can be provided for the merging operation. That is, guidance information can be displayed in the session interface to guide the user to trigger the message merging command. The guidance information can be in the form of text, graphics, animation, or video, and can be used to guide the target object to perform the target operation to trigger the message merging command. Figure 11 This is a schematic diagram of the interface for performing the merging operation provided in an embodiment of this application. See also: Figure 11 When a user presses a conversation message they sent, a text prompt appears in the conversation interface indicating that the pressed message can be merged with other conversation messages by clicking on them. Figure 11 The message prompts message 111, which means "Click the message to merge".
[0173] As a user continuously performs a pressing operation and clicks multiple times on other people's conversation messages to merge messages, the number of merged conversation messages can be displayed in the conversation interface. Figure 12 A schematic diagram of the interface for displaying the number of merged session messages provided in this application embodiment is shown below. Figure 12 While the user's finger 121 is continuously pressing, another finger can be used to repeatedly click on messages to merge multiple conversation messages, and the number of merged conversation messages 122 is displayed in the conversation interface.
[0174] In some embodiments, if a user wants to merge messages from another person in a session, they need to obtain authorization from that person. Specifically, when at least one of the senders of the first session message and the second session message is the session object of the target object, before displaying the third session message obtained by merging the first and second session messages in the session interface, the terminal displays an authorization prompt and a corresponding confirmation function item. The authorization prompt is used to prompt for authorization to perform the merging operation on the session messages of the session object. In response to the triggering operation of the confirmation function item, the terminal sends an authorization request to the session object. This authorization request is used to request authorization to perform the merging operation on the session messages of the session object. When authorization to perform the merging operation on the session messages of the session object is obtained, the terminal displays the third session message obtained by merging the first and second session messages in the session interface.
[0175] In practical applications, after the terminal displays the third session message obtained by merging the first and second session messages, it can provide users with functions for further processing of the third session message. In some embodiments, the terminal displays at least one message processing function corresponding to the third session message; in response to a trigger operation on a target message processing function among the at least one message processing function, the terminal performs the target processing operation indicated by the target message processing function on the third session message. The message processing function displayed by the terminal may include at least one of the following functions: a sending function for sending messages, a forwarding function for forwarding messages, a copying function for copying messages, a file generation function for generating a target format file (such as a text format file, .txt file), a meeting minutes function for generating meeting minutes, and a voting function for voting on the content of the message, etc. The specific functions of the message processing function can be set according to actual needs.
[0176] Here, when the third session message includes at least two sub-contents and the target message processing function is a voting function, performing the target processing operation indicated by the target message processing function on the third session message may include: displaying the voting message corresponding to the third session message, which includes: options corresponding to each sub-content and voting operation controls; wherein, the voting operation controls are used to vote on the sub-content selected based on the options. In practical applications, the terminal may display the voting message corresponding to the third session message in the following ways: displaying the voting message corresponding to the third session message in the session interface; or, displaying a display overlay and displaying the voting message corresponding to the third session message in the display overlay; or, displaying a voting information interface and displaying the voting message corresponding to the third session message in the voting information interface.
[0177] For example, Figure 13A and Figure 13BThis is a schematic diagram of the interface for message processing based on the message processing function item provided in an embodiment of this application. See also: Figure 13A After the terminal displays the third session message obtained by merging the first and second session messages, it displays the merged message processing interface 131, which shows the merged third session message 132 and the corresponding message processing function item 133. When the user triggers the "send" function item, the third session message 132 is sent to the session interface as a new session message; see continue. Figure 13B When a user triggers the "vote" function, the terminal displays the voting message 134 corresponding to the third session message in the session interface. The voting message includes: options 135 corresponding to each sub-content and voting operation control 136. When the user selects the voting content based on the options 135 corresponding to each sub-content, such as clicking the options corresponding to "Location A" and "Location B Day Trip", and clicking the voting operation control 136, the user can vote for "Location A" and "Location B Day Trip".
[0178] In some embodiments, after the terminal displays the voting message corresponding to the third session message, the voting results of the corresponding sub-content are displayed in the associated area of each sub-content in the voting message. The voting results are used to indicate the number of session objects that voted for the corresponding sub-content. Figure 14 This is a schematic diagram of the interface for displaying voting results provided in an embodiment of this application. See also: Figure 14 In voting message 134, the associated area of each sub-content displays the voting results 137 for the corresponding sub-content. For example, the number of session objects voting for location A is 1, while the number of day trips to location B is the most, at 5.
[0179] In practical applications, users have limited voting time. Specifically, after the terminal displays the voting message corresponding to the third session message, the terminal obtains the display duration of the voting message. When the display duration of the voting message reaches the display duration threshold (which can be set according to actual needs, such as 10 minutes), the display of the voting operation controls is canceled, and an end indication message indicating that the voting has ended is displayed in the voting message.
[0180] In some embodiments, when the target message processing function is a forwarding function, after the user triggers the forwarding function, the terminal displays at least one selectable forwarding object, which has a social connection with the target object (e.g., the target object and the forwarding object are friends on the client); in response to a selection instruction for the target forwarding object among the at least one forwarding object, a third session message is sent to the target forwarding object. In practical applications, the terminal can display at least one selectable forwarding object in the following ways: the terminal displays a forwarding object selection interface; at least one selectable forwarding object is displayed in the forwarding object selection interface; or, a display overlay is displayed, and at least one selectable forwarding object is displayed in the display overlay.
[0181] In some embodiments, when the target message processing function is a meeting minutes function, in response to a trigger operation for the meeting minutes function, a meeting minutes corresponding to the third session message is generated; in response to a storage instruction for the meeting minutes, the meeting minutes are stored.
[0182] In practical applications, meeting minutes include a title, a time period, and the main body. In some embodiments, when a third session message includes at least two sub-contents, the terminal can generate meeting minutes corresponding to the third session message in the following manner: perform semantic analysis on the content of the third session message and generate a title for the meeting minutes based on the analysis results; obtain the sending time corresponding to each sub-content and determine the time period for the meeting minutes based on the obtained sending time; and generate a meeting minutes including a title, time period, and main body by using the content of the third session message as the main body of the meeting minutes.
[0183] In some other embodiments, the title of the meeting minutes can be obtained by predicting it using a pre-trained neural network model. Specifically, the third session message is input into the neural network model, which outputs the title of the meeting minutes.
[0184] Applying the above embodiments of this application, the target object triggers a message merging instruction. Since the message merging instruction instructs the merging of the first session message and the second session message, that is, the target object specifies that the first session message and the second session message be merged, the electronic device can respond to the message merging instruction and realize the merging of the first session message and the second session message specified by the target object in the session interface. By merging interrupted messages, the missed reading of sent messages can be avoided. When the user needs to summarize the messages of multiple session objects in a group chat, the message merging can be used to merge the messages of different session objects, so that the messages of different session objects are presented through a single message, which improves the efficiency of message transmission. At the same time, compared with the related technology that only displays messages in the session interface based on the message sending time, the utilization rate of the electronic device's hardware processing resources and display resources is improved.
[0185] Figure 15 This is a flowchart illustrating the session message processing method provided in this application. In some embodiments, the session message processing method provided in this application can be implemented by the terminal alone, by the server alone, or by the terminal and the server working together. Here, we will describe the implementation by the terminal as an example. See [link to documentation]. Figure 15 The session message processing method provided in this application includes:
[0186] Step 201: The terminal displays at least two session messages in the group session interface of the first object.
[0187] Here, the group conversation interface displays at least two conversation messages, including at least: a first conversation message and a second conversation message sent by the first object, a third conversation message sent by the second object, and a fourth conversation message sent by the third object.
[0188] Step 202: In response to a drag operation on the first session message, display the process of the first session message being dragged.
[0189] In practice, the dragging process of the first session message is only displayed when the dragging operation on the first session message reaches the target duration.
[0190] Step 203: When the first session message is dragged to the second session message and the drag operation is released, the process of merging the first session message and the second session message to obtain the fifth session message is displayed.
[0191] Step 204: In response to a press operation on the fifth session message, control the third and fourth session messages in the group session interface to be in the candidate state.
[0192] Step 205: During the execution of the press operation, in response to the click operation on the third session message which is in the candidate state, the copy of the third session message is automatically moved to the fifth session message and merged with the fifth session message to obtain the sixth session message.
[0193] Step 206: During the execution of the press operation, in response to the click operation on the fourth session message which is in the candidate state, the process of automatically moving a copy of the fourth session message to the sixth session message and merging it with the sixth session message to obtain the seventh session message is displayed.
[0194] Step 207: In response to the press being released, the voting function item is displayed.
[0195] Here, the voting function is used to vote on the various sub-contents contained in the seventh session message (i.e., the content corresponding to the first session message, the content corresponding to the second session message, the content corresponding to the third session message, and the content corresponding to the fourth session message).
[0196] Step 208: In response to the trigger operation for the voting function item, display the voting message corresponding to the seventh session message. The voting message includes the options for each sub-content and the voting operation controls.
[0197] Step 209: In response to the voting instruction triggered by the voting operation control for the selected sub-content, display the voting results of the corresponding sub-content in the associated area of each sub-content in the voting message.
[0198] By applying the above embodiments of this application, users can merge messages sent by themselves by dragging and dropping conversation messages. Furthermore, they can merge their own conversation messages with those sent by multiple group members in a group conversation by pressing one conversation message and clicking on other conversation messages. In this way, merging one's own messages avoids missing messages due to interruption, improving message delivery efficiency. By merging conversation messages from oneself and others, messages from different conversation objects can be summarized. Furthermore, a voting function is provided for the summarized messages, allowing users to vote on each sub-content in the merged messages, and the voting results are displayed accordingly, improving the processing efficiency of the target object for multiple conversation messages. At the same time, compared with related technologies that only display messages in the conversation interface based on the message sending time, the utilization rate of electronic device hardware processing resources and display resources is improved.
[0199] The following describes an exemplary application of the embodiments of this application in a real-world application scenario. This embodiment is illustrated using a server and terminal working together, with an instant messaging client installed on the terminal. In some embodiments, a user can trigger a message merging command by dragging a message from one session to another, thereby merging two messages into one. Based on this, the message processing on both the client and server sides during message merging will be explained.
[0200] In the session message processing system, each session message has the concepts of seq (sequential or ordered) and timestamp. When a user sends a session message from the client, it goes through the backend server. The message is the seqth message in the current session. When sending the message, the seq is returned to the client, and the data is assembled along with the seq and sent to the receiver. This serves as a unique identifier for the message, allowing the client to locate the message. The timestamp represents the timestamp of the message, which is also based on the backend server's timestamp and is independent of the client. Like the seq, it is also returned to the sender when sending the message, and is included in the data assembly before being sent to the receiver.
[0201] Figure 16 This is a schematic diagram of the session message sending process provided in an embodiment of this application. See also... Figure 16 On the message sending end, after the user edits a good message, they can send the message by clicking the send button. The message sending end sends a message signaling to the message backend (i.e., the server). The server obtains the timestamp and sorting of the message based on the message signaling, processes the message, and distributes it to each terminal in the session. The server then returns the sending result to the message sending end so that the message sending end can update the message status and send the message to the receiving end so that the receiving end can display the message.
[0202] Here, the assembly of messages is explained. The client sorts the list according to the timestamp and assembles the messages according to the sequence number (seq) to obtain specific session messages. Figure 17 This is a schematic diagram of the message composition provided in an embodiment of this application. See also: Figure 17 Each message has a seq and timestamp field, the contents of which are represented by an array to display messages, merged messages, mixed rich text messages, etc., and can contain text, images, videos, etc.; among them, text, images, and videos are represented as independent message content items.
[0203] In practical applications, clients modify, delete, and perform other editing operations on messages by sending protocol request packets to the server. Figure 18 This is a schematic diagram illustrating the composition of the protocol request packet provided in an embodiment of this application. See also... Figure 18 The protocol request packet includes a request packet header and an array of message edit packets. The message edit packet array can include at least two message edit packets, each containing the edit type (e.g., update or delete) and basic message information (e.g., sorting, timestamp, message content). Correspondingly, the server returns a response packet to the message edit signaling protocol request packet sent by the client. Figure 19 This is a schematic diagram illustrating the composition of the response packet provided in an embodiment of this application. See also... Figure 19The response packet includes a response header and basic result information, which may include the request error code and a description of the request result. The detailed protocol definitions for the request and response packets are as follows:
[0204]
[0205]
[0206] In practical applications, when a user triggers a message merging command to instruct the merging of session messages, the message merging may involve the following two changes:
[0207] 1. Delete the merged message; 2. Modify the content of the merged message.
[0208] The message editing protocol request body contains two editing messages: deletion and modification. Deleting the merged message body will also update the modified message body. The deleted message body will be added to the merged message body to achieve the purpose of updating the message. Figure 20 This is a schematic diagram of the preprocessing flow for message merging provided in an embodiment of this application. This preprocessing is performed by the client. See [link / reference]. Figure 20 The message preprocessing flow for merging is as follows:
[0209] Step 1: The client drags the message.
[0210] Here, the client responds to the user's drag operation on the session message. When the drag condition is met (such as the drag duration reaching a duration threshold), the drag of the session message is triggered.
[0211] Step 2: Determine if the time limit has been exceeded.
[0212] Here, in some embodiments, users can only merge messages within a certain time range (e.g., 1 minute). The client determines whether the sending duration of the dragged message and the message to be merged by the user (i.e., the message reached by the dragged message when the user releases the drag operation) is within the set time range. If it is not within the time range, step 3 is executed, that is, there is no effect and the dragged message is reset; if it is within the time range, step 4 is executed.
[0213] Step 3, if there is no effect.
[0214] Step 4: Extract the content of the dragged message.
[0215] Step 5: Merge message content.
[0216] Step 6: Assemble the message and delete the data.
[0217] Here, the client reassembles the messages based on the merged message content and deletes the original data of the dragged messages.
[0218] Step 7: Assemble the message update data.
[0219] Here, data is updated based on the reassembled messages.
[0220] Step 8: Request message editing signaling.
[0221] Here, the client generates a request message editing signaling based on the updated data and sends it to the server.
[0222] In practice, after the client generates a request message editing signaling, it pushes the message editing information to the message receiver through the server's bridge, so that the message receiver client can update its local message according to the corresponding editing information. Figure 21 This is a schematic diagram of the interaction process between the client and the server provided in an embodiment of this application. See also... Figure 21 The interaction logic between the client sending end, the backend server, and the client receiving end is as follows:
[0223] Step 1: The client performs message editing preprocessing.
[0224] Here, the client's message editing preprocessing is specifically as follows: Figure 20 As shown, after the client performs message editing preprocessing, it sends a message editing signal to the message backend (i.e., the server).
[0225] Step 2: The message backend checks the legality of the message editing signaling.
[0226] Here, the legality check can be whether the message editing signaling format is correct, whether there is illegal content, and whether the user has the corresponding operation permissions. When the message backend detects that it is illegal, step 3 is triggered, and when the message signaling is detected to be legal, step 4 is triggered.
[0227] Step 3: Return the editing failure result to the message sender.
[0228] Here, when the message sender receives an editing failure result from the message backend, it handles the message editing failure, such as displaying a message indicating that merging failed.
[0229] Step 4: Send message editing signaling to both the message sender and the message receiver.
[0230] Here, when the message sender receives the message editing signaling sent by the message backend, it can display the result after successful editing. When the message receiver receives the message editing signaling sent by the message backend, it can edit and process local messages, such as deleting local messages and updating local message content.
[0231] In practice, the sender and receiver on the client side process local data based on the message editing signaling data. A specific message can be found and updated / deleted based on its sequence number (seq). Within each message session, the seq is a unique identifier for the message. If it's a message update, the message content with `modify_type` set to `MODIFY_TYPE_UPDATE` in the message editing signaling will be used to replace it. If it's a deletion (where `modify_type` is `MODIFY_TYPE_UPDATE`), the message with the corresponding seq will be deleted.
[0232] In practice, after merging the first and second session messages into a third session message in the client's session interface, the client can further adjust the position of the third session message. Messages in a session use `seq` as a unique identifier and `timestamp` to identify the message's timestamp, which is used to determine the message's display order. After receiving a message, the client can insert it into a specific position based on its timestamp. The timestamp represents the number of seconds that have elapsed since January 1, 1970, and is consistently used with the timestamp returned from the server to ensure consistency. Figure 22 This is a schematic diagram of the preprocessing flow for adjusting the position of merged messages (such as third session messages) provided in an embodiment of this application. See also... Figure 22 The preprocessing logic for mobile merge messages is as follows:
[0233] Step 1, move the message.
[0234] Here, when a user triggers an operation to adjust the position of a message, such as a drag operation, a message-moving instruction is triggered. This message-moving instruction can be used to instruct the message to be moved by means of swiping, dragging, etc., so as to adjust the position of the message.
[0235] Step 2: Determine if it is a merged message type.
[0236] Here, the client determines whether the message indicating a location adjustment by the user is a merged message (such as a third session message). If it is, step 3 is executed; otherwise, step 4 is executed.
[0237] Step 3: Determine if the time limit is met.
[0238] Here, the client further determines whether the time difference of the mobile message location falls within the time period. If it does, proceed to step 5; otherwise, proceed to step 4.
[0239] Step 4, invalid processing result.
[0240] Here, the client indicates that the move for the message is invalid.
[0241] Step 5: Get the timestamp of the previous message.
[0242] Step 6: Merge message timestamps +1.
[0243] Step 7: Assemble the message update data.
[0244] Step 8: Request message editing signaling.
[0245] Here, the client generates a request message editing signaling based on the updated data and sends it to the server.
[0246] In summary, the mobile message merging process preprocesses the mobile message location, primarily determining two aspects: whether the message is a merged type, and whether the time difference between the mobile message locations falls within a specified time period. Only if these conditions are met will the message be updated via message editing signaling. This mainly involves updating the message's timestamp, adding 1 to the timestamp of the previous message at the destination location, based on the mobile message's location. This facilitates the client's sorting and display of messages to achieve the desired movement to a specific position. Once the mobile message preprocessing is complete, the client can request message editing signaling, and the backend server will send the message movement and editing information to the receiving client. The `modify_type` is of type `MODIFY_TYPE_UPDATE`.
[0247] Figure 23 This is a schematic diagram of the interaction process during message merging and movement provided in an embodiment of this application. See also... Figure 23 ,
[0248] Step 1: The client performs message editing preprocessing.
[0249] Here, the client's message editing preprocessing is specifically as follows: Figure 22 As shown, after the client performs message editing preprocessing, it sends a message editing signal to the message backend (i.e., the server).
[0250] Step 2: The message backend checks the legality of the message editing signaling.
[0251] Here, the legality check can be whether the message editing signaling format is correct, whether there is illegal content, and whether the user has the corresponding operation permissions. When the message backend detects that it is illegal, step 3 is triggered, and when the message signaling is detected to be legal, step 4 is triggered.
[0252] Step 3: Return the editing failure result to the message sender.
[0253] Here, when the message sender receives an editing failure result from the message backend, it handles the message editing failure, such as displaying a message indicating that the move failed.
[0254] Step 4: The message backend sends a message mobile editing signal to the message sender and message receiver.
[0255] Here, when the sending end receives the message move and edit signaling, it can display that the message move was successful and refresh the message list. When the receiving end receives the message move and edit signaling, it can process local messages, such as deleting the moved local messages and updating the local message content.
[0256] In practical applications, based on the aforementioned embodiments, users can not only merge their own sent conversation messages, but also merge their own messages with those of others. That is, this application is not limited to merging one's own message content; it can also merge others' messages into one's own messages without affecting others' messages. Unlike the aforementioned merging of multiple messages sent within one minute, this method simply merges others' messages into one's own; there is no deletion of others' messages. The message editing request signaling will not contain any deleted content, only updates. Figure 24 This is a schematic diagram comparing message signaling provided in an embodiment of this application. See also: Figure 24 In the signaling for merging one's own messages, there is deletion and updating of message content, while in the signaling for merging messages from others and oneself, there is only updating of message content.
[0257] Merging messages from others involves a two-handed interaction. You need to press and hold your own message while simultaneously clicking on another message with your other hand. The program will automatically merge the other message content into your own. When you release your hand, the message editor will update the message with the currently set content. Figure 25 This is a schematic diagram of the preprocessing flow for merging other people's messages provided in an embodiment of this application. See also... Figure 25 The preprocessing logic for merging other people's messages is as follows:
[0258] Step 1: The user presses and holds their own message.
[0259] Step 2: Determine if the release is complete.
[0260] Here, the client will detect in real time whether the message pressed by the user has been released. If it is detected that the message has been released, the client will assemble the message update data and generate a request message editing signaling to send to the server. If it is detected that the message has not been released, step 3 will be executed.
[0261] Step 3, click on someone else's message.
[0262] Step 4: Determine if the time limit has been exceeded.
[0263] Here, the client determines whether the sending time of the message clicked by the user exceeds the time limit based on the message timestamp. If it does, the operation has no effect; if it does not exceed the time limit, the content of the clicked message is extracted and merged.
[0264] After merging and preprocessing other people's messages, you can request a message editing signaling message. The signaling message content only contains UPDATE, which will update the current message itself. At the same time, the message data will be updated by the message recipient through the signaling message. The request signaling message is described above. Figure 20 The process and corresponding descriptions all use the same mechanism and the same signaling, with only slight differences in the assembly of signaling data. There is no DELETE situation.
[0265] Once messages are merged, the message content will contain `is_combine` to indicate whether the message is a merged message (true for merged, false for normal). During merging, a right-click menu will pop up with options for sending, forwarding, copying, and voting, providing at least four capabilities. Sending, forwarding, and copying reuse capabilities from existing instant messaging clients. For voting, the message needs to be processed and adapted to the voting interface. The message content is formatted as an array, with each element treating as a vote item. Figure 26 This is a schematic diagram of the message content structure provided in an embodiment of this application. See also: Figure 26 ,as follows:
[0266] Each message content is a MessageBody, which contains some basic information such as the message's unique identifier seq, is_combine to indicate whether message types should be merged, and the message's timestamp. The actual message content is contained in a MessageArray structure, which is an array. Each item in the array is a MessageContent structure. The MessageContent has a type to identify the type of the message content (text / image / audio / video, etc.) and contains the actual content. If it is text, it contains the actual text content. If it is image / audio / video content, it contains the fileid of the resource uploaded to the server. The fileid is the unique identifier returned when the resource is uploaded to the server, and the corresponding resource can be downloaded through this fileid.
[0267] Figure 27 This is a schematic diagram of the message merging process provided in the embodiments of this application. See also: Figure 27The post-message operation process includes: when the user clicks on the merged message (i.e., the merged type message), the client will pop up an operation selection box, which includes the send, forward, copy, and vote functions; when the user clicks send, the message is sent; when the user clicks forward, the message is forwarded; when the user clicks copy, the message is copied; when the user clicks vote, the client parses the message content, splits the message content into each vote item, and then calls the interface for the user to vote.
[0268] This application provides a method for scrambling the chronological order of multiple messages and performing further operations in chat. In related technologies, messages are ordered chronologically, which sometimes leads to situations where consecutive messages intended to be sent are interrupted by messages from other users; or in group discussions, summarizing information from multiple participants is cumbersome. In this application, users can drag and drop multiple messages from within a certain time frame to merge them. The order of the merged message can be freely adjusted. In group discussions, users can also drag and drop messages from others to merge, generating a summary that can be copied, forwarded, and voted on. This allows for more continuous message delivery and better summarization of others' chat information, increasing the efficiency of information transmission in chats.
[0269] The following description continues to illustrate the exemplary structure of the session message processing apparatus 455 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 3 As shown, the software modules in the session message processing device 455 stored in the memory 450 may include:
[0270] The first display module 4551 is used to display at least two conversation messages in the conversation interface of the target object, wherein the at least two conversation messages include a first conversation message and a second conversation message;
[0271] The receiving module 4552 is used to receive a message merging instruction triggered by the target object, wherein the message merging instruction is used to instruct the merging of the first session message and the second session message;
[0272] The second display module 4553 is used to display, in response to the message merging instruction, a third session message obtained by merging the first session message and the second session message in the session interface.
[0273] In some embodiments, the first display module is further configured to respond to the drag operation of the target object on the first session message, and when the operation duration of the drag operation reaches a duration threshold, display the process of the first session message being dragged in the session interface;
[0274] The receiving module is further configured to receive the message merging instruction in response to the release of the drag operation when the first session message is dragged to the second session message.
[0275] In some embodiments, the first display module is further configured to obtain a first time interval between the sending time of the first session message and the current time when the operation duration of the drag operation reaches a duration threshold;
[0276] When the first time interval is less than or equal to the time interval threshold, the process of dragging the first session message is displayed in the session interface.
[0277] In some embodiments, the receiving module is further configured to, in response to the release of the drag operation, obtain a second time interval between the sending time of the second session message and the current time when the first session message is dragged to the second session message;
[0278] The message merging instruction is received when the second time interval is less than or equal to the time interval threshold.
[0279] In some embodiments, the receiving module is further configured to, in response to the release of the drag operation, obtain the sending time interval between the first session message and the second session message when the first session message is dragged to the second session message;
[0280] When the sending time interval is less than or equal to the sending time interval threshold, the message merging instruction is triggered.
[0281] In some embodiments, the first display module is further configured to display a message merging function item in the session interface;
[0282] The receiving module is also configured to control the at least two session messages to be in a candidate state in response to a trigger operation for the message merging function item;
[0283] In response to the selection operation for the first session message and the second session message in the candidate state, the message merging instruction is received.
[0284] In some embodiments, the second display module is further configured to display the process of the first session message automatically moving to the second session message when the sending time of the first session message is earlier than the sending time of the second session message, and to display a third session message obtained by merging the first session message and the second session message.
[0285] In some embodiments, the apparatus further includes:
[0286] The first position adjustment module is used to move the position of the third session message in the session interface in response to the sorting adjustment instruction for the third session message, so as to change the message sorting of the third session message in the session interface.
[0287] In some embodiments, the receiving module is further configured to respond to a drag operation on the third session message, and trigger a sorting adjustment instruction on the third session message when the operation duration of the drag operation reaches a duration threshold.
[0288] The first position adjustment module is also used to control the third session message to move synchronously in the session interface along with the execution of the drag operation, so as to change the message order of the third session message in the session interface.
[0289] In some embodiments, the second display module is further configured to display a target area while moving the position of the third session message;
[0290] When the third session message moves to the edge of the target area, a movement prompt message is displayed;
[0291] The movement prompt information is used to prompt the user to adjust the order of the third session messages within the target area.
[0292] In some embodiments, the second display module is further configured to, during the process of moving the position of the third session message, determine when the third session message moves to a target position, the target position makes the third session message adjacent to a target historical session message, and the transmission time interval between the third session message and the target historical session message reaches a time interval threshold.
[0293] An intercept line is displayed between the third session message and the target historical session message. The intercept line is used to intercept the third session message when it moves to the intercept line.
[0294] In some embodiments, the third session message includes first content corresponding to the first session message and second content corresponding to the second session message; the apparatus further includes:
[0295] The second position adjustment module is used to adjust the position of at least one of the first content and the second content in the third session message in response to the position adjustment instruction for the content in the third session message, so as to change the order of the first content and the second content in the third session message.
[0296] In some embodiments, when the first session message is sent to the target object and the second session message is sent to the session object of the target object...
[0297] The second display module is further configured to display a copy of the second session message;
[0298] The session interface displays a third session message obtained by merging the message copies of the first session message and the second session message.
[0299] In some embodiments, when at least one of the first session message and the second session message is sent to the session object of the target object...
[0300] The first display module is also used to display authorization prompts and corresponding confirmation function items;
[0301] The authorization prompt information is used to prompt for authorization to perform a merging operation on the session messages of the session object;
[0302] In response to a trigger operation for the determined function item, an authorization request is sent to the session object, the authorization request being used to request authorization to perform a merging operation of session messages for the session object;
[0303] The second display module is further configured to, when authorized to perform a merging operation on the session messages of the session object, display a third session message obtained by merging the first session message and the second session message in the session interface.
[0304] In some embodiments, when the first session message is sent to the target object and the second session message is sent to the session object of the target object...
[0305] The second display module is further configured to control the first session message to be in a selected state in response to a press operation on the first session message;
[0306] During the execution of the press operation, in response to the drag operation of the second session message, a copy of the second session message is displayed, and the process of dragging the copy of the second session message is displayed in the session interface;
[0307] The receiving module is further configured to receive the message merging instruction in response to the release of the drag operation when the second session message is dragged to the first session message.
[0308] In some embodiments, the second display module is further configured to, during the execution of the pressing operation, in response to a drag operation on the fourth session message, display in the session interface the process of the fourth session message being dragged;
[0309] When the fourth session message is dragged to the position of the third session message, in response to the release of the drag operation, the fifth session message, which is a combination of the fourth session message and the third session message, is displayed.
[0310] In some embodiments, the second display module is further configured to display the number of merged session messages during the execution of the pressing operation.
[0311] In some embodiments, the first display module is further configured to display merge guidance information in the session interface of the target object;
[0312] The merge guidance information is used to guide the target object to perform the target operation in order to trigger the message merge instruction.
[0313] In some embodiments, the apparatus further includes a message processing module;
[0314] The second display module is further configured to display at least one message processing function item corresponding to the third session message after displaying the third session message obtained by merging the first session message and the second session message;
[0315] The message processing module is configured to, in response to a trigger operation on a target message processing function item among the at least one message processing function items, perform the target processing operation indicated by the target message processing function item on the third session message.
[0316] In some embodiments, the third session message includes at least two sub-contents;
[0317] The message processing module is further configured to, when the target message processing function item is a voting function item, display the voting message corresponding to the third session message in the session interface, wherein the voting message includes: options corresponding to each of the sub-contents and voting operation controls;
[0318] The voting control is used to vote on the sub-content selected based on the options.
[0319] In some embodiments, the message processing module is further configured to display the voting results of the corresponding sub-content in the associated area of each sub-content in the voting message; wherein the voting results are used to indicate the number of session objects that voted for the corresponding sub-content.
[0320] In some embodiments, the message processing module is further configured to, after displaying the voting message corresponding to the third session message, cancel the display of the voting operation control when the display duration of the voting message reaches a display duration threshold, and
[0321] The voting message displays an end indication message to indicate that the voting has ended.
[0322] In some embodiments, the message processing module is further configured to display a forwarding object selection interface when the target message processing function item is a forwarding function item;
[0323] The forwarding object selection interface displays at least one forwarding object for selection, and the forwarding object has a social relationship with the target object;
[0324] In response to a selection instruction for a target forwarding object among the at least one forwarding objects, the third session message is sent to the target forwarding object.
[0325] In some embodiments, the message processing module is further configured to generate meeting minutes corresponding to the third session message in response to a triggering operation for the meeting minutes function when the target message processing function is a meeting minutes function.
[0326] In response to a storage instruction for the meeting minutes, the meeting minutes are stored.
[0327] In some embodiments, the third session message includes at least two sub-contents;
[0328] The message processing module is also used to perform semantic analysis on the content of the third session message and generate the title of the meeting minutes based on the analysis results;
[0329] Obtain the sending time corresponding to each of the sub-contents, and determine the summary time of the meeting minutes based on the obtained sending time;
[0330] Using the content of the third session message as the body of the meeting minutes, a meeting minutes including the title, the minutes time, and the body is generated.
[0331] In some embodiments, the second display module is further configured to, after displaying a third session message obtained by merging the first session message and the second session message in the session interface, in response to a message merging instruction for the third session message and the sixth session message, display a seventh session message obtained by merging the third session message and the sixth session message in the session interface.
[0332] This application embodiment also provides an electronic device, the electronic device comprising:
[0333] Memory, used to store executable instructions;
[0334] The processor, when executing executable instructions stored in the memory, implements the session message processing method provided in the embodiments of this application.
[0335] This application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the session message processing method provided in this application.
[0336] This application also provides a computer-readable storage medium storing executable instructions, which, when executed by a processor, implement the session message processing method provided in this application.
[0337] This application also provides a computer program product, including a computer program or instructions, characterized in that, when the computer program or instructions are executed by a processor, they implement the session message processing method provided in this application.
[0338] In some embodiments, the computer-readable storage medium may be a read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic surface memory, optical disk, or CD-ROM, etc.; or it may be a device that includes one or any combination of the above-mentioned memories.
[0339] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
[0340] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).
[0341] As an example, executable instructions can be deployed to execute on a single computing device, or on multiple computing devices located in one location, or on multiple computing devices distributed across multiple locations and interconnected via a communication network.
[0342] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.
Claims
1. A method for processing session messages, characterized in that, The method includes: In the target object's session interface, at least two session messages are displayed, including a first session message and a second session message; Receive a message merging instruction triggered by the target object, the message merging instruction being used to instruct the merging of the first session message and the second session message; In response to the message merging instruction, if the merging conditions are met based on a first time interval, a third session message obtained by merging the first session message and the second session message is displayed in the session interface. Wherein, the first time interval is the time interval between the sending time of the first session message and the current time of the drag operation, and the drag operation satisfies the message movement condition.
2. The method as described in claim 1, characterized in that, The step of receiving the message merging instruction triggered by the target object includes: In response to the drag operation of the target object on the first session message, when the drag operation meets the message movement conditions, the process of the first session message being dragged is displayed in the session interface; When the first session message is dragged to the second session message, the message merging instruction is received in response to the release of the drag operation.
3. The method as described in claim 2, characterized in that, The process of displaying the dragged first session message in the session interface when the drag operation meets the message movement conditions includes: When the drag operation meets the message movement condition, obtain the first time interval between the sending time of the first session message and the current time; When the first time interval is less than or equal to the time interval threshold, the process of dragging the first session message is displayed in the session interface.
4. The method as described in claim 2, characterized in that, When the first session message is dragged to the second session message, in response to the release of the drag operation, the message merging instruction is received, including: When the first session message is dragged to the second session message, in response to the release of the drag operation, the sending time interval between the first session message and the second session message is obtained; The message merging instruction is received when the sending time interval is less than or equal to the sending time interval threshold.
5. The method as described in claim 1, characterized in that, The method further includes: The message merging function is displayed in the session interface; In response to a trigger operation on the message merging function item, control the at least two session messages to be in a candidate state; The message merging instruction is triggered in response to the selection operation of the first session message and the second session message in the candidate state.
6. The method as described in claim 5, characterized in that, The display of the third session message obtained by merging the first session message and the second session message includes: When the sending time of the first session message is earlier than the sending time of the second session message, the process of the first session message automatically moving to the position of the second session message is displayed, and the third session message obtained by merging the first session message and the second session message is displayed.
7. The method as described in claim 1, characterized in that, After displaying the third session message obtained by merging the first session message and the second session message, the method further includes: In response to the sorting adjustment instruction for the third session message, the position of the third session message in the session interface is moved to change the message sorting of the third session message in the session interface.
8. The method as described in claim 7, characterized in that, The method further includes: In response to a drag operation on the third session message, when the duration of the drag operation reaches a duration threshold, a sorting adjustment instruction for the third session message is triggered. Moving the position of the third session message in the session interface to change the message order of the third session message in the session interface includes: As the drag operation is executed, the third session message is controlled to move synchronously in the session interface to change the message order of the third session message in the session interface.
9. The method as described in claim 7, characterized in that, The method further includes: The target area is displayed while the position of the third session message is being moved; When the third session message moves to the edge of the target area, a movement prompt message is displayed; The movement prompt information is used to prompt the user to adjust the order of the third session messages within the target area.
10. The method as described in claim 7, characterized in that, The method further includes: During the relocation of the third session message, when the third session message moves to the target location, the target location makes the third session message adjacent to the target historical session message, and the transmission time interval between the third session message and the target historical session message reaches a time interval threshold, An intercept line is displayed between the third session message and the target historical session message. The intercept line is used to intercept the third session message when it moves to the intercept line.
11. The method as described in claim 1, characterized in that, The third session message includes the first content corresponding to the first session message and the second content corresponding to the second session message; After displaying the third session message obtained by merging the first session message and the second session message in the session interface, the method further includes: In response to a position adjustment instruction for the content in the third session message, the position of at least one of the first content and the second content in the third session message is adjusted to change the order of the first content and the second content in the third session message.
12. The method as described in claim 1, characterized in that, When the first session message is sent to the target object and the second session message is sent to the session object of the target object, displaying the third session message obtained by merging the first session message and the second session message in the session interface includes: Displays a copy of the message from the second session; The session interface displays a third session message obtained by merging the message copies of the first session message and the second session message.
13. The method as described in claim 1, characterized in that, When the sender of at least one of the first session message and the second session message is the session object of the target object, before displaying the third session message obtained by merging the first session message and the second session message in the session interface, the method further includes: Display authorization prompts and corresponding confirmation options; The authorization prompt information is used to prompt for authorization to perform a merging operation on the session messages of the session object; In response to a trigger operation for the determined function item, an authorization request is sent to the session object, the authorization request being used to request authorization to perform a merging operation of session messages for the session object; The step of displaying a third session message, obtained by merging the first session message and the second session message, in the session interface includes: When authorization is granted to perform a merge operation on the session messages of the session object, a third session message, obtained by merging the first session message and the second session message, is displayed in the session interface.
14. The method as described in claim 1, characterized in that, When the first session message is sent to the target object and the second session message is sent to the session object of the target object, the method further includes: In response to a press operation on the first session message, the first session message is controlled to be in a selected state; During the execution of the press operation, in response to the drag operation of the second session message, a copy of the second session message is displayed, and the process of dragging the copy of the second session message is displayed in the session interface; When the second session message is dragged to the first session message, the message merging instruction is triggered in response to the release of the drag operation.
15. The method as described in claim 14, characterized in that, After displaying the third session message obtained by merging the first session message and the second session message, the method further includes: During the execution of the press operation, in response to the drag operation for the fourth session message, the process of the fourth session message being dragged is displayed in the session interface; When the fourth session message is dragged to the position of the third session message, in response to the release of the drag operation, the fifth session message, which is a combination of the fourth session message and the third session message, is displayed.
16. The method as described in claim 1, characterized in that, When the first session message is sent to the target object and the second session message is sent to the session object of the target object, receiving the message merging instruction triggered by the target object includes: In response to a press operation on the first session message, when the press operation meets the press condition, the session message in the session interface is controlled to be in a candidate state. During the execution of the press operation, in response to a trigger operation for the second session message in the candidate state, the message merging instruction is received.
17. The method as described in claim 16, characterized in that, After displaying the third session message obtained by merging the first session message and the second session message, the method further includes: During the execution of the press operation, in response to the trigger operation for the sixth session message, the process of the copy of the sixth session message automatically moving to the third session message is displayed, and the seventh session message obtained by merging the copy of the sixth session message and the third session message is displayed.
18. The method as described in claim 1, characterized in that, After displaying the third session message obtained by merging the first session message and the second session message, the method further includes: Display at least one message processing function item corresponding to the third session message; In response to a trigger operation on a target message processing function item among the at least one message processing function items, the target processing operation indicated by the target message processing function item is performed on the third session message.
19. The method as described in claim 18, characterized in that, The third session message includes at least two sub-contents; the execution of the target processing operation indicated by the target message processing function item on the third session message includes: When the target message processing function item is a voting function item, the voting message corresponding to the third session message is displayed. The voting message includes: options corresponding to each of the sub-contents and voting operation controls. The voting control is used to vote on the sub-content selected based on the options.
20. The method as described in claim 19, characterized in that, After displaying the voting message corresponding to the third session message, the method further includes: In the associated area of each sub-content in the voting message, the voting results of the corresponding sub-content are displayed; The voting result indicates the number of session objects that voted on the corresponding sub-content.
21. The method as described in claim 18, characterized in that, The execution of the target processing operation indicated by the target message processing function item on the third session message includes: When the target message processing function is a meeting minutes function, in response to the trigger operation for the meeting minutes function, the meeting minutes corresponding to the third session message are generated; In response to a storage instruction for the meeting minutes, the meeting minutes are stored.
22. A device for processing session messages, characterized in that, The device includes: The first display module is used to display at least two conversation messages in the conversation interface of the target object, wherein the at least two conversation messages include a first conversation message and a second conversation message; The receiving module is configured to receive a message merging instruction triggered by the target object, wherein the message merging instruction is used to instruct the merging of the first session message and the second session message; The second display module is configured to, in response to the message merging instruction, display a third session message obtained by merging the first session message and the second session message in the session interface when it is determined that the merging conditions are met based on a first time interval; wherein the first time interval is the time interval between the sending time of the first session message and the current time of the drag operation, and the drag operation meets the message movement conditions.
23. An electronic device, characterized in that, The electronic device includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the session message processing method as described in any one of claims 1 to 21.
24. A computer-readable storage medium, characterized in that, The device stores executable instructions, which, when executed, are used to implement the session message processing method as described in any one of claims 1 to 21.
25. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, they implement the session message processing method according to any one of claims 1 to 21.
Citation Information
Patent Citations
Information processing method and device
CN110634220A
Message display method and terminal equipment
CN110673770A
Message processing method and device, terminal and storage medium
CN114422468A