Message transmission method, message reception method and device, apparatus, and computer program

Abstract

To provide a transmission method and a reception method of instant messaging, and a device, an apparatus and a medium.SOLUTION: A method includes: displaying a profile picture of a second user account on a first user interface; in response to an interactive instruction triggered on the profile picture of the second user account, generating an interactive message based on a first field corresponding to a first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account; and transmitting the interactive message to a second client logged in to the second user account.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to a Chinese patent application filed on June 29, 2020, bearing application number 202010603972.5 and entitled "Message sending method, message receiving method and device, apparatus and medium," the entire contents of which are incorporated herein by reference.

[0002] Technical Field TECHNICAL FIELD The embodiments of the present application relate to the field of instant messaging, and in particular to a method and apparatus for sending a message, a method and apparatus for receiving a message, an apparatus, and a medium. [Background technology]

[0003] Instant messaging programs offer private chat and group chat features, where a private chat feature is a chat feature between two user accounts, and a group chat feature is a chat feature between multiple user accounts.

[0004] Taking the group chat function as an example, if user account A wants to interact with user account B, user account A can send a group chat message by "@user account B." At this time, user account B will receive a notification and view the group chat message. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a message sending method, a message receiving method and device, an apparatus, and a medium. The technical configuration is as follows. [Means for solving the problem]

[0006] According to one aspect of the present application, there is provided a method of sending a message executed by a first client logged into a first user account, the method comprising: displaying a profile picture of the second user account on the first user interface; generating an interactive message based on a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account in response to an interactive command triggered on a profile picture of the second user account; sending the interactive message to a second client logged into the second user account; The present invention provides a method for sending a message, comprising:

[0007] According to another aspect of the present application, there is provided a method of receiving a message executed by a second client logged into a second user account, the method comprising: displaying a second chat window interface, where chat members in the second chat window interface include a first user account and the second user account; receiving an interactive message sent from the first user account to the second user account, the message content of the interactive message including a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account; displaying the interactive message in the second chat window interface; The present invention provides a method for receiving a message, comprising:

[0008] According to another aspect of the present application, there is provided a message sending device logged into a first user account, the message sending device comprising: a display module for displaying a profile picture of the second user account on the first user interface; a generating module that generates an interactive message based on a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account in response to an interactive command triggered on a profile picture of the second user account; a sending module for sending the interactive message to a second client logged into the second user account; The present invention provides a message sending device comprising:

[0009] According to another aspect of the present application, there is provided a message receiving device logged into a second user account, the message receiving device comprising: a display module for displaying a second chat window interface, where chat members in the second chat window interface include a first user account and the second user account; a receiving module for receiving an interactive message sent from the first user account to the second user account, the message content of the interactive message including a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account; Equipped with the display module displays the interactive message in the second chat window interface. A message receiving device is provided.

[0010] According to another aspect of the present application, there is provided a computing device comprising a processor and a memory having stored therein at least one instruction, at least one program, code set or instruction set that is loaded and executed by the processor to implement a message sending method or a message receiving method according to the above-mentioned aspect.

[0011] According to another aspect of the present application, there is provided a computer-readable storage medium having stored thereon at least one instruction, at least one program, code set, or instruction set that is loaded and executed by the processor to realize the message sending method or the message receiving method described in the above aspect. [Brief description of the drawings]

[0012] In order to more clearly explain the technical configuration in the embodiments of the present application, the drawings necessary for describing the embodiments will be briefly introduced below. However, the drawings described below are merely illustrative of some embodiments of the present application, and it goes without saying that those skilled in the art can obtain other drawings from these drawings without any creative effort. [Figure 1] FIG. 2 is a structural block diagram of a computer system according to an exemplary embodiment of the present application. [Diagram 2] FIG. 2 is a schematic diagram of an interface for light interactive messaging according to an exemplary embodiment of the present application; [Diagram 3] 4 is a method flowchart of a message sending method according to another exemplary embodiment of the present application; [Figure 4] 4 is a method flowchart of a message receiving method according to another exemplary embodiment of the present application; [Diagram 5] FIG. 13 is an interface schematic diagram of a person attribute interface according to another exemplary embodiment of the present application. [Figure 6] FIG. 13 is an interface diagram of a contacts interface according to another exemplary embodiment of the present application; [Figure 7]FIG. 13 is an interface schematic diagram of a group member display interface (group chat details page) according to another exemplary embodiment of the present application. [Figure 8] FIG. 13 is an interface schematic diagram of a personal chat member display interface (personal chat detail page) according to another exemplary embodiment of the present application. [Figure 9] FIG. 13 is an interface schematic diagram of a social circle display interface according to another exemplary embodiment of the present application. [Figure 10] 4 is a flowchart of a message sending / receiving method according to another exemplary embodiment of the present application; [Figure 11] FIG. 13 is an interface schematic diagram of a message sending / receiving method according to another exemplary embodiment of the present application; [Figure 12] FIG. 13 is a schematic diagram of an interface of a message sending / receiving method according to another exemplary embodiment of the present application; [Figure 13] FIG. 13 is an interface schematic diagram of a message sending / receiving method according to another exemplary embodiment of the present application; [Figure 14] 2 is a flowchart of a method for customizing a first field according to an exemplary embodiment of the present application; [Figure 15] FIG. 2 is a schematic interface diagram of a first field customization method according to an exemplary embodiment of the present application; [Figure 16] 4 is a flowchart of a method for customizing a second field according to an exemplary embodiment of the present application; [Figure 17] FIG. 11 is a schematic interface diagram of a method for customizing a second field according to an exemplary embodiment of the present application; [Figure 18] 4 is a flowchart of a message sending / receiving method according to another exemplary embodiment of the present application; [Figure 19] FIG. 13 is an interface schematic diagram of a person attribute page according to another exemplary embodiment of the present application; [Figure 20] 4 is a flowchart of a message sending / receiving method according to another exemplary embodiment of the present application; [Figure 21]FIG. 13 is an interface schematic diagram of a read folding policy according to another exemplary embodiment of the present application; [Figure 22] FIG. 13 is an interface schematic diagram of an interrupt folding policy according to another exemplary embodiment of the present application; [Diagram 23] FIG. 2 is a block diagram of a message sending device according to another exemplary embodiment of the present application; [Figure 24] FIG. 2 is a block diagram of a message receiving device according to another exemplary embodiment of the present application; [Diagram 25] FIG. 2 is a block diagram of a terminal according to another exemplary embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] In order to make the objectives, technical configurations and advantages of the present application clearer, the embodiments of the present application will be described in more detail below with reference to the drawings.

[0014] In existing instant messaging programs, interactions using "@user account" may be a strong reminder to the reminded user, and depending on the situation, it may not be appropriate to use the strong reminder function. Therefore, the embodiment of the present application provides a message exchange method with a light reminder function, and a corresponding method, device, equipment, etc. for sending / receiving light interactive messages.

[0015] 1 shows a structural block diagram of a computer system according to an exemplary embodiment of the present application. The computer system 100 includes a first terminal 110, a server 120, and a second terminal .

[0016] A first client 111 supporting instant messaging is installed and executed on the first terminal 110, and the first client 111 may be an application program or a web client with an instant messaging function. When the first client 111 is executed on the first terminal 110, a user interface of the first client 111 is displayed on the screen of the first terminal 110. The first terminal 110 is a terminal used by a first user 112, and the first client 111 is logged into a first user account of the first user 112. A second client 131 supporting instant messaging is installed and executed on the second terminal 130, and the second client 131 may be an application program or a web client with an instant messaging function. When the second client 131 is executed on the second terminal 130, a user interface of the second client 131 is displayed on the screen of the second terminal 130. The second terminal 130 is a terminal used by the second user 113, and a second client 131 is logged into the second user account of the second user 113. The application program may be any one of an instant messaging program, a microblog program, a voice call program, a conference program, an online community program, a payment program, a shopping program, a social networking program, and a matching program. In the embodiment of the present application, the application program is an instant messaging program.

[0017] Exemplarily, the application programs installed on the first terminal 110 and the second terminal 130 are the same, or the application programs installed on the two terminals are the same type of application programs on different operating system platforms (Android or IOS). The first terminal 110 may refer to one of the multiple terminals in a general sense, and the second terminal 130 may refer to the other of the multiple terminals in a general sense. In this embodiment, only the first terminal 110 and the second terminal 130 are taken as examples for description. The device types of the first terminal 110 and the second terminal 130 may be the same or different. The device types include at least one of a smartphone, a tablet computer, an e-book reader, an MP3 player, an MP4 player, a laptop computer, and a desktop computer.

