Message processing method and device, electronic equipment and readable storage medium

Abstract

The application discloses a message processing method and device and electronic equipment, and belongs to the technical field of communication. The method comprises the following steps: displaying a target conversation interface; the target conversation interface comprises conversation identifiers corresponding to at least two conversations in which a target user participates; the at least two conversations come from more than one instant messaging application; in response to a first input, displaying input information in an information editing area corresponding to the conversation identifiers; and in response to a second input, sending the input information as a conversation message to a conversation corresponding to a target conversation identifier among the conversation identifiers of the target conversation interface.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a message processing method and device, electronic equipment and a readable storage medium. BACKGROUND

[0002] In today's information age, with the use of electronic devices becoming more popular, people will use communication software in electronic devices for communication. However, due to the difference in the use groups of different communication software, for example, a user is used to using a certain instant messaging application for communication in life, but needs to communicate through another instant messaging application at work.

[0003] Therefore, in order to communicate with different other users in real time, the user needs to switch between different communication software, input and send messages, which leads to a relatively cumbersome process of sending messages in different communication software. SUMMARY

[0004] The embodiments of the present application provide a message processing method, device, electronic equipment and readable storage medium, which can solve the problem of a relatively cumbersome process of sending messages in different communication software.

[0005] In a first aspect, the embodiments of the present application provide a message processing method, which comprises: displaying a target conversation interface; the target conversation interface comprises conversation identifiers corresponding to at least two conversations in which a target user participates; the at least two conversations come from more than one instant messaging application; in response to a first input, displaying input information in an information editing area corresponding to the conversation identifiers; in response to a second input, sending the input information as a conversation message to a conversation corresponding to a target conversation identifier among the conversation identifiers.

[0006] In a second aspect, the embodiments of the present application provide a message processing device, which comprises: a display module and a sending module; the display module is configured to display a target conversation interface; the target conversation interface comprises conversation identifiers corresponding to at least two conversations in which a target user participates; the at least two conversations come from more than one instant messaging application; the display module is configured to display input information in an information editing area corresponding to the conversation identifiers in response to a first input; and the sending module is configured to send the input information as a conversation message to a conversation corresponding to a target conversation identifier among the conversation identifiers in response to a second input.

[0007] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implementing the steps of the method described in the first aspect.

[0008] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0009] Fifthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0010] In a sixth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.

[0011] In this embodiment, the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates. These at least two sessions originate from more than one instant messaging application. In response to a first input, input information is displayed in the information editing area common to all session identifiers on the target session interface. In response to a second input, the input information is sent as a session message to the session corresponding to the target session identifier in the target session interface. Thus, messages can be sent to sessions in different instant messaging applications through the information editing area of ​​the target session interface, avoiding the cumbersome operation of switching between different communication software to send messages. Attached Figure Description

[0012] Figure 1 This is one of the schematic diagrams of a message processing method provided in an embodiment of this application;

[0013] Figure 2 This is one of the schematic diagrams of an interface example of a message processing method provided in the embodiments of this application;

[0014] Figure 3 This is a second schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0015] Figure 4 This is the third schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0016] Figure 5 This is the fourth schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0017] Figure 6 This is the fifth schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0018] Figure 7 This is the sixth schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0019] Figure 8 This is the seventh schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0020] Figure 9 This is the eighth schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0021] Figure 10 This is the ninth schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0022] Figure 11 This is the tenth schematic diagram of an interface example of a message processing method provided in the embodiments of this application;

[0023] Figure 12(a) is an eleventh schematic diagram of an interface example of a message processing method provided in an embodiment of this application;

[0024] Figure 12(b) is a schematic diagram of an interface example of a message processing method provided in an embodiment of this application;

[0025] Figure 13 This is the thirteenth schematic diagram of an interface example of a message processing method provided in this application embodiment;

[0026] Figure 14 This is one of the structural schematic diagrams of a message processing device provided in the embodiments of this application;

[0027] Figure 15 This is a second schematic diagram of the structure of a message processing device provided in an embodiment of this application;

[0028] Figure 16 This is one of the hardware structure diagrams of an electronic device provided in the embodiments of this application;

[0029] Figure 17 This is a second schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0030] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0031] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0032] The message processing method, apparatus, and electronic device provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0033] In real life, we may encounter scenarios where different communication software users have different needs. Daily communication might require using one software (APP1), while work-related communication might require using another (APP2). Sometimes, to communicate with different users in real time, it's necessary to switch back and forth between different software and input information, which is not only cumbersome but also carries the risk of sending incorrect messages or to the wrong recipient.

[0034] Furthermore, when using different communication software for real-time communication, users need to quickly switch between multiple software programs, which is quite cumbersome. At the same time, the content of communication between different users will inevitably differ, and switching communication software may result in forgotten information or messages being sent to the wrong recipient. Moreover, while continuously communicating with other users on one communication software, it's easy to overlook messages on another software, thus missing important information. Additionally, opening multiple communication software programs simultaneously means that all chat messages within each software need to be loaded, increasing the burden on memory resources.

[0035] For example, consider a scenario where a user wants to send message A to contact 1 in "Communication" APP 1, contact 2 in "Communication" APP 2, and contact 3 in "Communication" APP 3. When a user wants to send the same message to three different contacts through three different communication apps, they need to constantly switch between these three apps, editing the message in the corresponding contact's chat interface within each app and then sending it to the appropriate contact. For instance, after sending message A in contact 1's chat interface in "Communication" APP 1, the user needs to switch from "Communication" APP 1 to "Communication" APP 2, and then continue sending message A in contact 2's chat interface in "Communication" APP 2. This makes the entire message sending process cumbersome and time-consuming.

[0036] In this embodiment of the application, a target session interface can be created, and the contact identifiers of three contacts—Contact 1 in "Communication" APP1, Contact 2 in "Communication" APP2, and Contact 3 in "Communication" APP3—can be displayed in the target session interface. This allows users to use the information editing area in the target session interface to send messages to sessions corresponding to different contacts in different "Communication" APPs, simplifying the message sending process across applications.

[0037] The execution subject of the message processing method provided in this application embodiment can be a message processing device, which can be an electronic device or a functional module in the electronic device.

[0038] The technical solution provided in this application will be described below using a message processing device as an example.

[0039] This application provides a message processing method. Figure 1 A flowchart of a message processing method provided in an embodiment of this application is shown, such as... Figure 1 As shown, the message processing method provided in this application embodiment may include the following steps 201 to 205.

[0040] Step 201: Display the target session interface; the target session interface includes the session identifiers corresponding to at least two sessions in which the target user participates; the at least two sessions come from more than one instant messaging application.

[0041] In this embodiment, the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates; these at least two sessions originate from more than one instant messaging application, meaning they are sessions in which the target user participates in at least two instant messaging applications. These at least two sessions may include at least one of contact sessions and group sessions. A contact session is a session between the target user and one of their contacts. A group session is a session between the target user and at least two contacts.