[0018] Although only two terminals are shown in FIG. 1, in different embodiments, there may be multiple other terminals 140 that can access the server 120. Illustratively, there are one or more terminals 140 corresponding to developers. A client development and editing platform supporting instant messaging is installed on the terminal 140, and the developer can edit and update the client on the terminal 140 and transmit the updated application program installation package to the server 120 via a wired or wireless network. The first terminal 110 and the second terminal 130 can download the application program installation package from the server 120 to update the client.

[0019] A first terminal 110, a second terminal 130 and another terminal 140 are connected to a server 120 via a wireless network or a wired network.

[0020] The server 120 includes at least one of a server, a plurality of servers, a cloud computing platform, and a virtualization center. The server 120 provides background services for clients that support instant messaging. Illustratively, the server 120 is responsible for main computing tasks, and the terminal is responsible for secondary computing tasks, or the server 120 is responsible for secondary computing tasks, and the terminal is responsible for main computing tasks, or the server 120 and the terminal use a distributed computing architecture to perform collaborative computing.

[0021] In a schematic example, the server 120 includes a processor 122, a user account database 123, an instant messaging service module 124, and an input / output interface (I / O interface) 125 for users. The processor 122 loads instructions stored in the server 120 and processes data in the user account database 123 and the instant messaging service module 124. The user account database 123 stores data of user accounts used by the first terminal 110, the second terminal 130, and the other terminals 140, such as a profile picture of the user account (also called a "profile picture", "avatar", or "icon picture"), an alias of the user account, a group in which the user account is located, etc. The instant messaging service module 124 provides multiple chat rooms (two-person chat or multi-person chat) for users to chat, send stickers, send lucky money, and perform other instant messaging. The user I / O interface 125 establishes communication and exchanges data with the first terminal 110 and / or the second terminal 130 via a wireless or wired network.

[0022] In addition to the above description of the computer system structure, a method for sending (or receiving) a message according to an embodiment of the present application will be described below. The method will be described by taking as an example a case where the execution subject of the method is a client running on the terminal shown in Fig. 1. The client, which is an application program supporting instant messaging, is running on the terminal.

[0023] 2A and 2B show a first user interface 10 of a first client 111 and a second user interface 20 of a second client 131. The first client 111 is logged in to the first user account, and the second client 131 is logged in to the second user account. The first user account and the second user account can send and receive chat messages in a chat window interface for two-person chat (one-to-one chat, also called interpersonal chat or private chat) or a chat window interface for group chat of multiple people. As shown in FIG. 2A and FIG. 2B, the first user interface 10 and the second user interface 20 are chat window interfaces for two-person chat. The first user interface 10 and the second user interface 20 display a profile picture 12 of the first user account, a profile picture 22 of the second user account, and chat messages between the first user account and the second user account, including chat messages 1, 2, and 3.

[0024] As shown in Figures 2A and 2B, when a first user double-tap with a finger on a profile picture of a second user account corresponding to a chat message 2 on the first user interface 10 (not shown, but one may also refer to 22, which is the profile picture of the second user account), the first user interface 10 and the second user interface 20 display the profile picture of the second user account corresponding to the chat message 2 as a profile video 22-1 (as an example), and the first user interface 10 and the second user interface 20 display a light interactive message 30.

[0025] The light interactive message 30 is a message different from a chat message. Illustratively, the message content of the light interactive message 30 is constructed by the client. The message content of the light interactive message 30 includes a first field corresponding to a first user account, an action description field indicating that the first user account performs an action on a second user account, and a second field corresponding to the second user account. At least one of the first field, the action description field, and the second field is a custom field that is pre-edited by a user for the light interactive message.

[0026] For example, in the first user interface 10, the message content of the light interactive message 30 is that "I" who is giggling lightly tapped "User Account 2" on the head. In the second user interface 20, the message content of the light interactive message 30 is that "User Account 1" who is giggling lightly tapped "I" on the head.

[0027] 3 shows a flowchart of a message sending method according to an exemplary embodiment of the present application. In this embodiment, the method is performed by a first client shown in FIG. 1, which is logged into a first user account. The method includes the following steps:

[0028] Step 302 displays a profile picture of a second user account on the first user interface.

[0029] The first user interface is any user interface in which a profile picture of the second user account is displayed on the first client. Illustratively, the first user interface is a non-chat window interface or a first chat window interface.

[0030] The non-chat window interface includes, for example, at least one of a person attribute interface, a contacts interface, a group member display interface, a person-to-person chat member display interface, and a social circle interactive interface. The first chat window interface is a user interface for a first user account to chat with another user account. The first chat window interface includes a chat window interface for a two-person chat (e.g., a chat between the first user account and a second user account) or a chat window interface for a multi-person group chat (e.g., a chat between the first user account, the second user account, and another user account).

[0031] The first chat window interface may display a chat message list sorted according to a timeline. In each chat message in the chat message list, a profile picture of the user account that is the sender and the message content of the chat message may be displayed. Illustratively, each chat message also displays the annotation name, group alias, or custom alias of the user account. The annotation name is a name that other user accounts have annotated for the current user account, the group alias is an alias that the current user account has defined for itself in the group, and the custom alias is an alias that the current user account has defined for itself in the client.

[0032] In some embodiments, the first user account and the second user account are different user accounts, while in other embodiments, the first user account and the second user account are the same user account.

[0033] At step 304, an interactive message is generated in response to the interactive instruction triggered on the profile picture of the second user account.

[0034] The first user performs a trigger operation on a profile picture of the second user account, and the trigger operation may include at least one of a double tap operation, a single tap operation, and a long press operation. In this embodiment, the interactive command is described by taking a double tap command as an example.

[0035] In some embodiments, the interaction is a light interaction. The interactive command is a light interactive command, and the interactive message is a light interactive message. The light interaction is compared to a traditional "@user account" interaction, which is a strong reminder to the reminded user account. The light interaction may be an interaction triggered by an operation on a user's profile picture. After receiving the trigger operation, the first client triggers to generate a light interactive command, and generates a light interactive message based on a first field corresponding to the first user account, a second field corresponding to the second user account, and an action description field. In general, the light interactive message includes a first field, an action description field, and a second field, which are arranged in order.

[0036] The action description field is a field that indicates that a first user account performs an action on a second user account, for simulating a user's communication action in a real environment, such as tapping, hugging, stroking, kicking, poking, touching, kissing, etc.

[0037] In some embodiments, the first field may be a name of a first user account, the action description field may be a server-predefined field, and the second field may be a name of a second user account. In other embodiments, at least one of the first field, the second field, and the action description field is a custom field pre-edited by a user for light interactive messages.

[0038] In some embodiments, all or a portion of the text in a first field corresponding to a first user account is pre-customized by a first user, and all or a portion of the text in a second field corresponding to a second user account is pre-customized by a second user.

[0039] In some embodiments, the action description field is pre-customized by the first user or the second user. If both the first user and the second user customize the action description field, one of the two action description fields is selected for use according to a priority rule. For example, the priority of the sender of the light interactive message is higher than the priority of the receiver of the light interactive message.

[0040] A light interactive message is a different message type than a chat message. Illustratively, a light interactive message may be implemented in a system message format or in a custom message format.

[0041] In step 306, the interactive message is sent to a second client logged into a second user account.

[0042] Sending the light interactive message to a second client logged into a second user account may be performed by sending the light interactive message to the second client via the first client and a server (e.g., an instant messaging server) corresponding to the second client.

[0043] The light interactive message triggers the second client to display the light interactive message in a second chat window interface. Illustratively, the light interactive message also triggers the second client to display a profile animation of a profile picture of the second user account in the second chat window interface. Illustratively, the profile animation is a jittering animation of the profile picture.

[0044] As described above, in the method according to the present embodiment, an interactive message is generated according to an interactive command triggered on a profile picture of a second user account, and at least one of the first field, the action description field, and the second field in the interactive message is a custom field pre-edited by the user. Since the two users cannot predict what the other user's custom field is, a new interaction method with a light reminder function is provided, which is suitable for interesting interactions in a chat scene with a fun and relaxed atmosphere.

[0045] 4 shows a flowchart of a message receiving method according to an exemplary embodiment of the present application. In this embodiment, the method is performed by the second client shown in FIG. 1, which is logged into a second user account. The method includes the following steps:

[0046] In step 402, a second chat window interface is displayed.

[0047] The second chat window interface is a chat window interface in which the second user account chats with at least the first user account. The second chat window interface is a chat window interface for two-person chat or a chat window interface for a group chat of multiple people. For example, the chat window interface for two-person chat means a chat window interface of the first user account and the second user account, and the chat window interface for the group chat of multiple people means a chat interface for a group chat between the first user account, the second user account, and another user account. Illustratively, the second chat window interface displays a chat message list sorted according to a timeline.

[0048] In each chat message in the chat message list, a profile picture of the user account that is the sender and the message content of the chat message may be displayed. Illustratively, each chat message also displays the annotation name, the alias in the group, or the custom alias of the user account. The annotation name is a name that other user accounts have annotated for the current user account, the alias in the group is an alias that the current user account has defined for itself in the group, and the custom alias is an alias that the current user account has defined for itself in the client. The annotation name may be a name that the current user account has annotated for other user accounts.

[0049] An example will be given in which the second chat window interface is a chat window interface for a group chat of multiple people, where the group of multiple people includes at least two user accounts, including a first user account, a second user account, and another user account.

[0050] In step 404, an interactive message sent from the first user account to the second user account is received.

[0051] A second client receives an interactive message between the first user account and the second user account, the interactive message being a light interactive message triggered and generated by the first user on the first client, the first client being a client logged into the first user account.

[0052] Generally speaking, a light interactive message includes a first field, an action description field, and a second field, in sequence.

[0053] The action description field is a field that indicates that a first user account performs an action on a second user account, for simulating a user's communication action in a real environment, such as tapping, hugging, stroking, kicking, poking, touching, kissing, etc.

[0054] In some embodiments, the first field may be a name of a first user account, the action description field may be a server-predefined field, and the second field may be a name of a second user account. In other embodiments, at least one of the first field, the second field, and the action description field is a custom field pre-edited by a user for light interactive messages.

[0055] In some embodiments, all or a portion of the text in a first field corresponding to a first user account is pre-customized by a first user, and all or a portion of the text in a second field corresponding to a second user account is pre-customized by a second user.

[0056] In some embodiments, the action description field is pre-customized by the first user or the second user. If both the first user and the second user customize the action description field, one of the two action description fields is selected for use according to a priority rule. For example, the priority of the sender of the light interactive message is higher than the priority of the receiver of the light interactive message.

[0057] A light interactive message is a different message type than a chat message. Illustratively, a light interactive message may be implemented in a system message format or in a custom message format.

[0058] At step 406, the interactive message is displayed in the second chat window interface, along with a profile animation of the profile picture of the second user account.

[0059] Illustratively, the light interactive message not only triggers the second client to display a profile video of the profile picture of the second user account in the second chat window interface, but also triggers the second client to display the light interactive message in the second chat window interface.

[0060] As described above, in the method of this embodiment, at least one of the first field, the action description field, and the second field in the light interactive message is a custom field pre-edited by the user, and two users cannot predict what the other user's custom field is, so a new interaction method with a light reminder function is provided, which is suitable for interesting interactions in chat scenes with a fun and relaxed atmosphere.

[0061] In one embodiment shown in Figures 5A and 5B, the person attribute interface 40 is a user interface for displaying person attribute information of a second user account. The person attribute information of the second user account includes at least one of the following: the second user account, the name of the second user account (alias / group member name / annotation name), a profile picture of the second user account, a region where the second user account is located, the phone number of the second user account, the tag of the second user account, a privacy setting for the second user account, a personal album of the second user account, and information shown by the second user account in Moments. When the first user double-tap the profile picture 22-5 of the second user account on the person attribute interface 40 (as shown in Figure 5A), a light interactive message 30-5 is displayed around the profile picture 22-5 of the second user account (as shown in Figure 5B), indicating that "I" lightly tapped the thigh of "User Account 2". At the same time, the second client of "User Account 2" receives the light interactive message. The light interactive message may be sent from a first client to a second client.

[0062] In one embodiment shown in FIG. 6A and FIG. 6B, the contact interface 50 is a user interface for displaying all friend user accounts of the first user account. The friend user accounts of the first user account include the second user account. Illustratively, the contact interface 50 further includes at least one of a chat group, a subscription account, and an official account saved by the first user account. The contact interface 50 includes a plurality of friend user accounts arranged by the initials of Pinyin (Chinese pronunciation). When the first user double-tap the profile picture 22-6 of the second user account in the contact interface 50 (as shown in FIG. 6A), a light interactive message 30-6 is displayed around the profile picture 22-6 of the second user account, indicating that "I" lightly tapped "Friend B4" on the thigh (as shown in FIG. 6B). At the same time, the second client of "Friend B4" receives the light interactive message. The light interactive message may be sent from the first client to the second client.

[0063] In one embodiment shown in FIG. 7A and FIG. 7B, the group member display interface 60 is a user interface for displaying group members of the group in which the first user account is located. Illustratively, the group member display interface 60 further displays information such as a group name, a group QR code, a group notification, a comment, an entry for history search, a button for muting notifications, a button for displaying at the top, and a button for saving to contacts. When the first user double-tap the profile picture 22-7 of the second user account in the group member display interface 60 (as shown in FIG. 7A), a light interactive message 30-7 is displayed around the profile picture 22-7 of the second user account, indicating that "I" lightly tapped the thigh of "user account 2" (as shown in FIG. 7B). At the same time, the second client of "user account 2" receives the light interactive message. The light interactive message may be sent from the first client to the second client.

[0064] In one embodiment shown in Figures 8A and 8B, in a chat details interface 70 in which a first user account and a second user account are engaged in a two-person chat, the first user may trigger a light interactive message 30-8 (as shown in Figure 8B) by double-tapping the profile picture 22-8 of the second user account (as shown in Figure 8A).

[0065] In one embodiment shown in FIG. 9A and FIG. 9B, the social circle interactive interface 80 is a user interface for displaying posted information of a first user account and a friend user account of the first user account. The posted information is display information assembled from at least one of the following information: text, picture, audio, video, location, and time. When the first user double-tap the profile picture 22-9 of the second user account (as shown in FIG. 9A), a light interactive message 30-9 is displayed around the profile picture 22-9 of the second user account, indicating that "I" tapped "Prince" on the shoulder (as shown in FIG. 9B). At the same time, the second client of "Prince" receives the light interactive message. The light interactive message may be sent from the first client to the second client.

[0066] 10 shows a flowchart of a message sending / receiving method according to another exemplary embodiment of the present application. In this embodiment, the method is performed by the first client and the second client shown in FIG. 1. The method includes the following steps:

[0067] In step 1001, a first client displays a profile picture of a second user account on a first user interface.

[0068] The first user interface is any user interface on the first client in which a profile picture of the second user account is displayed. The first user interface may be a non-chat window interface or a first chat window interface.

[0069] The first chat window interface is a user interface for a first user account to chat with another user account. The first chat window interface includes a chat window interface for a two-person chat or a group chat with multiple people. The first chat window interface displays a chat message list sorted according to a timeline.

[0070] In some embodiments, the first user account and the second user account are different user accounts, while in other embodiments, the first user account and the second user account are the same user account.

[0071] In step 1002, the first client generates an interactive message in response to a double-tap instruction triggered on a profile picture of a second user account.

[0072] The first user performs a trigger operation on a profile picture of the second user account, and the trigger operation may include at least one of a double tap operation, a single tap operation, and a long press operation. In this embodiment, the light interactive command is described by taking a double tap command as an example.

[0073] After receiving the trigger operation, the first client triggers to generate a light interactive instruction, and generates a light interactive message according to a first field corresponding to the first user account, a second field corresponding to the second user account, and an action description field. In general, the light interactive message includes a first field, an action description field, and a second field arranged in order.

[0074] The action description field is a field that indicates that a first user account performs an action on a second user account, for simulating a user's communication action in a real environment, such as tapping, hugging, stroking, kicking, poking, touching, kissing, etc.

[0075] At least one of the first field, the second field and the action description field is a custom field pre-edited by a user for a light interactive message.

[0076] In some embodiments, all or a portion of the text in a first field corresponding to a first user account is pre-customized by a first user, and all or a portion of the text in a second field corresponding to a second user account is pre-customized by a second user.

[0077] In some embodiments, the action description field is pre-customized by the first user or the second user. If both the first user and the second user customize the action description field, one of the two action description fields is selected for use according to a priority rule. For example, the priority of the sender of the light interactive message is higher than the priority of the receiver of the light interactive message.