[0042] Optionally, the members of a contact session can be social objects from the same or different instant messaging applications. For example, a contact session in a first instant messaging application can be a session between the target user and a contact in the first instant messaging application, or a session established in the first instant messaging application between the target user and a contact in a second instant messaging application.

[0043] The session identifier is used to uniquely identify a session. For a contact session, the session identifier can be the contact identifier of the contact who is having the session with the target user, such as the contact name or contact avatar. For a group session, the session identifier can be the group name or group avatar. Step 202: Receive the first input.

[0044] Step 203: In response to the first input, display the input information in the information editing area that corresponds to all the session identifiers of the target session interface.

[0045] In this embodiment, the target session interface further includes an information editing area, which is used to receive input operations from the target user. The input information is information entered through the first input. The input information can be text, voice, images, emoticons, files, or audio / video, etc.

[0046] In this embodiment of the application, the first input may include: user touch input on the display screen, or user voice command, or user specific gesture. The specific input can be determined according to actual usage needs, and this embodiment of the invention does not limit it.

[0047] For example, the above-mentioned touch input includes user tap input, swipe input, press input, etc. Specific gestures in this embodiment of the invention can be any one of a single-click gesture, swipe gesture, pressure-recognition gesture, long-press gesture, area-change gesture, double-press gesture, or double-tap gesture; the tap input in this embodiment of the invention can be a single-click input, double-click input, or tap input of any number of times, etc., and the above-mentioned tap input can also be a long-press input or a short-press input.

[0048] Step 204: Receive the second input.

[0049] Step 205: In response to the second input, the above input information is sent as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface.

[0050] The target session identifier is at least one session identifier in the target session interface.

[0051] In one embodiment, in response to the second input, a target session identifier is determined from each session identifier of the target session interface, wherein the number of target session identifiers is at least one, and the input information is sent as a session message to the session corresponding to the target session identifier.

[0052] In this embodiment, the second input is used to send a session message to the session corresponding to the target session identifier. For example, the second input can be dragging the input information to the target session identifier on the target session interface, selecting the target session identifier from among the various session identifiers on the target session interface, or performing a sending operation on the input information. In this embodiment, the second input can include user touch input on the display screen, user-inputted voice commands, or user-inputted specific gestures. The specific input can be determined according to actual usage requirements, and this embodiment does not impose any limitations.

[0053] Optionally, in this embodiment of the application, the above step 203, "in response to the second input, sending the input information as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface," includes the following step 203a:

[0054] Step 203a: In response to the second input, using the first user identifier corresponding to the target user as the message sender, the above input information is sent as a session message to the session corresponding to the target session identifier in the target session interface.

[0055] For example, the first user identifier is the user identifier of the target user in the first instant messaging application, and the session corresponding to the target session identifier comes from the first instant messaging application.

[0056] Further optionally, in this embodiment of the application, the above step 203a, "in response to the second input, using the first user identifier corresponding to the target user as the message sender, sending the above input information as a session message to the session corresponding to the target session identifier in the target session interface," includes the following step 203a1:

[0057] Step 203a1: In response to the second input, the input information is sent as a session message to the session corresponding to the target session identifier in the target session interface through the message transmission interface corresponding to the first instant messaging application, with the first user identifier corresponding to the target user as the message sender.

[0058] For example, different instant messaging applications have different message transmission interfaces.

[0059] In this way, the message processing device can use different message transmission interfaces to send the input information in the target session interface to the corresponding instant messaging application.

[0060] In one embodiment, when a session message is received in the session corresponding to the sixth session identifier, the session message of the sixth session identifier is displayed in the target session interface; the sixth session identifier is one of the session identifiers of the target session interface.

[0061] Optionally, the session message corresponding to the sixth session identifier is received through the message transmission interface of the first instant messaging application, and the session message corresponding to the sixth session identifier is displayed in the target session interface. The session corresponding to the sixth session identifier originates from the first instant messaging application.

[0062] In the message processing method provided in this application embodiment, the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates. These at least two sessions originate from more than one instant messaging application. In response to a first input, input information is displayed in the information editing area common to all session identifiers on the target session interface. In response to a second input, the input information is sent as a session message to the session corresponding to the target session identifier in the target session interface. Thus, messages can be sent to sessions in different instant messaging applications through the information editing area of ​​the target session interface, avoiding the cumbersome operation of switching between different communication software to send messages.

[0063] Optionally, in this embodiment of the application, the target session interface includes at least two session controls, each of which displays a corresponding session identifier.

[0064] In this embodiment of the application, the target session interface displays various session controls, and each session control displays a corresponding session identifier. A session identifier indicates a session in the instant messaging application.

[0065] In one possible embodiment, the above-mentioned session controls can be displayed in the form of a communication interface, or in the form of visual effects such as bubbles, or in the form of a list.

[0066] Example 1, such as Figure 2 As shown, the target conversation interface 21 includes area 21a and area 21b, where area 21b can be a message editing area. Area 21a displays four contact icons 22 (i.e., the aforementioned conversation icons). These four contact icons 22 are displayed as bubble controls (i.e., the aforementioned conversation controls). Specifically, the bubble shape of these four contact icons can be generated based on the corresponding contact information and communication software information, as shown in the reference... Figure 2 The main body of the bubble is the contact's avatar, and below the avatar is their nickname (which can be hidden), such as Amin, Dahuang, Xiaoli, Xiaohong, etc. The icon in the upper right corner indicates the instant messaging application to which the conversation belongs, such as APP1, APP2, and APP3, etc.

[0067] Example 2, such as Figure 3 As shown, the target session interface 21 includes areas 21a and 21b. Area 21a displays three communication interfaces 31 (i.e., the aforementioned session controls), as shown in the figure. Figure 3The corresponding APP icon is generated in the upper right corner of the communication interface, and the contact nickname corresponding to the conversation (i.e., the aforementioned conversation identifier) ​​is displayed in the upper left corner of the communication interface.

[0068] Example 3, such as Figure 4 As shown, the target conversation interface 21 includes an area 21a and an area 21b (i.e., the information editing area). In area 21a, four chat boxes (i.e., the aforementioned conversation controls) corresponding to the conversations are displayed in a sequential order, arranged vertically from left to right: contact avatar, contact nickname, and APP identifier (i.e., the aforementioned conversation identifier). The order can be manually adjusted by long-pressing and dragging. It should be noted that users can customize the chat box display style, such as rounded rectangles or square rectangles. This format is suitable for users familiar with traditional chat software, providing a clear and concise information display, greater freedom in frame adjustment, and better visibility.

[0069] In this way, the corresponding session identifier and session can be displayed in different forms of session controls according to user needs.

[0070] Optionally, in this embodiment of the application, before sending the input information as a session message to the session corresponding to the target session identifier in the target session interface, the message processing device may select a target session control and use the session identifier corresponding to the target session control as the target session identifier.

[0071] For example, referring to Example 1, users can swipe left and right to select a communication interface (i.e., the target session control mentioned above) and use the session identifier corresponding to that communication interface as the target session identifier.

[0072] For example, referring to Example 2, a user selects a bubble (i.e., the target session control mentioned above) by touch, and the communication interface of the session corresponding to that bubble is displayed, with the session identifier corresponding to that bubble serving as the target session identifier.

[0073] For example, referring to Example 3, if a user selects a chat box (i.e., the target session control mentioned above) by touching it, the session identifier corresponding to that chat box will be used as the target session identifier.

[0074] In this way, by using different new message notification methods and message sending methods, users can simply tap or swipe without having to switch back and forth between multiple applications, greatly improving the experience of real-time communication and browsing.

[0075] Optionally, in this embodiment of the application, the second input can be an operation of dragging input information to the session control corresponding to the target session identifier in the target session interface.

[0076] For example, referring to Example 1, in a scenario where the conversation control is displayed in the form of a bubble, such as...Figure 7 As shown, after the user enters the conversation message "Thank you" in the message editing area 21b, they long-press the "Input Line" button, making the entire conversation message draggable. The user can then freely drag the entire message to different avatar bubbles (i.e., the aforementioned conversation controls) to complete the message sending (for example, dragging "Thank you" to the bubble avatar of the contact "Xiao Hong"). Finally, successfully sent conversation messages will be displayed in the communication interface 71. Generally, the communication interface 71 will display the latest n transmitted messages, where n can be set by the user.

[0077] This allows users to easily drag and drop edited information into the corresponding conversation control, simplifying the message sending process.

[0078] Optionally, in this embodiment of the application, the conversation controls in the target conversation interface are displayed in a stacked manner, and the stacking order of the conversation controls is related to the order in which the conversation identifiers corresponding to each conversation control are added.

[0079] Optionally, in this embodiment of the application, the message processing method provided further includes steps 301 and 302:

[0080] Step 301: Receive the fourth input from the first session control in the session identifier corresponding to each session control of the target session interface.

[0081] Step 302: In response to the fourth input, adjust the stacking order of the first session controls.

[0082] In this embodiment of the application, the fourth input may include: touch input by the user to the first conversation control, or voice command input by the user, or specific gesture input by the user, etc. For details, please refer to the first input described above, which will not be repeated here.

[0083] For example, the first session control mentioned above is one of at least one session control in the target session interface.

[0084] For example, the fourth input described above is used to adjust the stacking order of the first session controls.

[0085] For example, the above-mentioned touch input includes click input, swipe input, press input, etc.

[0086] For example, referring to Example 2, in a scenario where the conversation control is displayed as a communication interface, the user can swipe left and right across multiple overlaid communication interfaces to switch between the currently displayed communication interface (i.e., the first conversation control mentioned above). Furthermore, after the top-level communication interface receives the user's swipe input (i.e., the fourth input mentioned above), it shrinks and fades, thus falling to the bottom layer. At this time, the second-to-top-level communication interface enlarges and is clearly displayed on top, and the communication interface swiped to the top automatically adjusts to the center position. In addition, after the user selects the first conversation control, the message processing device will directly display the communication interface corresponding to that first conversation control on top, allowing the user to browse and reply to messages.

[0087] In this way, users can select the conversation they want to view by swiping or touching, which improves the efficiency of viewing conversations.

[0088] Optionally, in this embodiment of the application, the message processing method provided further includes steps S1 to S4:

[0089] Step S1: Display the message prompt control.

[0090] For example, the message notification control described above can be displayed anywhere on the target session interface. For instance, it can be displayed in the lower left corner of the target session interface; or, the message notification control can also be displayed in the information editing area.

[0091] For example, the message notification control described above can be displayed floating on the target session interface. When the user drags the message notification control, the message notification control can move on the target session interface along with the user's dragging operation.

[0092] For example, the above message prompt control can be displayed in the form of a bubble, a rectangle, etc. The specific form can be determined according to actual usage requirements, and the embodiments of the present invention do not limit it.

[0093] Step S2: When the session corresponding to the third session identifier receives a session message, display the third session identifier on the aforementioned message prompt control.

[0094] For example, the third session identifier is at least one of the session identifiers of the target session interface.

[0095] For example, the aforementioned third session identifier is used to indicate a session where a new message exists.

[0096] Step S3: Receive the fifth input to the above message prompt control.

[0097] Step S4: In response to the fifth input, display the session control corresponding to the third session identifier in the first stacking order.

[0098] For example, when session identifiers are displayed in a first stacking order, the session identifier corresponding to the session window in the first stacking order is the target session identifier.

[0099] For example, the fifth input mentioned above may include: touch input by the user to the message prompt control, or voice command input by the user, or specific gesture input by the user, etc. For details, please refer to the first input mentioned above, which will not be repeated here.

[0100] For example, the fifth input described above is used to select the target message prompt control.

[0101] For example, when the message processing device receives multiple new messages, it displays the third session identifiers corresponding to these new messages in superimposed order according to their reception time. Furthermore, the third session identifier corresponding to the most recently received message can typically be displayed at the underlying layer.

[0102] For example, referring to Example 2, in a scenario where the conversation control is displayed as a communication interface, such as... Figure 6 As shown, when the message processing device receives a new message, a corresponding small bubble icon 61 (i.e., the aforementioned message prompt control) will appear on the left side of area 21a of the target session interface and flash to remind the user that there is a new message. At this time, the user clicks on one of the bubbles (i.e., the aforementioned fifth input), triggering the display of the communication interface corresponding to that bubble, thereby using the session icon of the session corresponding to that communication interface as the target session icon, and the bubble bursts and disappears.

[0103] It should be noted that if new messages are generated on multiple communication interfaces, the bubbles will be displayed in chronological order, with the most recently generated message bubble at the bottom, so that users can quickly locate and reply to messages that have not been replied to for a long time.

[0104] For example, the first stacking order mentioned above includes placing the target session identifier on top. That is, after being displayed according to the first stacking order, the target session identifier will be displayed on top.

[0105] For example, when the session control is a communication interface, upon receiving the user's fifth input, the session corresponding to the target session identifier is displayed at the top in response to the fifth input.

[0106] In this way, by using the same information editing area to send messages and real-time message notification icons, the cumbersome steps of switching applications for users are greatly simplified, providing great convenience for scenarios where users of different communication software often need to communicate in real time at the same time.

[0107] Optionally, in this embodiment of the application, the message processing method provided further includes step A:

[0108] Step A: When the session corresponding to the fourth session identifier receives a session message, adjust the size of the session control corresponding to the fourth session identifier, and move the fourth session identifier to the preset area in the target session interface.

[0109] For example, the fourth session identifier mentioned above is one of the session identifiers of the target session interface mentioned above.

[0110] For example, the session corresponding to the fourth session identifier mentioned above is the session that received the new message.

[0111] It should be noted that the fourth session identifier mentioned above can be the same as or different from the target session identifier.

[0112] For example, the aforementioned preset area can be any location on the target session interface, such as the center.