[0078] Illustratively, the light interactive message is implemented in a system message format, and illustratively, the system message includes a first user account and a second user account, or the system message includes a first user account, a second user account, and a light interaction identifier, or the system message includes a first field, a second field, and an action description field.

[0079] In some embodiments, the first client also displays, in the first user interface, a profile video of the profile picture of the second user account, the profile video being a video displayed with respect to the profile picture of the second user account. With respect to the profile picture of the second user account, for example, the profile video is with respect to a position of the profile picture of the second user account or an area of ​​the profile picture. Illustratively, the profile video includes, but is not limited to, at least one of a video in which the profile picture of the second user account is jittered, a video in which the profile picture of the second user account is rotated, a video in which a filter is applied to the profile picture of the second user account, a video in which another display element (e.g., a person's hand) is superimposed on the profile picture of the second user account, and a video in which the profile picture of the second user account is reduced or enlarged.

[0080] The profile video may be always displayed or may be occasionally displayed. In general, in response to the first user interface being a non-chat window interface, the first client does not display a profile video of a profile picture of the second user account. In response to the first user interface being a first chat window interface, the first client displays a profile video of a profile picture of the second user account.

[0081] In this embodiment, a case will be described as an example in which the profile video is a video in which jitter has been added to the profile picture of the second user account.

[0082] In step 1003, the first client displays the message content of the interactive message in a first user interface.

[0083] In some embodiments, the first client displays the light interactive message in a target area in the first user interface relative to a profile picture of the second user account. The target area is a region around the profile picture of the second user account, such as a right area or a lower area. In some embodiments, in response to the first user interface being a non-chat window interface, the first client displays a light interactive message such as the light interactive messages 30-5, 30-6, 30-7, and 30-8 shown in FIGS. 5B to 8B in a target area in the non-chat window interface relative to the profile picture of the second user account. In some embodiments, in response to a display time of the light interactive message reaching a threshold, the display of the light interactive message in the non-chat window interface is cancelled. Generally, the threshold is 3 seconds, 5 seconds, and the like.

[0084] In some embodiments, in response to the first user interface being the first chat window interface, the first client displays a light interactive message, such as 30-11 shown in FIG. 11B, in the first chat window interface. When displaying the light interactive message in the first chat window interface, a message display form of the light interactive message is different from a message display form of the chat message.

[0085] For example, the message display format of a light interactive message is to display the message content in the form of text without a speech bubble in the background, whereas the message display format of a chat message is to display the message content in the form of a speech bubble in the background. That is, light interactive messages are not displayed in the form of speech bubbles, but in the message display format of system messages.

[0086] Exemplarily, when the first client displays a light interactive message, the message content of the light interactive message is assembled by the first client itself. For example, the message content of the light interactive message includes a first field, an action description field, and a second field, which are arranged in order. This is because a certain delay is required when the light interactive message is generated on the server side and transferred to the first client. On the other hand, when the first client assembles and displays the light interactive message by itself, the delay may be ignored.

[0087] Considering that the profile picture of the second user account may be at any position in the chat message list, the profile picture of the second user account tapped by the first user may be at the middle position in the chat message list, in this case, further includes the following steps:

[0088] In response to the display content in the first chat window interface not including the latest message content, the first chat window interface is automatically scrolled to the latest message content, and the latest message content includes the message content of the light interactive message. For example, in response to the display content in the first chat window interface not including the latest message content in the chat message list, the chat message list is automatically scrolled to the latest message content in the first chat window so that the first chat window interface displays the latest message content including the message content of the light interactive message. As shown in FIG. 11A, when the first user double-tap the profile picture of the second user account corresponding to the chat message 2 on the first chat window interface 90, the first client displays the profile picture of the second user account as the jittering video 22-11. However, since the chat message 2 is located at the top of the chat message list, the message content at the bottom of the chat message list cannot be displayed when the chat message 2 is displayed on the first chat window interface 90. In this case, the first chat window interface 90 automatically scrolls to the latest message content in the first chat window interface, which includes a light interactive message that "I" tapped "User Account 2" on the thigh, thereby allowing the first user to know in a timely manner that the light interactive message has been successfully triggered, and avoiding the waste of computational and network resources caused by the user repeatedly double-tapping the profile picture 22 of the second user account in succession without receiving the feedback.As shown in FIG. 11B, the first client displays the profile picture of the second user account as a jittering video 22-11, and then automatically scrolls the chat message list to the position of the most recent message content in the first chat window interface, so that the most recent message content is displayed on the first chat window interface 90, and the most recent message content includes a light interactive message 30-11 indicating that “I” lightly tapped “User Account 2” on the thigh.

[0089] Illustratively, chat messages are arranged in a timeline, so that the most recent message content is displayed in a bottom display area of ​​the first chat window interface.

[0090] In step 1004, the first client sends an interactive message to the second client.

[0091] A first client sends a light interactive message to a second client through a server. Illustratively, the first client sends the light interactive message to the server according to a system message format (or a newly defined message format), and the server verifies that the light interactive message meets a sending condition and then sends the light interactive message to a second user account.

[0092] In some embodiments, in response to the first user interface being a person attribute interface, a contacts interface, a personal chat member display interface (also referred to as a personal chat detail page), a social circle interactive interface, or a first chat window interface, the server sends the light interactive message to the first user account and the second user account (or sends the light interactive message only to the second user account). That is, the server sends the light interactive message to the personal chat window interfaces of the first user account and the second user account. In addition, in response to the first user interface being a first chat window interface in the form of a group chat of three or more people or a group member display interface (also referred to as a group chat detail page), the server sends the light interactive message to each user account in the group (or other user accounts excluding the first user account). That is, the server sends the light interactive message to the group chat window interfaces of the first user account and the second user account.

[0093] Exemplarily, the transmission conditions include conditions for limiting the transmission frequency. The transmission conditions include, but are not limited to, at least one of the following conditions:

[0094] Condition 1: The number of times that a first user account sends a light interactive message to a second user account within time period A is x or less. For example, the number of times that a light interactive message is sent to the same user account within two seconds is one or less.

[0095] Condition 2: The number of times that all user accounts in the same group send light interactive messages within time period B is y or less. For example, the number of times that all user accounts in the same group send light interactive messages within 10 seconds is 30 or less.

[0096] If the light interactive message sent by the first client does not meet the sending condition, the server sends a failure notification to the first client. In general, the failure notification is that "messages using the tap function cannot be sent frequently."

[0097] In step 1005, the second client displays a second chat window interface.

[0098] The second chat window interface displays profile pictures of at least two user accounts, including a first user account and a second user account, where the first user account and the second user account are not necessarily displayed simultaneously in the second chat window interface and may appear in any possible position in the chat message list.

[0099] Illustratively, the second chat window interface is a chat window interface for two-person chat or a chat window interface for a group chat of multiple people. The second chat window interface displays a chat message list sorted according to a timeline.

[0100] The first chat window interface and the second chat window interface are for the same chat session (a two-person chat session or a multi-person group chat session) and appear as interfaces for two clients logged into different user accounts.

[0101] In step 1006, the second client receives the interactive message from the first user account to the second user account.

[0102] The second client receives the light interactive message forwarded by the server. The light interactive message is encapsulated in a message format of a system message. Illustratively, the light interactive message includes a first user account, a second user account, and a light interaction identifier, or the system message includes a first field, a second field, and an action description field. The light interaction identifier is an identifier for indicating that the message type is a light interactive message.

[0103] Exemplarily, the message content of the light interactive message is assembled by the second client, for example, the message content of the light interactive message includes a first field, an action description field, and a second field arranged in order. When the light interactive message includes a first user account and a second user account, the first field is determined by querying a local database based on the first user account, the second field is determined by querying a local database based on the second user account, and the action description field is determined based on at least one of the settings of the server, the settings of the first user account, and the settings of the second user account. The local database stores custom fields that have been pre-edited by the server and each user account (oneself and each friend).

[0104] Since a certain delay is required for the server side to transfer a light interactive message, the second client can shorten the delay as much as possible by constructing and displaying the light interactive message by itself.

[0105] In step 1007, the second client displays the message content of the interactive message in a second chat window interface, where the message display form of the interactive message is different from the message display form of the chat message.

[0106] The second chat window interface includes a chat message list sorted according to a timeline. The second client additionally displays message content of the light interactive message at the bottom of the chat message list in the second chat window interface.

[0107] For example, the message display format of a light interactive message is to display the message content in the form of text without a speech bubble in the background, whereas the message display format of a chat message is to display the message content in the form of text with a speech bubble in the background. That is, light interactive messages are not displayed in the form of speech bubbles, but in the message display format of system messages.

[0108] In some embodiments, the light interactive message is displayed in a first message display form in the second chat window interface in response to the light interactive message being an unread message. Also, the light interactive message is displayed in a second message display form in response to the light interactive message being a read message. The first message display form and the second message display form are different. For example, the action description field in the first message display form is blue, and the first and second fields are gray. Meanwhile, the action description field, the first and second fields in the second message display form are all gray.

[0109] In some embodiments, the chat members of the second chat window interface further include a third user account, and the second client further receives other light interactive messages sent from the chat members to the third user account and displays the other light interactive messages in the second chat window interface. The message display form of the other light interactive messages is different from the message display form of the light interactive messages. For example, the message content of the other light interactive messages is displayed in a non-bold font, and the light interactive messages sent to the second user account are displayed in a bold font.

[0110] In step 1008, the second client displays a profile video of the profile picture of the second user account in a profile picture area that corresponds to the chat message sent from the second user account that is closest to the interactive message.

[0111] The profile video is a video displayed based on the profile picture of the second user account. Exemplarily, the profile video includes at least one of a video in which a jitter is applied to the profile picture of the second user account, a video in which the profile picture of the second user account is rotated, a video in which a filter is applied to the profile picture of the second user account, a video in which another display element (e.g., a person's hand) is superimposed on the profile picture of the second user account, and a video in which the profile picture of the second user account is reduced or enlarged, but is not limited thereto.

[0112] Illustratively, the profile video of the profile picture of the second user account is a video related to an action description in the message content of the light interactive message, such as tapping the profile picture of the second user account or stroking the profile picture of the second user account.

[0113] Because the message content of the light interactive message may have a distance between it and the chat message sent from the second user account, in other words, between it and the profile picture of the second user account, the second client first determines the chat message that is closest to the light interactive message among the chat messages sent from the second user account, and then displays the profile picture of the second user account corresponding to the chat message that is closest in location as a profile video.

[0114] As shown in FIG. 12, of the chat messages 1 and 2 sent from the second user account, the chat message closest to the light interactive message 30-12 is determined to be the preceding chat message 2, and the second client displays the profile picture of the second user account in the preceding chat message 2 of the light interactive message 30-12 as a jittering video 22-12.

[0115] As shown in Fig. 13, among chat messages 1, 2, and 4 sent from the second user account, the chat message closest to the light interactive message 30-13 is determined to be the subsequent chat message 4, and the second client displays the profile picture of the second user account in the chat message 4 after the light interactive message 30-13 as a jittering video 22-13. Illustratively, when the previous chat message 2 and the subsequent chat message 4 have the same distance to the light interactive message 30-13, the previous chat message 2 is preferentially selected. The distance between the two messages is measured by the number of messages between the two messages.

[0116] Note that step 1007 may be performed before step 1008, step 1007 may be performed after step 1008, or step 1007 and step 1008 may be performed simultaneously.

[0117] In addition, in the case of a group chat with multiple users, the other user accounts other than the first user account and the second user account also receive the light interactive message, and the other clients logged in to the other user accounts encapsulate and display the message content of the light interactive message themselves. The other clients may display the jittering video of the profile picture of the second user account, or may not display the jittering video of the profile picture of the second user account.

[0118] The second user account may also be the first user account itself, i.e. the user may send a light interactive message to himself, which triggers the display of a light interactive message saying that "I" tapped myself.

[0119] As described above, the method according to the present embodiment includes sending a light interactive message to a second user account according to a light interactive command triggered on a profile picture of the second user account, and the light interactive message triggers the second client to display the light interactive message and the profile picture of the second user account in a second chat window interface, thereby providing a new interaction method with a light remind function, which is suitable for entertaining interaction in a chat scene with a fun and relaxed atmosphere.

[0120] Since the light interactive message is not a message having a message content customized by the user, but a message simulating the user's behavior, the user can use the light interactive message to convey his / her intention of light interaction in chat scenes in which the user does not want to talk, does not know what to say, or expresses an ambiguous meaning.

[0121] In one embodiment with reference to the above embodiment, at least one of the first field, the action description field, and the second field is a custom field pre-edited by a user.

[0122] In some embodiments, the first field is a custom field, and the first field includes a name of the first user account and at least one of a custom prefix and a custom suffix for the first user account.

[0123] When the light interactive message is displayed in the first user interface, the name of the first user account is replaced with the first person "I" or the second person "you". When the light interactive message is displayed in the second chat window interface, the name of the first user account includes at least one of an annotation name, an in-group alias, and a custom alias. Illustratively, the priority of the annotation name is higher than the priority of the in-group alias, which is higher than the priority of the custom alias. If the annotation name exists, the annotation name is displayed preferentially. If the annotation name does not exist and an in-group alias exists, the in-group alias in this group is displayed preferentially. If the annotation name and the in-group alias do not exist, the custom alias is displayed.

[0124] The custom prefix of the first user account refers to the characters before the name of the first user account, and the custom suffix of the first user account refers to the characters after the name of the first user account. The custom prefix and the custom suffix may be both set or only one may be set. If both the custom prefix and the custom suffix are set, the custom prefix and the custom suffix may appear simultaneously or only one may appear. For example, if the first user account is a sender of a light interactive message, the custom prefix appears, and if the first user account is a recipient of a light interactive message, the custom suffix appears.

[0125] Referring to the above embodiment, Figure 14 shows a flowchart of a first field customization method according to an exemplary embodiment of the present application. The method may be performed by a first client, and includes the following steps:

[0126] In step 1401, a first custom interface is displayed.

[0127] The first custom interface is a user interface for custom setting the first field. With reference to FIG. 15A in general, when the first user taps "Set tap function" on the person attribute page of the first user account on the first client, the first client displays the first custom interface 141 as shown in FIG. 15B. In this embodiment, the case of setting a custom prefix for the first user account will be described as an example.

[0128] In step 1402, a customized portion of a first field is obtained by pre-editing in response to a first pre-edit operation on a first custom interface.

[0129] The first pre-editing operation is an editing operation before sending a light interactive message. The first client edits and saves the customized portion of the first field according to the user's editing operation on the first custom interface 141. In this embodiment, the customized portion of the first field refers to the custom prefix of the first user account. As shown in FIG. 15C, the customized portion of the first field is, for example, "fearless".

[0130] Illustratively, the number of characters in the customized portion of the first field is limited, such as a maximum of eight characters.

[0131] As shown in FIG. 15C, when the first user taps the done button 142, the first client saves the customized portion of the first field and synchronizes the customized portion of the first field with the server and with a second client corresponding to the second user account that is in a friend relationship.

[0132] As described above, the method according to the present embodiment provides a function for customizing the first field, so that the second user cannot predict the first field customized by the first user, thereby improving the fun of light interactive messages and increasing the frequency of interactions between the first user account and the second user account.

[0133] In some embodiments, the second field is a custom field, and the second field includes a name of the second user account and at least one of a custom prefix and a custom suffix for the second user account.

[0134] When the light interactive message is displayed in the second user interface, the name of the second user account is replaced with the first person "I" or the second person "you". When the light interactive message is displayed in the second chat window interface, the name of the second user account includes at least one of an annotation name, an in-group alias, and a custom alias. Illustratively, the priority of the annotation name is higher than the priority of the in-group alias, which is higher than the priority of the custom alias. If the annotation name exists, the annotation name is preferentially displayed. If the annotation name does not exist and an in-group alias exists, the in-group alias in this group is preferentially displayed. If the annotation name and the in-group alias do not exist, the custom alias is displayed.

[0135] The custom prefix of the second user account refers to the characters that precede the name of the second user account, and the custom suffix of the second user account refers to the characters that follow the name of the second user account. The custom prefix and the custom suffix may both be set, or only one may be set. If both the custom prefix and the custom suffix are set, the custom prefix and the custom suffix may appear simultaneously, or only one may appear. For example, if the second user account is a sender of a light interactive message, the custom prefix appears, and if the second user account is a recipient of a light interactive message, the custom suffix appears.

[0136] Referring to the above embodiment, Figure 16 shows a flowchart of a method for customizing a second field according to an exemplary embodiment of the present application. The method may be performed by a second client, and includes the following steps:

[0137] In step 1601, a second custom interface is displayed.

[0138] The second custom interface is a user interface for custom setting the second field. With reference to FIG. 17A in general, when the second user taps "Set tap function" in the person attribute page of the second user account, the second client displays the second custom interface 161 as shown in FIG. 17B. In this embodiment, the case of setting a custom suffix for the second user account is taken as an example for description.

[0139] In step 1602, a customized portion of a second field is obtained by pre-editing in response to a second pre-edit operation on the second custom interface.

[0140] The second pre-editing operation is an editing operation before sending a light interactive message. The second client edits and saves the customized portion of the second field according to the user's editing operation on the second custom interface 161. In this embodiment, the customized portion of the second field refers to the custom prefix of the second user account. As shown in FIG. 17C, the customized portion of the second field is, for example, "shoulder".

[0141] Illustratively, the number of characters in the customized portion of the second field is limited, such as a maximum of eight characters.

[0142] As shown in FIG. 17C, when the second user taps the done button 162, the second client saves the customized portion of the second field and synchronizes the customized portion of the second field with the server and the first client corresponding to the first user account with which the second user is friends.

[0143] As described above, the method according to the present embodiment provides a function for customizing the second field, so that the first user cannot predict the second field customized by the second user, thereby improving the fun of light interactive messages and increasing the frequency of interactions between the first user account and the second user account.

[0144] In some embodiments, the first client and / or the second client further customize the action description field. The first client and / or the second client display a third custom interface and pre-edit the action description field in response to a third pre-edit operation on the third custom interface. Generally, the action description field includes slapping, hugging, kissing, tapping, nudge, etc. Illustratively, the number of characters in the customized portion of the action description field is limited, e.g., a maximum of three characters.

[0145] In one embodiment of the above embodiment, the above method further includes the following step 1009 or step 1010, as shown in FIG.

[0146] In step 1009, the first client displays a person attribute page of the first user account in response to a first trigger instruction on the name of the first user account in the interactive message.

[0147] The light interactive message includes the names of two user accounts, for example, the name of a first account and the name of a second account. When the user taps the name of the first user account in the light interactive message, a first trigger command is triggered on the first client, and the first client displays a person attribute page of the first user account according to the first trigger command. As shown in FIG. 19A and FIG. 19B, when the user taps "you" in the light interactive message 30-19 on the first chat window interface 90, the first client displays a person attribute page 910. As shown in FIG. 19B, the person attribute page 910 of the first user account displays at least one information of the name, account, profile picture, signature, gender, phone, QR code, album, and personal space of the first user account.

[0148] In step 1010, the first client displays a person attribute page of the second user account in response to a second trigger instruction on the name of the second user account in the interactive message.

[0149] Similarly, when a user taps on the name of a second user account in the light interactive message, a second trigger instruction is triggered on the first client, and the first client displays a person attribute page of the second user account in accordance with the second trigger instruction.

[0150] Illustratively, for any client, when a light interactive message sent by oneself or another person is displayed in the chat window interface of that client, the client displays the person attribute page of that user account in response to a trigger command on the name of the user account in the light interactive message.

[0151] As described above, in the method of this embodiment, the client displays the person attribute page of the user account in response to a trigger command on the name of the user account in a light interactive message, thereby providing a man-machine interaction method for quickly browsing the person attribute page of the user account in the chat window interface, and improving the efficiency of man-machine interaction.

[0152] In one embodiment of the above embodiment, the above method further includes the following step 1011, as shown in FIG.

[0153] In step 1011, if there are n consecutive interactive messages, the n interactive messages are displayed in a folded state.

[0154] For any client, when there are n consecutive light interactive messages in the chat window interface of the client, all or part of the n light interactive messages can be collapsed and displayed according to a folding policy. Folding is also called hiding or non-display. By collapsing and displaying multiple consecutive light interactive messages, the appearance of unnecessary light interactive messages can be reduced and corresponding computation resources can be saved.

[0155] Illustratively, the folding policy includes at least one of a read folding policy or a suspended folding policy.

[0156] 1. Read collapsing policy In response to n consecutive light interactive messages being present in the first chat window interface and all of the n light interactive messages being in a read state, the first client collapses and displays all or a part of the n light interactive messages, where n is an integer greater than 1. Similarly, in response to n consecutive light interactive messages being present in the second chat window interface and all of the n light interactive messages being in a read state, the second client collapses and displays all or a part of the n light interactive messages, where n is an integer greater than 1.

[0157] As shown in Fig. 21, when there are five consecutive light interactive messages 32 in a read state in the first chat window interface 210, the first client collapses and displays the last two light interactive messages of the five light interactive messages 32 (displays the first three of the five consecutive light interactive messages that have been read, and does not display the last two). An "expand all" button is displayed on the two collapsed light interactive messages (i.e., after the third light interactive message), and when the user taps the "expand all" button, the display of the two light interactive messages can be restored.

[0158] However, for five consecutive light interactive messages 34, if the first four light interactive messages are in a read state and the last light interactive message is in an unread state, folding of the five light interactive messages is refrained from.

[0159] Second, the suspension and folding policy In response to m consecutive light interactive messages being present in the first chat window interface and all of the m light interactive messages being earlier than the latest chat message, the first client collapses and displays all or a part of the m light interactive messages, where m is an integer greater than 1. Similarly, in response to m consecutive light interactive messages being present in the second chat window interface and all of the m light interactive messages being earlier than the latest chat message, the second client collapses and displays all or a part of the m light interactive messages, where m is an integer greater than 1.

[0160] As shown in FIG. 22, when a series of multiple light interactive messages 36 (more than five) are interrupted in the first chat window interface 220, the first three light interactive messages are displayed while the remaining light interactive messages are collapsed and displayed. The collapsed multiple light interactive messages (after the third light interactive message) have an "expand all" button displayed, and when the user taps the "expand all" button, the display of the multiple light interactive messages can be restored. The multiple light interactive messages 36 are interrupted by a system message indicating that "Passerby B invites Passerby C to a group chat", and the multiple light interactive messages 38 are not interrupted, so the folding of the multiple light interactive messages 38 is refrained from.

[0161] The folding policy may optionally include the following properties:

[0162] If one or two light interactive messages are interrupted by another chat message or another system message (collectively referred to as another message of a different type from the light interactive message), the consecutive count is restarted from the first light interactive message following the other message.

[0163] 2. If there are time division stamps (e.g. 13:20) between two light interactive messages, the consecutive count between the two light interactive messages will not be affected by the time division stamps, and these time division stamps will be ignored when redeploying and displaying.

[0164] 3. Storing consecutive light interactive messages that are not interrupted by other messages in the same database (DB) message. The database is a database for storing messages in a client. There are multiple sub-messages in the same DB message, and each sub-message is used to store one light interactive message. After storing one light interactive message using a DB message, if the client receives another light interactive message and is not interrupted by another message, the other light interactive message is stored in the DB message content by updating the message content. On the other hand, if the client receives another light interactive message and is interrupted by another message, a new DB message is created to store the other light interactive message.Therefore, according to an embodiment of the present application, the message sending method further includes the steps of: creating a database message for storing the interactive message according to the interactive message being the first interactive message in the first chat window interface; and for each new interactive message following the interactive message in the first chat window interface, storing the new interactive message in the database message in which the previous interactive message exists by updating the database message in which the previous interactive message exists according to the absence of a non-interactive message between the new interactive message and the previous interactive message, while creating a new database message for storing the new interactive message according to the presence of a non-interactive message between the new interactive message and the previous interactive message, where the interactive message is a light interactive message and the non-interactive message is a non-light interactive message. When displaying at least one interactive message, the client or terminal renders the at least one interactive message by dividing the database message in which the at least one interactive message exists, and displays it on the first chat window interface. In this way, it can contribute to realizing the folding operation and rendering a plurality of consecutive light interactive messages when unfolding or folding by the client or computer device.

[0165] 4. The read state of the light interactive message may be updated according to the user's swipe state on the client, and may be updated according to whether the profile video of the second user account is displayed. In one example, after the profile video of the second user account is displayed on the client of the message recipient, the state of the light interactive message is set to read. In another example, when the display position of the light interactive message is 20% or less of the interface from top to bottom on the screen and the profile video of the second user account is displayed, the state of the light interactive message is set to read. Its role is to (1) ensure that the user has indeed read it, and (2) ensure that the profile picture of the person who was hit is present within approximately half the screen in front of the light interactive message as much as possible, so that it is not overlooked when the profile video of the person who was hit is displayed, especially in the case of a scene where the user swipes to browse the context.

[0166] FIG. 23 illustrates a block diagram of a message sending device according to an exemplary embodiment of the present application. The device is logged into a first user account, and the device: a display module 2320 for displaying a profile picture of the second user account on the first user interface; a generating module 2340 that generates an interactive message based on a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account in response to an interactive command triggered on a profile picture of the second user account; and a sending module 2360 for sending the interactive message to a second client logged into the second user account.

[0167] In one exemplary design of the present application, at least one of the first field, the action description field, and the second field is a custom field pre-edited for the interactive message.

[0168] In one exemplary design of the present application, in response to the first field being the custom field, the first field includes a name of the first user account and at least one of a custom prefix and a custom suffix of the first user account, and in response to the second field being the custom field, the second field includes a name of the second user account and at least one of a custom prefix and a custom suffix of the second user account.

[0169] In one exemplary design of the present application, the apparatus further includes an editing module, wherein the display module 2320 displays a first custom interface, and the editing module obtains a customized portion of the first field by pre-editing in response to a first pre-editing operation on the first custom interface.

[0170] In one exemplary design of the present application, the display module 2320 displays a third custom interface, and the editing module obtains a customized portion of the action description field by pre-editing in response to a third pre-editing operation on the third custom interface.

[0171] In one exemplary design of the present application, the generating module 2340 generates the interactive message in response to a double-tap instruction triggered on a profile picture of the second user account.

[0172] In one exemplary design of the present application, the first user interface is a non-chat window interface, and the non-chat window interface includes at least one of a person attribute interface, a contacts interface, a group member display interface, a person-to-person chat member display interface, and a social circle interactive interface.

[0173] The display module 2320 further displays the interactive message in a region of interest in the non-chat window interface relative to a profile picture of the second user account.

[0174] In one exemplary design of the present application, the display module 2320 further cancels display of the interactive message in the non-chat window interface in response to a display time of the interactive message reaching a threshold.

[0175] In one exemplary design of the present application, the first user interface is a first chat window interface, and the display module 2320 further displays a message content of the interactive message in the first chat window interface, and a message display form of the interactive message is different from a message display form of a chat message.

[0176] In one exemplary design of the present application, the display module 2320 further, in response to the content displayed in the first chat window interface not including the latest message content, automatically scrolls the first chat window interface to the latest message content and displays the latest message content, where the latest message content includes the message content of the interactive message.

[0177] In one exemplary design of the present application, the display module 2320 further displays all or part of the n interactive messages in a collapsed manner according to the existence of n consecutive interactive messages (n is an integer greater than 1) in the first chat window interface and all of the n interactive messages have been read, or displays all or part of the m interactive messages in a collapsed manner according to the existence of m consecutive interactive messages (m is an integer greater than 1) in the first chat window interface and all of the m interactive messages are earlier than the latest chat message.

[0178] FIG. 24 illustrates a block diagram of a message receiving device according to an exemplary embodiment of the present application. The device is logged into a second user account, and the device: A display module 2420 for displaying a second chat window interface, where chat members in the second chat window interface include a first user account and the second user account; a receiving module 2440 for receiving an interactive message sent from the first user account to the second user account, the message content of the interactive message including a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account; Equipped with The display module 2420 displays the interactive message in the second chat window interface.

[0179] In one exemplary design of the present application, at least one of the first field, the action description field, and the second field is a custom field pre-edited for the interactive message.

[0180] In one exemplary design of the present application, in response to the first field being the custom field, the first field includes a name of the first user account and at least one of a custom prefix and a custom suffix of the first user account, and in response to the second field being the custom field, the second field includes a name of the second user account and at least one of a custom prefix and a custom suffix of the second user account.

[0181] In one exemplary design of the present application, the apparatus further includes an editing module, wherein the display module 2420 further displays a second custom interface, and the editing module obtains a customized portion of the second field by pre-editing in response to a second pre-editing operation on the second custom interface.

[0182] In one exemplary design of the present application, the display module 2420 further displays a message content of the interactive message in the second chat window interface, and a message display form of the interactive message is different from a message display form of a chat message.

[0183] In one exemplary design of the present application, the display module 2420 further displays the interactive message in the second chat window interface in a first message display form in response to the interactive message being an unread message, and displays the interactive message in the second chat window interface in a second message display form in response to the interactive message being a read message; The first message display form and the second message display form are different.

[0184] In one exemplary design of the present application, the chat members of the second chat window interface further include a third user account, the receiving module 2440 further receives other interactive messages sent from the chat members to the third user account, and the display module 2420 further displays the other interactive messages in the second chat window interface, and the message display form of the other interactive messages is different from the message display form of the interactive message.

[0185] In one exemplary design of the present application, the display module 2420 further displays a profile video of the profile picture of the second user account in a profile picture area corresponding to the chat message sent from the second user account that is closest to the interactive message.

[0186] In one exemplary design of the present application, the display module 2420 further collapses and displays all or part of the n interactive messages according to the existence of n consecutive interactive messages in the second chat window interface and all of the n interactive messages being in a read state, or the display module 2420 further collapses and displays all or part of the m interactive messages according to the existence of m consecutive interactive messages in the second chat window interface and all of the m interactive messages being earlier than the latest chat message.

[0187] In addition, the message transmission device according to the above embodiment will be described by taking only the division of each of the above functional modules as an example, but in actual application, the above functions may be assigned to different functional modules to be completed as necessary, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above-described functions. In addition, the message transmission device according to the above embodiment is based on the same idea as the embodiment of the message transmission method, and the specific realization process may be referred to in detail in the embodiment of the method, but the details will be omitted here.

[0188] Similarly, the message receiving device according to the above embodiment is described by taking only the division of each of the above functional modules as an example, but in actual application, the above functions may be assigned to different functional modules to be completed as necessary, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above-described functions. Also, the message receiving device according to the above embodiment is based on the same idea as the embodiment of the message receiving method, and the specific implementation process may be referred to in detail in the embodiment of the method, but the details will be omitted here.

[0189] The present application further provides a computer device (terminal or server), comprising a processor and a memory storing at least one instruction that is loaded and executed by the processor to realize the message sending method or the message receiving method according to the embodiments of the above methods. Note that the computer device may be a computer device as shown in FIG. 25 below.

[0190] 25 illustrates a structural block diagram of a computing device 2500 according to an exemplary embodiment of the present application. The computing device 2500 may be a smartphone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III), an MP4 player (Moving Picture Experts Group Audio Layer IV), a notebook computer, or a desktop computer. The computing device 2500 may also be referred to as a user device, a portable computing device, a laptop computing device, a desktop computing device, etc.

[0191] Generally, the computing device 2500 comprises a processor 2501 and a memory 2502 .

[0192] The memory 2502 may include one or more computer readable storage media, which may be non-transitory. The memory 2502 may further include high speed random access memory and non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, etc. In some embodiments, the non-transitory computer readable storage media in the memory 2502 stores at least one instruction executed by the processor 2501 to implement a message transmission method according to a method embodiment of the present application.

[0193] In some embodiments, the computing device 2500 may optionally further include a peripheral interface 2503 and at least one peripheral device. The processor 2501, the memory 2502, and the peripheral interface 2503 may be connected via a bus or signal lines. Each peripheral device may be connected to the peripheral interface 2503 via a bus, signal lines, or a circuit board. Specifically, the peripheral device includes at least one of a radio frequency circuit 2504, a touch display panel 2505, a camera component 2506, an audio circuit 2507, a positioning component 2508, and a power source 2509.

[0194] The peripheral interface 2503 may be used to connect at least one peripheral device associated with I / O (Input / Output) to the processor 2501 and the memory 2502. In some embodiments, the processor 2501, the memory 2502, and the peripheral interface 2503 are integrated on the same chip or circuit board. In other embodiments, any one or two of the processor 2501, the memory 2502, and the peripheral interface 2503 may be implemented on separate chips or circuit boards, and this embodiment is not limited thereto.

[0195] The display panel 2505 displays a user interface (UI). The UI may include graphics, text, icons, videos, and any combination thereof. If the display panel 2505 is a touch display panel, the display panel 2505 is further capable of collecting touch signals on or above the surface of the display panel 2505. The touch signals may be input as control signals to the processor 2501 for processing. In this case, the display panel 2505 may also be used to provide virtual buttons and / or a virtual keyboard, also called soft buttons and / or a soft keyboard.

[0196] In some embodiments, the computing device 2500 further comprises one or more sensors 2510, including, but not limited to, an acceleration sensor 2511, a gyro sensor 2512, a pressure sensor 2513, a fingerprint sensor 2514, an optical sensor 2515, and a proximity sensor 2525.

[0197] Those skilled in the art will appreciate that computing device 2500 is not limited to the structure shown in FIG. 25 and may include more or fewer components than those shown, may combine some components, or may be configured using different components.

[0198] The memory further includes one or more programs, the one or more programs being stored in the memory, and the one or more programs include those for executing a message sending method or a message receiving method related to an embodiment of the present application.

[0199] The present application further provides a computer-readable storage medium having stored therein at least one instruction that is loaded and executed by the processor to realize a message sending method or a message receiving method relating to an embodiment of each of the above methods.

[0200] The present application further provides a computer program product, which, when executed on a computer, causes the computer to perform the message sending method or the message receiving method according to each of the method embodiments described above.

[0201] The numbers of the above-mentioned embodiments of the present application are merely for the purpose of explanation and do not indicate superiority or inferiority of the embodiments.

[0202] It will be understood by those skilled in the art that all or part of the steps in the above-mentioned embodiments may be completed by hardware, or may be completed in related hardware by a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disk, etc.

Claims

1. 1. A method of sending a message executed by a first client logged into a first user account, the method comprising: displaying a profile picture of the second user account on the first user interface; generating an interactive message in response to an interactive instruction triggered on a profile picture of the second user account, the interactive message being a message different from a chat message; sending the interactive message to a second client logged into the second user account; The method according to claim 1, further comprising:

2. The interactive message is generated based on a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account, and at least one of the first field, the action description field, and the second field is a custom field pre-edited for the interactive message.

2. The method of claim 1 .

3. In response to the first field being the custom field, the first field includes a name of the first user account and at least one of a custom prefix and a custom suffix of the first user account; In response to the second field being the custom field, the second field includes a name of the second user account and at least one of a custom prefix and a custom suffix of the second user account.

3. The method of claim 2 .

4. The method comprises: displaying a first custom interface; and obtaining a customized portion in the first field by pre-editing in response to a first pre-editing operation on the first custom interface.

4. The method according to claim 2 or 3.

5. The method comprises: displaying a third custom interface; obtaining a customized portion in the action description field by pre-editing in response to a third pre-editing operation on the third custom interface.

4. The method according to claim 2 or 3.

6. The step of generating the interactive message in response to an interactive instruction triggered on a profile picture of the second user account comprises: generating the interactive message in response to a double tap command triggered on a profile picture of the second user account. The method according to any one of claims 1 to 4.

7. The first user interface is a non-chat window interface, the non-chat window interface including at least one of a person attribute interface, a contacts interface, a group member display interface, a person-to-person chat member display interface, and a social circle interactive interface; The method comprises: displaying the interactive message in a region of interest in the non-chat window interface relative to a profile picture of the second user account; The method according to any one of claims 1 to 3.

8. The method comprises: canceling display of the interactive message in the non-chat window interface in response to a display time of the interactive message reaching a threshold.

8. The method of claim 7.

9. The first user interface is a first chat window interface; The method comprises: displaying message content of the interactive message in the first chat window interface, wherein a message display form of the interactive message is different from a message display form of a chat message; The method according to any one of claims 1 to 4.

10. The step of displaying message content of the interactive message in the first chat window interface comprises: automatically scrolling the chat message list to the latest message content in the first chat window interface and displaying the latest message content in the first chat window interface in response to the content displayed in the first chat window interface not including the latest message content in a chat message list, wherein the latest message content includes the message content of the interactive message; 10. The method of claim 9.

11. The method comprises: When there are n consecutive interactive messages (n is an integer greater than 1) in the first chat window interface and all of the n interactive messages have been read, display all or part of the n interactive messages in a collapsed state; Or, The method further includes a step of displaying all or a part of m consecutive interactive messages (m being an integer greater than 1) in the first chat window interface in a collapsed manner according to the existence of the m consecutive interactive messages in the first chat window interface and the m interactive messages all being earlier than a latest chat message.

11. The method of claim 10.

12. The method of claim 11, wherein the first user interface is a first chat window interface; The method comprises: creating a database message for storing the interactive message in response to the interactive message being an initial interactive message in the first chat window interface, the database message being used to store messages in a database at the first client; for each new interactive message following the interactive message in the first chat window interface, in response to there being no non-interactive messages between the new interactive message and the previous interactive message, storing the new interactive message in the database message in which the previous interactive message exists by updating the database message in which the previous interactive message exists, while in response to there being non-interactive messages between the new interactive message and the previous interactive message, creating a new database message for storing the new interactive message; and rendering the at least one interactive message by splitting a database message in which the at least one interactive message exists, and displaying the at least one interactive message on the first chat window interface.

2. The method of claim 1 .

13. The interactive message is for triggering the second client to display a jittering video of the profile picture of the second user account in a second chat window interface.

2. The method of claim 1 .

14. A method for receiving a message executed by a second client logged into a second user account, comprising: displaying a second chat window interface, where chat members in the second chat window interface include a first user account and the second user account; receiving an interactive message sent from the first user account to the second user account, the interactive message being generated in response to an interactive instruction triggered on a profile picture of the second user account displayed on a first user interface on a first client to which the first user account is logged in; displaying the interactive message in the second chat window interface, wherein a message content of the interactive message is displayed in a display format different from a message display format of a chat message; The method according to claim 1, further comprising:

15. A message content of the interactive message includes a first field corresponding to the first user account, an action description field indicating that the first user account performs an action on the second user account, and a second field corresponding to the second user account, and at least one of the first field, the action description field, and the second field is a custom field pre-edited for the interactive message.

15. The method of claim 14.

16. In response to the first field being the custom field, the first field includes a name of the first user account and at least one of a custom prefix and a custom suffix of the first user account; In response to the second field being the custom field, the second field includes a name of the second user account and at least one of a custom prefix and a custom suffix of the second user account.

16. The method of claim 15 .

17. The method comprises: displaying a second custom interface; and pre-editing the second field in response to a second pre-edit operation on the second custom interface.

17. The method according to claim 15 or 16.

18. The step of displaying the interactive message in the second chat window interface includes: displaying the interactive message in a first message display format in the second chat window interface in response to the interactive message being an unread message; If the interactive message is a read message, displaying the interactive message in a second message display format in the second chat window interface; The first message display form and the second message display form are different.

17. The method of claim 16.

19. The chat members of the second chat window interface further include a third user account; The method comprises: receiving another interactive message sent from the chat member to the third user account, and displaying the other interactive message in the second chat window interface, wherein a message display form of the other interactive message is different from a message display form of the interactive message; 15. The method of claim 14.

20. The method comprises: displaying a profile video of a profile picture of the second user account in a profile picture area corresponding to a chat message sent from the second user account that is closest to the interactive message; 17. The method according to any one of claims 14 to 16.

21. The profile picture is a jittering video.

15. The method of claim 14.

22. The method comprising: When there are n consecutive interactive messages in the second chat window interface and all of the n interactive messages have been read, displaying all or a part of the n interactive messages in a collapsed state; Or, The method further includes a step of displaying all or a part of the m interactive messages in a collapsed state according to the existence of m consecutive interactive messages in the second chat window interface and all of the m interactive messages being earlier than a latest chat message.

21. The method of claim 20.

23. A message sending device logged into a first user account, comprising: a display module for displaying a profile picture of the second user account on the first user interface; a generation module that generates an interactive message in response to an interactive command triggered on a profile picture of the second user account, the interactive message being a message different from a chat message and including custom fields previously edited by a user for the interactive message; a sending module for sending the interactive message to a second client logged into the second user account; A message sending device comprising:

24. A message receiving device logged into a second user account, comprising: a display module for displaying a second chat window interface, where chat members in the second chat window interface include a first user account and the second user account; a receiving module for receiving an interactive message sent from the first user account to the second user account, the interactive message being generated in response to an interactive instruction triggered on a profile picture of the second user account displayed on a first user interface on a first client to which the first user account is logged in; Equipped with The display module displays the interactive message in the second chat window interface, and a message content of the interactive message is displayed in a display format different from a message display format of a chat message.

25. A processor; a memory in which at least one instruction, at least one program, code set or instruction set is stored, which is loaded and executed by the processor so as to implement the message sending method according to any one of claims 1 to 13 or the message receiving method according to any one of claims 14 to 22; A computer device comprising:

26. A computer program configured to cause a computer to execute the message sending method described in any one of claims 1 to 13, or the message receiving method described in any one of claims 14 to 22.

Images