[0113] For example, the different sizes and positions of the session controls corresponding to the fourth session identifier can indicate whether the session corresponding to the fourth session identifier needs to be viewed or operated by the user.

[0114] For example, if a session message is received in the session corresponding to the fourth session identifier, the fourth session identifier is moved to a first preset area of ​​the target session interface (e.g., the center of the target session interface), and the size of the session control corresponding to the fourth session identifier is changed. For example, the shape of the session control corresponding to the fourth session identifier is enlarged.

[0115] For example, after the fourth session identifier is moved to a preset area, if a new message in the session corresponding to the fourth session identifier is in a read state, the fourth session identifier is moved to a second preset position in the target session interface (e.g., the edge area of ​​the target session interface), and the size of the session control corresponding to the fourth session identifier is changed. For example, the shape of the session control corresponding to the fourth session identifier is made smaller.

[0116] It should be noted that users can customize the display status of the fourth session identifier, such as setting the degree of transparency of the bubble, the overall shape and size, the amplitude of flashing vibration, etc., and can choose to turn the bubble flashing vibration on or off.

[0117] For example, when each session corresponding to each session identifier of the target session interface receives a new message within a certain time period, the message processing device can select a fourth session identifier from multiple session identifiers (i.e., the session identifiers corresponding to the sessions that receive new messages among the aforementioned sessions) according to a first predetermined rule.

[0118] For example, the first predetermined rule mentioned above includes at least one of the following: a new message received in the session is an unread message; the reception time of a new message received in the session meets a first condition; and the number of new messages received in the session is greater than or equal to a predetermined number. In one example, the first condition mentioned above includes: the reception time of a new message received in the session is the earliest.

[0119] Example 4: In a scenario where the conversation control is displayed as a bubble, if multiple new messages are continuously received in conversation 1, the bubble corresponding to conversation 1 is used as the fourth conversation identifier. Then, the bubble's shape is updated (e.g., the bubble is enlarged), and the updated bubble is moved to the center of the target conversation interface, making it easier for the user to notice the arrival of new messages. At this time, the bubble can flash and vibrate regularly to remind the user to pay attention to and promptly handle the backlog of new messages.

[0120] Furthermore, after Session 1 is moved to the center position, if a new message in Session 1 has been read, the display state of the bubble corresponding to Session 1 can be updated to a semi-transparent silent state, the bubble size can be reduced, and the updated bubble can be moved to the edge area of ​​the target session interface to spread out.

[0121] In this way, by changing the size and position of the conversation control, a fourth conversation indicator indicating that a new message has been received can be displayed, promptly reminding the user to check the new information and preventing the received information from being missed.

[0122] Optionally, in this embodiment of the application, before step 201 "displaying the target session interface" described above, the message processing method provided in this embodiment of the application further includes steps 401 to 403:

[0123] Step 401: Display the first application interface of the first instant messaging application.

[0124] For example, the first application interface includes a session identifier corresponding to at least one session in which the target user participates in the first instant messaging application.

[0125] Step 402: Receive the third input of the first session identifier from the session identifiers of the first application interface.

[0126] Step 403: In response to the third input above, add the first session identifier to the target session interface.

[0127] For example, the aforementioned first session identifier can be a session identifier. In this case, one first session identifier indicates one session. Specifically, the aforementioned first session identifier may include: the communication interface corresponding to the session, or the contact identifier of the contact corresponding to the session (e.g., the contact's avatar and / or contact's nickname, etc.). The aforementioned first session identifier can be displayed in the form of a communication interface, or in a visual form such as a bubble, or in the form of a list. For example, the aforementioned first application interface can be the session list interface of a first instant messaging application.

[0128] For example, the first session identifier is a session identifier corresponding to at least one session participated in in the first instant messaging application.

[0129] For example, the first application interface described above displays at least one first session identifier, which indicates at least one session in an instant messaging application (i.e., an application installed on an electronic device that can communicate).

[0130] Optionally, in this embodiment of the application, the message processing method provided in this embodiment further includes step B:

[0131] Step B: Display the target session control.

[0132] For example, the target session control described above is used to collect session identifiers displayed in the target session interface.

[0133] In one example, the target control described above can be a floating control that can be moved freely on the screen, and the user can perform operations such as long-pressing and dragging on the floating control. For example, the target control can be displayed floatingly on the target session interface, and when the user drags the target control, the target control can move on the target session interface along with the user's dragging operation.

[0134] In one example, the shape of the target control can be any possible shape such as a circle, rectangle, triangle, rhombus, annulus, or polygon, which can be determined according to actual usage requirements. This embodiment of the invention does not impose any limitations.

[0135] Further optionally, in this embodiment of the application, the process of step 403 "in response to the third input, add the first session identifier to the target session interface" includes the following step 403a:

[0136] Step 403a: In response to the third input mentioned above, add the first session identifier from each session identifier of the first application interface to the target session control.

[0137] In one example, when the target session control is displayed, the user can click on the target session control to open "Chat Space". The target session interface is the display interface of Chat Space.

[0138] For example, when a user wants to enter the chat space, such as Figure 5 As shown, the user can click the floating control 51 to display interface 52, which displays four controls: a "Document" control, a "Music" control, a "Video" control, and a "Chat Space" control. The user can then click the floating control 53 to display the target conversation interface and enter the Chat Space, as shown above. Figures 2 to 4 As shown

[0139] For example, the third input mentioned above may include: touch input from the user to the first session identifier and the target session control, or voice commands input by the user, or specific gestures input by the user, etc. For details, please refer to the first input mentioned above, which will not be repeated here.

[0140] For example, the third input mentioned above includes: drag input where the user drags the first session identifier to the target session control.

[0141] For example, the third input described above is used to select the session corresponding to the first session identifier.

[0142] For example, by performing the above operations on the application interfaces of different applications in sequence, the session identifiers corresponding to different sessions are selected from the application interfaces of different applications, thereby concentrating the different sessions of different applications into the same interface (i.e., the target session interface), thereby achieving the aggregation effect.

[0143] For example, after receiving a third input, the message processing device adds a first session identifier to the target session interface.

[0144] For example, taking the conversation list interface of the first application interface as communication APP1 as an example, such as Figure 8 As shown, when a user wants to add a conversation in the chat space, the user can drag the conversation identifier 82 (i.e. the first conversation identifier mentioned above) corresponding to conversation 2 in the conversation list interface 81 to the floating control 83 (i.e. the target conversation control mentioned above), thereby adding the conversation identifier 83 corresponding to conversation 2 to the chat space.

[0145] It should be noted that when the user drags session identifier 81 above the floating control 83, the floating control automatically recognizes session identifier 82. When the status of session identifier 82 changes (e.g., changes color) and a prompt appears, it indicates that it has been placed in the target session interface. At this point, releasing the control will display session identifier 82 in the target session interface. Simultaneously, the session identifier dragged into the floating control still exists in the original application. Thus, by dragging the communication interface into the floating ball, the communication interfaces of different communication applications are centralized, with the basic unit of centralization being the communication interface of a specific session within different applications.

[0146] For example, when a message processing device moves a session identifier into the target session interface, it typically displays the session identifier according to the time it was moved in. For instance, the session identifier that was moved in first is located at the bottom layer, and the session identifier that was moved in later is located at the top layer. The layers do not completely overlap, so that the user can have a grasp of all session identifier information, status, and quantity.

[0147] This allows users to choose the target session on the target session interface, making it convenient for them to send messages in different sessions within the target session interface.

[0148] Optionally, in this embodiment of the application, before step 201 "displaying the target session interface" described above, the message processing method provided in this embodiment of the application further includes steps C1 to C3:

[0149] Step C1: Display the first interface.

[0150] For example, the first interface mentioned above includes an application identifier corresponding to at least one instant messaging application.

[0151] Step C2: Receive the sixth input of the first application identifier from the application identifiers corresponding to the at least one instant messaging application.

[0152] Step C3: In response to the sixth input, add the fifth session identifier to the target session interface.

[0153] Among them, the session corresponding to the fifth session identifier is the session in the instant messaging application corresponding to the first application identifier that meets the first condition.

[0154] Further optionally, in this embodiment of the application, the above step C3 "in response to the sixth input, add the fifth session identifier to the above target session interface" includes the following step 703a:

[0155] Step C3a: In response to the sixth input, add the fifth session identifier to the target session control mentioned above.

[0156] Further optionally, in this embodiment of the application, after step 702 "receiving the sixth input of the application identifier corresponding to the second instant messaging application in at least one instant messaging application in the first interface", the message processing method provided in this embodiment of the application further includes step A:

[0157] Step A: In response to the sixth input, the application identifier corresponding to the second instant messaging application is added to the target session control.

[0158] For example, the sixth input may include: touch input of the user to the application identifier corresponding to the second instant messaging application, or voice command input by the user, or specific gesture input by the user, etc. For details, please refer to the first input mentioned above, which will not be repeated here.

[0159] For example, the sixth input mentioned above includes: drag input where the user drags the application identifier corresponding to the second instant messaging application to the target session control.

[0160] For example, the sixth input is used to select the application identifier corresponding to the second instant messaging application.

[0161] For example, the target session control described above can be referred to in the preceding description, and will not be repeated here.

[0162] For example, after receiving the sixth input, the message processing device adds the fifth session identifier of the second instant messaging application that meets the first condition to the target session interface (i.e., the target session control), and adds the application identifier corresponding to the second instant messaging application to the target session control. Further, after receiving the sixth input, the message processing device selects sessions that meet the conditions from the sessions in the second instant messaging application according to the first condition, and then adds the session identifiers of these sessions to the target session interface. For example, the sessions corresponding to the aforementioned fifth session identifier are: the sessions in the aforementioned second instant messaging application that meet the first condition.

[0163] For example, a session that satisfies the first condition includes at least one of the following:

[0164] Session 1: In the second instant messaging application, the session message transmission time is within a preset time range;

[0165] Session 2: In the second instant messaging application, a session in which the number of session messages is greater than or equal to a first predetermined threshold;

[0166] Session 3: A session in a second instant messaging application where the included contacts meet the first predetermined conditions.

[0167] For example, the first predetermined condition mentioned above includes: contacts selected by the user, contacts in a specific group, contacts with a specific tag, etc.

[0168] For example, such as Figure 9 As shown, users can directly drag a communication application into the floating control, triggering the message processing device to select chat boxes within that application that meet predetermined rules, and then synchronize all of these chat boxes to the target session interface. For example, as Figure 10 As shown, the rule configuration items for each dimension are displayed, such as the "Time Filter" configuration item, the "Intimacy Filter" configuration item, the "List Filter" configuration item, and the "Real-time Update Filter" configuration item. When the user clicks the switch button corresponding to the "Real-time Update" configuration item, the filtering function can be turned on or off.

[0169] Furthermore, when a user clicks the "Time Filter" configuration item, detailed configuration information for each dimension of that "Time Filter" item will be displayed, for example, Figure 11 The configuration settings interface for the "Time Filtering" option is shown. In this interface, users can freely select a time range. After clicking "Activate", conversations with the user that have a message sending record within that time range will be selected and added to the target conversation interface.

[0170] Similarly, when a user clicks the "List Filter" configuration item, detailed configuration information for each dimension of the "List Filter" configuration item can be displayed, such as the configuration settings interface of the "List Filter" configuration item shown in Figure 12(a). Next, if the user clicks the "Add" control 121, alternative application icons will be displayed (e.g., the icons of APP1, APP2, and APP3 in Figure 12(a)). If the user selects the newly added application icon 122 (i.e., APP1), the user will be redirected to the application interface 124 corresponding to APP1, as shown in Figure 12(b). This interface 124 displays multiple contact information and adds the conversations corresponding to the contact selected by the user to the required list or the avoid list.

[0171] It should be noted that if a session is on the mandatory list, it will be automatically synchronized to the target session interface if the user uses the application identifier of the application containing the session as the target third identifier; conversely, if a session is on the avoidance list, it will not be synchronized to the target session interface under any circumstances.

[0172] For example, combined with Figure 10 If a user clicks the "Intimacy Filter" configuration item, they can set a certain time period (this time is related to the time set in the "Time Filter" configuration item; if the "Time Filter" configuration item is turned off, the default is within 24 hours) for sessions with a message transmission number greater than or equal to a second predetermined threshold as sessions that meet the intimacy condition. Subsequently, the message processing device can filter sessions in each communication application according to the intimacy rule and synchronize the filtered sessions to the target session interface.

[0173] In this way, the method can batch aggregate sessions from different communication applications. By dragging an application icon to the target control and configuring the corresponding time, intimacy, and list filtering dimensions, the desired sessions can be quickly filtered and aggregated. At the same time, it provides a real-time update function, which changes the cumbersome method that previously required users to actively search for new messages. Instead, the system actively pushes and generates sessions and new messages, greatly simplifying the user process and reducing operating costs.

[0174] Optionally, in this embodiment of the application, the message processing method provided in this embodiment of the application further includes step 501:

[0175] Step 501: When the third instant messaging application corresponding to the third application identifier that has been added to the target session control receives the first session message, add the session identifier corresponding to the session in which the first session message received by the third instant messaging application is located to the target session control.

[0176] For example, upon receiving a first session message, a user can add the session tag of the third instant messaging application corresponding to the third application identifier that received the first session message to the target session interface (i.e., the target session control).

[0177] For example, combined with Figure 10 Users can enable the real-time update function by clicking the "Real-time Update" configuration item mentioned above. Furthermore, users can set a preset time by clicking the "Real-time Update" configuration item. It should be noted that this application can set the same preset time for different scenarios, or it can set different preset times for different scenarios, such as setting two preset times, namely preset time a and preset time b.

[0178] Example a: For scenarios where the third identifier is the application identifier, if the reception time of new messages received in the session corresponding to the selected application meets the preset time a, then the session will be automatically synchronized to the target session interface.

[0179] Example b: If a session has been synchronized to the target session interface, and if the session does not receive any new messages within the preset time b, then the session will be removed from the target session interface. It should be noted that if the session transmits messages within the preset time b, then the session will be retained, and the duration will be recalculated.

[0180] Optionally, in this embodiment of the application, the message processing method provided in this embodiment of the application further includes step 502:

[0181] If the target session identifier corresponding to the target session identifier that has been added to the target session interface does not receive a session message within the first predetermined time period, the target session identifier will be removed from the target session interface.

[0182] For example, if the session corresponding to the target session identifier does not receive a session message within a first predetermined time, the message processing device removes the session from the target session interface.

[0183] In this way, the session on the target session interface can be updated in real time according to the received messages, thus making the session on the target session interface the currently active session.

[0184] Optionally, in this embodiment of the application, the message processing method provided in this embodiment of the application further includes steps 601 and 602:

[0185] Step 601: Receive the user's seventh input to the second session control in the target session interface.

[0186] Step 602: In response to the seventh input, perform the target operation.

[0187] For example, the second session control mentioned above is at least one session control in the target session interface.

[0188] For example, the target operation mentioned above includes: turning off the message notification function of the session corresponding to the second session control (i.e., the session corresponding to the second session control is in a do-not-disturb state), or removing the identifier.

[0189] For example, the seventh input mentioned above may include: touch input by the user to at least one session control in the target session interface, or voice command input by the user, or specific gesture input by the user, etc. For details, please refer to the first input mentioned above, which will not be repeated here.

[0190] For example, the seventh input described above is used to select the target operation to be performed.

[0191] For example, after receiving a seventh input, the message processing device displays at least one function option above the second session control or at another specific location, with each function option corresponding to a function. Then, upon receiving user input for a target function option, the target function corresponding to that option can be executed. For example, such as... Figure 13 As shown, when a user long-presses bubble 131, two function options will be displayed on the right side of bubble 131: the "Do Not Disturb" function to turn off the message notification function of the conversation corresponding to bubble 131, and the "Remove" function to remove bubble 131.

[0192] Further optionally, step S4 may include the following: in response to the seventh input, perform the target operation and update the display state of the second session control according to the operation type of the target operation.

[0193] For example, after receiving the seventh input, the message processing device can perform a corresponding target operation on the selected second session control. At this time, the display state of the second session control will be updated according to the operation type of the target operation performed.

[0194] For example, combined with Figure 13 Once the user clicks the "Remove" option, the message processing device can delete the bubble, causing it to burst and disappear.

[0195] For example, if you need to remove a session control, you can drag it back to the target session control to reclaim it. This operation will not affect the communication interface of the session corresponding to that session control.

[0196] In this way, users can further manipulate the session controls in the target session interface to manage the identifiers and their corresponding sessions, thus improving message transmission efficiency.

[0197] It should be noted that the message processing method provided in this application embodiment can be executed by a message processing device. This application embodiment uses the execution of the message processing method by a message processing device as an example to illustrate the message processing device provided in this application embodiment.

[0198] Figure 14 A schematic diagram of a possible structure of the message processing apparatus involved in an embodiment of this application is shown. For example... Figure 14 As shown, the message processing device 700 may include: a display module 701 and a sending module 702; the display module is used to display a target session interface; the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates; the at least two sessions come from more than one instant messaging application; the display module 701 is used to display input information in response to a first input in the information editing area commonly corresponding to each session identifier of the target session interface; the sending module 702 is used to send the input information as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface in response to a second input.

[0199] Optionally, in this embodiment of the application, the sending module 702 is specifically used to respond to the second input, using the first user identifier corresponding to the target user as the message sender, and send the input information as a session message to the session corresponding to the target session identifier; wherein, the first user identifier is the user identifier of the target user in the first instant messaging application, and the session corresponding to the target session identifier comes from the first instant messaging application.

[0200] Optionally, in this embodiment of the application, the sending module 702 is specifically used to respond to the second input by sending the input information as a session message to the session corresponding to the target session identifier through the message transmission interface corresponding to the first instant messaging application, using the first user identifier corresponding to the target user as the message sender.

[0201] Optionally, in the embodiments of this application, combined with Figure 14 ,like Figure 15 As shown, the device 700 further includes: a receiving module 703 and a processing module 704; the display module 701 is also used to display a first application interface of the first instant messaging application; the first application interface includes a session identifier corresponding to at least one session in which the target user participates in the first instant messaging application; the receiving module 703 is used to receive a third input of the first session identifier among the session identifiers of the first application interface; the processing module 704 is used to add the first session identifier to the target session interface in response to the third input.

[0202] Optionally, in this embodiment of the application, the display module 701 is further configured to display a target session control; the target session control is configured to collect session identifiers displayed in the target session interface; the processing module 704 is further configured to add the first session identifier to the target session control in response to the third input.

[0203] Optionally, in this embodiment of the application, the target session interface includes at least two session controls, each session control displays a corresponding session identifier, the session controls are stacked, and the stacking order of the session controls is related to the order in which the session controls corresponding to each session identifier were added.

[0204] Optionally, in this embodiment, the receiving module 703 is further configured to receive a fourth input to the first session control in the session identifier corresponding to each session control of the target session interface; the processing module 704 is further configured to adjust the stacking order of the first session control in response to the fourth input.

[0205] Optionally, in this embodiment, the display module 701 is further configured to: display a message prompt control; when the session corresponding to the third session identifier receives a session message, display the third session identifier on the message prompt control; the third session identifier is one of the session identifiers of the target session interface; the receiving module 703 is further configured to receive a fifth input to the message prompt control; the display module 701 is further configured to, in response to the fifth input, display the session control corresponding to the second session identifier in a first stacking order.

[0206] Optionally, in this embodiment of the application, the target session identifier is the session identifier corresponding to the session window in the first stacking order.

[0207] Optionally, in this embodiment of the application, the processing module 704 is further configured to adjust the size of the session control corresponding to the fourth session identifier and move the fourth session identifier to a preset area in the target session interface when the session corresponding to the fourth session identifier receives a session message; the fourth session identifier is one of the session identifiers in the target session interface.

[0208] Optionally, in this embodiment, the second input is the operation of dragging the input information to the session control corresponding to the target session identifier.

[0209] Optionally, in this embodiment, the display module 701 is further configured to display a first interface; the first interface includes an application identifier corresponding to at least one instant messaging application; the receiving module 704 is further configured to receive a sixth input to the application identifier corresponding to a second instant messaging application in the at least one instant messaging application; the processing module 704 is further configured to add a fifth session identifier to the target session interface in response to the sixth input; wherein the session corresponding to the fifth session identifier is: a session in the second instant messaging application that satisfies the first condition.

[0210] Optionally, in this embodiment of the application, the session that satisfies the first condition includes at least one of the following:

[0211] In the second instant messaging application, there are sessions where the transmission time of the session messages is within a preset time range; in the second instant messaging application, there are sessions where the number of session messages is greater than or equal to a first predetermined threshold; in the second instant messaging application, there are sessions where the included contacts meet the first predetermined conditions.

[0212] Optionally, in this embodiment, the display module 701 is further configured to display the session message of the sixth session identifier in the target session interface when the session corresponding to the sixth session identifier receives a session message; the sixth session identifier is one of the session identifiers in the target session interface. In the message processing apparatus provided in this embodiment, the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates, and the at least two sessions originate from more than one instant messaging application. In response to a first input, input information is displayed in the information editing area commonly corresponding to the session identifiers in the target session interface. In response to a second input, the input information is sent as a session message to the session corresponding to the target session identifier in the session identifiers of the target session interface. Thus, through the information editing area in the target session interface, messages can be sent to sessions in different instant messaging applications, avoiding the cumbersome operation of switching between different communication software to send messages.

[0213] The message processing device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television set (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0214] The message processing device in this application embodiment can be a device with an operating system. The operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0215] The message processing device provided in this application embodiment can achieve... Figures 14 to 15 The various processes implemented in the method implementation examples will not be described again here to avoid repetition.

[0216] Optionally, such as Figure 16 As shown, this application embodiment also provides an electronic device 800, including a processor 801 and a memory 802. The memory 802 stores a program or instructions that can run on the processor 801. When the program or instructions are executed by the processor 801, they implement the various steps of the above message processing method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0217] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0218] Figure 17 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of this application.

[0219] The electronic device 100 includes, but is not limited to, components such as: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

[0220] Those skilled in the art will understand that the electronic device 100 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 110 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 17 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0221] The display unit 106 is used to display a target session interface; the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates; the at least two sessions come from more than one instant messaging application; the display unit 106 is used to display input information in the information editing area commonly corresponding to each session identifier of the target session interface in response to a first input; the processor 110 is used to send the input information as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface in response to a second input.

[0222] Optionally, in this embodiment of the application, the processor 110 is specifically used to respond to the second input by sending the input information as a session message to the session corresponding to the target session identifier, using the first user identifier corresponding to the target user as the message sender; wherein, the first user identifier is the user identifier of the target user in the first instant messaging application, and the session corresponding to the target session identifier comes from the first instant messaging application.

[0223] Optionally, in this embodiment of the application, the processor 110 is specifically used to respond to the second input by sending the input information as a session message to the session corresponding to the target session identifier through the message transmission interface corresponding to the first instant messaging application, using the first user identifier corresponding to the target user as the message sender.

[0224] Optionally, in this embodiment of the application, the display unit 106 is further configured to display a first application interface of the first instant messaging application; the first application interface includes a session identifier corresponding to at least one session in which the target user participates in the first instant messaging application; the user input unit 107 is configured to receive a third input of the first session identifier among the session identifiers of the first application interface; the processor 110 is configured to add the first session identifier to the target session interface in response to the third input.

[0225] Optionally, in this embodiment, the display unit 106 is further configured to display a target session control; the target session control is configured to collect session identifiers displayed in the target session interface; the processor 110 is further configured to add the first session identifier to the target session control in response to the third input.

[0226] Optionally, in this embodiment of the application, the target session interface includes at least two session controls, each session control displays a corresponding session identifier, the session controls are stacked, and the stacking order of the session controls is related to the order in which the session controls corresponding to each session identifier were added.

[0227] Optionally, in this embodiment of the application, the user input unit 107 is further configured to receive a fourth input to the first session control in the session identifier corresponding to each session control of the target session interface; the processor 110 is further configured to adjust the stacking order of the first session control in response to the fourth input.

[0228] Optionally, in this embodiment, the display unit 106 is further configured to: display a message prompt control; when the session corresponding to the third session identifier receives a session message, display the third session identifier on the message prompt control; the third session identifier is one of the session identifiers of the target session interface; the user input unit 107 is further configured to receive a fifth input to the message prompt control; the display unit 106 is further configured to, in response to the fifth input, display the session control corresponding to the second session identifier in a first stacking order.

[0229] Optionally, in this embodiment of the application, the target session identifier is the session identifier corresponding to the session window in the first stacking order.

[0230] Optionally, in this embodiment of the application, the processor 110 is further configured to adjust the size of the session control corresponding to the fourth session identifier and move the fourth session identifier to a preset area in the target session interface when the session corresponding to the fourth session identifier receives a session message; the fourth session identifier is one of the session identifiers in the target session interface.

[0231] Optionally, in this embodiment, the second input is the operation of dragging the input information to the session control corresponding to the target session identifier.

[0232] Optionally, in this embodiment, the display unit 106 is further configured to display a first interface; the first interface includes an application identifier corresponding to at least one instant messaging application; the receiving module 704 is further configured to receive a sixth input to the application identifier corresponding to a second instant messaging application in the at least one instant messaging application; the processor 110 is further configured to add a fifth session identifier to the target session interface in response to the sixth input; wherein the session corresponding to the fifth session identifier is: a session in the second instant messaging application that meets the first condition.

[0233] Optionally, in this embodiment of the application, the session that satisfies the first condition includes at least one of the following:

[0234] In the second instant messaging application, there are sessions where the transmission time of the session messages is within a preset time range; in the second instant messaging application, there are sessions where the number of session messages is greater than or equal to a first predetermined threshold; in the second instant messaging application, there are sessions where the included contacts meet the first predetermined conditions.

[0235] Optionally, in this embodiment of the application, the display unit 106 is further configured to display the session message of the sixth session identifier in the target session interface when the session corresponding to the sixth session identifier receives a session message; the sixth session identifier is one of the session identifiers of the target session interface.

[0236] In the electronic device provided in this application embodiment, the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates. These at least two sessions originate from more than one instant messaging application. In response to a first input, input information is displayed in the information editing area common to all session identifiers on the target session interface. In response to a second input, the input information is sent as a session message to the session corresponding to the target session identifier in the target session interface. Thus, messages can be sent to sessions in different instant messaging applications through the information editing area of ​​the target session interface, avoiding the cumbersome operation of switching between different communication software to send messages.

[0237] It should be understood that, in this embodiment, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 107 includes at least one of a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0238] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 109 may include volatile memory or non-volatile memory, or it may include both volatile and non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0239] Processor 110 may include one or more processing units; optionally, processor 110 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 110.

[0240] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described message processing method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0241] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0242] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above message processing method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0243] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0244] This application provides a computer program product that is stored in a storage medium and executed by at least one processor to implement the various processes of the message processing method embodiments described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0245] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0246] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0247] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A message processing method, characterized in that, The method includes: Display the target session interface; the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates; the at least two sessions come from more than one instant messaging application; In response to the first input, the input information is displayed in the information editing area that corresponds to all session identifiers on the target session interface; In response to the second input, the input information is sent as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface; The target session interface includes at least two session controls, each session control displays a corresponding session identifier, and the session controls are stacked. The stacking order of the session controls is related to the order in which the session controls corresponding to each session identifier were added. The method further includes: When the session corresponding to the fourth session identifier receives a session message, the size of the session control corresponding to the fourth session identifier is adjusted, and the fourth session identifier is moved to a preset area in the target session interface. The fourth session identifier is one of the session identifiers in the target session interface. The different sizes and positions of the session controls corresponding to the fourth session identifier indicate whether the session corresponding to the fourth session identifier needs to be viewed or operated by the user. When the session corresponding to the fourth session identifier receives a session message, adjusting the size of the session control corresponding to the fourth session identifier and moving the fourth session identifier to a preset area in the target session interface includes: When a session message is received in the session corresponding to the fourth session identifier, the fourth session identifier is moved to the first preset area of ​​the target session interface, and the size of the session control corresponding to the fourth session identifier is adjusted. After the fourth session identifier is moved to the first preset area and the session message in the session corresponding to the fourth session identifier is in a read state, the fourth session identifier is moved to the second preset area in the target session interface, and the size of the session control corresponding to the fourth session identifier is adjusted.

2. The method according to claim 1, characterized in that, The step of responding to the second input by sending the input information as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface includes: In response to the second input, the input information is sent as a session message to the session corresponding to the target session identifier, using the first user identifier corresponding to the target user as the message sender; Wherein, the first user identifier is the user identifier of the target user in the first instant messaging application, and the session corresponding to the target session identifier comes from the first instant messaging application.

3. The method according to claim 2, characterized in that, The step of responding to the second input by sending the input information as a session message to the session corresponding to the target session identifier, using the first user identifier corresponding to the target user as the message sender, includes: In response to the second input, the input information is sent as a session message to the session corresponding to the target session identifier through the message transmission interface corresponding to the first instant messaging application, using the first user identifier corresponding to the target user as the message sender.

4. The method according to claim 1, characterized in that, Before the step of displaying the target session interface, the method further includes: The first application interface of the first instant messaging application is displayed; the first application interface includes a session identifier corresponding to at least one session in which the target user participates in the first instant messaging application. Receive a third input for the first session identifier among the session identifiers of the first application interface; In response to the third input, the first session identifier is added to the target session interface.

5. The method according to claim 4, characterized in that, The method further includes: Display target session control; the target session control is used to collect session identifiers displayed in the target session interface; The step of adding the first session identifier to the target session interface in response to the third input includes: In response to the third input, the first session identifier is added to the target session control.

6. The method according to claim 1, characterized in that, The method further includes: Receive the fourth input from the first session control in the session identifier corresponding to each session control of the target session interface; In response to the fourth input, the stacking order of the first session controls is adjusted.

7. The method according to claim 1, characterized in that, The method further includes: Display message prompt control; When a session message is received in the session corresponding to the third session identifier, the third session identifier is displayed on the message prompt control; the third session identifier is one of the session identifiers of the target session interface; Receive a fifth input to the message prompt control; In response to the fifth input, the session control corresponding to the second session identifier is displayed in the first stacking order.

8. The method according to claim 1, characterized in that, The target session identifier is the session identifier corresponding to the session window in the first stacking order.

9. The method according to claim 1, characterized in that, The second input is the operation of dragging the input information to the session control corresponding to the target session identifier.

10. The method according to claim 1, characterized in that, Before the step of displaying the target session interface, the method further includes: The first interface is displayed; the first interface includes an application identifier corresponding to at least one instant messaging application. Receive a sixth input for the first application identifier in the application identifiers corresponding to the at least one instant messaging application; In response to the sixth input, the fifth session identifier is added to the target session interface; The session corresponding to the fifth session identifier is the session in the instant messaging application corresponding to the first application identifier that meets the first condition.

11. The method according to claim 10, characterized in that, The session that satisfies the first condition includes at least one of the following: In the second instant messaging application, the session message transmission time is within a preset time range; In the second instant messaging application, there are sessions where the number of session messages is greater than or equal to a first predetermined threshold. In a second instant messaging application, there are conversations with contacts that meet a first predetermined condition.

12. The method according to claim 1, characterized in that, The method further includes: When a session message is received in the session corresponding to the sixth session identifier, the session message of the sixth session identifier is displayed in the target session interface; the sixth session identifier is one of the session identifiers in the target session interface.

13. A message processing device, characterized in that, The device includes: a display module, a transmission module, and a processing module; The display module is used to display the target session interface; the target session interface includes session identifiers corresponding to at least two sessions in which the target user participates; the at least two sessions come from more than one instant messaging application; The display module is used to display input information in response to the first input in the information editing area that corresponds to each session identifier of the target session interface. The sending module is used to respond to the second input by sending the input information displayed by the display module as a session message to the session corresponding to the target session identifier in each session identifier of the target session interface; The target session interface includes at least two session controls, each session control displays a corresponding session identifier, and the session controls are stacked. The stacking order of the session controls is related to the order in which the session controls corresponding to each session identifier were added. The processing module is used to adjust the size of the session control corresponding to the fourth session identifier when the session corresponding to the fourth session identifier receives a session message, and to move the fourth session identifier to a preset area in the target session interface. The fourth session identifier is one of the session identifiers in the target session interface. The different sizes and positions of the session controls corresponding to the fourth session identifier indicate whether the session corresponding to the fourth session identifier needs to be viewed or operated by the user. The processing module is specifically used for: When a session message is received in the session corresponding to the fourth session identifier, the fourth session identifier is moved to the first preset area of ​​the target session interface, and the size of the session control corresponding to the fourth session identifier is adjusted. After the fourth session identifier is moved to the first preset area and the session message in the session corresponding to the fourth session identifier is in a read state, the fourth session identifier is moved to the second preset area in the target session interface, and the size of the session control corresponding to the fourth session identifier is adjusted.

14. The apparatus according to claim 13, characterized in that, The sending module is specifically used to respond to the second input by sending the input information as a session message to the session corresponding to the target session identifier, using the first user identifier corresponding to the target user as the message sender; wherein, the first user identifier is the user identifier of the target user in the first instant messaging application, and the session corresponding to the target session identifier comes from the first instant messaging application.

15. The apparatus according to claim 14, characterized in that, The sending module is specifically used to respond to the second input by sending the input information as a session message to the session corresponding to the target session identifier through the message transmission interface corresponding to the first instant messaging application, using the first user identifier corresponding to the target user as the message sender.

16. The apparatus according to claim 13, characterized in that, The message processing device further includes: a receiving module and a processing module; the display module is further configured to display a first application interface of the first instant messaging application; the first application interface includes a session identifier corresponding to at least one session in which the target user participates in the first instant messaging application; the receiving module is configured to receive a third input to the first session identifier among the session identifiers of the first application interface; the processing module is configured to add the first session identifier to the target session interface in response to the third input.

17. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the message processing method as described in any one of claims 1 to 12.

18. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the message processing method as described in any one of claims 1 to 12.

Images