Message display method and device, terminal equipment and storage medium

Abstract

This application discloses a message display method, apparatus, terminal, and storage medium. The method includes: displaying a target type session message identifier on a first message receiving interface corresponding to a first identity account, indicating that a target contact in a second identity account is sending a target session message to a target user; when the target type session message identifier is selected, displaying a second message receiving interface corresponding to the second identity account, and displaying a session window identifier indicating that the second identity account and the target contact are having a session on the second message receiving interface; when the session window identifier is triggered, displaying a session window indicating that the target user under the second identity account is having a session with the target contact, and displaying the target session message in the session window. This method distinguishes the session messages received by the first identity account and the second identity account by using the target type session message identifier, which can improve the efficient management of messages from multiple identity accounts.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a message display method, apparatus, terminal device, and storage medium. Background Technology

[0002] As is well known, many social applications only allow one user to have one identity within one account. If a user wants to have two identities, they need to apply for a new account to represent the second identity. That is, the first account corresponds to the first identity, and the second account corresponds to the second identity, and both accounts and identities exist independently. When using the application, a user can only log in to one account at a time. If they want to log in to another account, the previous account must be logged out first. In this case, the process of creating a new account is relatively complicated and inconvenient to manage. When logging into the first account, the information of the second account cannot be viewed in a timely manner, and frequent switching between the two accounts may also lead to information loss. Therefore, how to improve the efficient management of messages from multiple identity accounts while satisfying user experience has become an urgent technical problem to be solved. Summary of the Invention

[0003] This invention provides a message display method, apparatus, terminal device, and storage medium, which can improve the efficient management of session messages in multiple identity accounts.

[0004] On one hand, embodiments of the present invention disclose a message display method, the method comprising:

[0005] The first message receiving interface corresponding to the first identity account is displayed. The first message receiving interface includes a target type session message identifier. The target type session message identifier is used to indicate that there is a target contact in the second identity account to send a target session message to the target user. The target contact is a contact under the second identity account. The first identity account is a user account applied for by the target user in the social application with a first identity. The second identity account is a user account applied for by the target user in the social application with a second identity.

[0006] When the target type session message identifier is selected, the second message receiving interface corresponding to the second identity account is displayed, and the session window identifier of the conversation between the target user under the second identity account and the target contact is displayed on the second message receiving interface.

[0007] When the session window identifier is triggered, a session window is displayed showing the conversation between the target user and the target contact under the second identity account, and the target session message is displayed in the session window.

[0008] On one hand, embodiments of the present invention disclose a message display device, the device comprising:

[0009] The display unit is used to display the first message receiving interface corresponding to the first identity account. The first message receiving interface includes a target type session message identifier. The target type session message identifier is used to indicate that there is a target contact in the second identity account sending a target session message to the target user. The target contact is a contact under the second identity account. The first identity account is a user account applied for by the target user in the social application with a first identity. The second identity account is a user account applied for by the target user in the social application with a second identity.

[0010] The display unit is also configured to display the second message receiving interface corresponding to the second identity account when the target type session message identifier is selected, and to display the session window identifier of the conversation between the target user under the second identity account and the target contact in the second message receiving interface;

[0011] The display unit is further configured to display a conversation window between the target user and the target contact under the second identity account when the conversation window identifier is triggered, and to display the target conversation message in the conversation window.

[0012] On one hand, embodiments of the present invention disclose a terminal device, including:

[0013] A processor adapted to implement one or more computer programs; and a computer storage medium storing one or more computer programs adapted to be loaded by the processor and executed by the above-described message display method.

[0014] On one hand, embodiments of the present invention disclose a computer-readable storage medium, characterized in that the computer-readable storage medium stores one or more computer programs, the computer programs being adapted to be loaded by a processor and executed by the above-described message display method.

[0015] On one hand, embodiments of the present invention disclose a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform the aforementioned message display method.

[0016] In this embodiment of the invention, on the first message receiving interface corresponding to the first identity account, a target type session message identifier is displayed, indicating that a target contact in the second identity account has sent a target session message to a target user. When the target type session message identifier is selected, the second message receiving interface corresponding to the second identity account is displayed, and a session window identifier indicating that the target user under the second identity account is having a session with the target contact is displayed on the second message receiving interface. Furthermore, when the session window identifier is triggered, a session window indicating that the target user under the second identity account is having a session with the target contact is displayed, and the target session message is displayed in the session window. This method uses the target type session message identifier to indicate that the second identity account has received a session message, so that the user can directly view the session message under the second identity account by triggering the target type session message identifier, without having to frequently switch between logging into the first identity account and the second identity account, thus achieving efficient management of session messages in multiple identity accounts. Attached Figure Description

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

[0018] Figure 1 This is a schematic diagram of the architecture of a message display system disclosed in an embodiment of the present invention;

[0019] Figure 2 This is a flowchart illustrating a message display method disclosed in an embodiment of the present invention;

[0020] Figure 3 This is a schematic diagram of a first message receiving interface disclosed in an embodiment of the present invention;

[0021] Figure 4a This is a schematic diagram of another first message receiving interface disclosed in an embodiment of the present invention;

[0022] Figure 4b This is a schematic diagram of another first message receiving interface disclosed in an embodiment of the present invention;

[0023] Figure 5 This is a schematic diagram of a second message receiving interface disclosed in an embodiment of the present invention;

[0024] Figure 6 This is a schematic diagram of a conversation window interface disclosed in an embodiment of the present invention;

[0025] Figure 7This is a schematic diagram of the interface flow of a message display method disclosed in an embodiment of the present invention;

[0026] Figure 8 This is a schematic diagram of an intelligent conversation message disclosed in an embodiment of the present invention;

[0027] Figure 9 This is a flowchart illustrating another message display method disclosed in an embodiment of the present invention;

[0028] Figure 10a This is a schematic diagram of an identity account management interface disclosed in an embodiment of the present invention;

[0029] Figure 10b This is a flowchart illustrating a display of an identity and account management interface as disclosed in an embodiment of the present invention;

[0030] Figure 11 This is a schematic diagram of an interface for an account status setting option disclosed in an embodiment of the present invention;

[0031] Figure 12 This is a schematic diagram of the interface process for creating a second identity account, as disclosed in an embodiment of the present invention;

[0032] Figure 13 This is a schematic diagram of another interface process for creating a second identity account, as disclosed in an embodiment of the present invention;

[0033] Figure 14 This is a schematic diagram showing the image identifier of a second identity account disclosed in an embodiment of the present invention;

[0034] Figure 15a This is a schematic diagram of the settings interface for a second identity account disclosed in an embodiment of the present invention;

[0035] Figure 15b This is a schematic diagram of a process for opening a settings interface disclosed in an embodiment of the present invention;

[0036] Figure 15c This is a schematic diagram illustrating the creation of a new identity account as disclosed in an embodiment of the present invention;

[0037] Figure 16a This is a schematic diagram of an interface process for adding a contact disclosed in an embodiment of the present invention;

[0038] Figure 16b This is a schematic diagram of a process for adding a contact disclosed in an embodiment of the present invention;

[0039] Figure 17 This is a schematic diagram of an interface for displaying a contact group list disclosed in an embodiment of the present invention;

[0040] Figure 18This is a schematic diagram of the interface of a contact grouping list disclosed in an embodiment of the present invention;

[0041] Figure 19 This is a schematic diagram of a first notification message disclosed in an embodiment of the present invention;

[0042] Figure 20a This is a schematic diagram of displaying a second prompt message according to an embodiment of the present invention;

[0043] Figure 20b This is a schematic diagram of a process for initiating a session through an application, as disclosed in an embodiment of the present invention;

[0044] Figure 21 This is a schematic diagram of a second account identification information disclosed in an embodiment of the present invention;

[0045] Figure 22 This is a schematic diagram of a quick reply method disclosed in an embodiment of the present invention;

[0046] Figure 23a This is a schematic diagram of a third notification message disclosed in an embodiment of the present invention;

[0047] Figure 23b This is a schematic diagram of the process of opening a chat window as disclosed in an embodiment of the present invention;

[0048] Figure 24 This is a schematic diagram of a fourth notification message disclosed in an embodiment of the present invention;

[0049] Figure 25a This is a schematic diagram of user information for a second identity account disclosed in an embodiment of the present invention;

[0050] Figure 25b This is a schematic diagram of a process for obtaining user information disclosed in an embodiment of the present invention;

[0051] Figure 26 This is a schematic diagram of the structure of a message display device disclosed in an embodiment of the present invention;

[0052] Figure 27 This is a schematic diagram of the structure of a terminal device disclosed in an embodiment of the present invention. Detailed Implementation

[0053] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0054] This invention provides a message display scheme where a single user can register two identity accounts within the same social application. Users can use different identities to communicate with different friends. For example, a user can register a regular user account and an enterprise user account within the social application. The user can choose to use the regular user account to communicate with regular friends and the enterprise user account to communicate with enterprise friends. In this invention, regardless of which identity account the user is currently logged into the social application with, they can receive conversation messages from both identity accounts and view and reply to conversation messages from either identity account. Assuming the user uses a primary identity and a secondary identity in the social application, the primary identity account can be considered the main account, and the secondary identity account can be considered the secondary account. Messages received by the primary account are directly displayed in the message receiving interface, while messages received by the secondary account are all grouped into a message node. This message node can be represented as a target type conversation message identifier in the message receiving interface. The user can trigger this target type conversation message identifier to view and reply to conversation messages received under the secondary identity account.

[0055] Currently, creating multiple identities for a single account generally falls into two categories. One is creating a completely new account to represent a new identity, such as WeChat, where only one identity is allowed per user per account; a second identity requires a newly created WeChat account. The other is using sub-accounts, such as WhatsApp, where logging into a sub-account logs out the parent account. In both methods, each identity can only receive conversation messages from that specific identity. To view conversation messages from another identity, the user must log out of the current account and log back in. This is not only cumbersome but also prone to delayed message responses. Compared to existing technologies, this invention allows a single account to receive messages from two identities, distinguishing between the first and second identity messages using a target type conversation message identifier. This method effectively improves user management of conversation messages across multiple identity accounts. Displaying conversation messages from different identities in different conversation windows protects user privacy and improves management efficiency.

[0056] Based on the above message display scheme, this embodiment of the invention provides a message display system. Please refer to... Figure 1This is a schematic diagram of the architecture of a message display system disclosed in an embodiment of the present invention. The message display system 10 may include a terminal device 101, a terminal device 102 and a server 103. The terminal device 101, the terminal device 102 and the server 103 can be connected to each other. The terminal device 101 may be a terminal used by the target user and the terminal device 102 may be a terminal used by the target contact.

[0057] In one embodiment, both terminal device 101 and terminal device 102 can be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, smart vehicles, etc., but are not limited to these; server 103 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0058] In one embodiment, terminal devices 101 and 102 can run social applications. Social applications are software that enables communication between people over a network; that is, any application that allows communication between people can be called a social application. Social applications can include instant messaging applications such as QQ, WeChat Work, Facebook, WhatsApp, and WeChat, as well as non-instant messaging applications such as SMS, microblogging, and various short video applications. Server 103 can provide support for the operation of social applications in terminal devices 101 and 102.

[0059] Any user can log in and register multiple identities in a social application through their terminal device. Multiple identities can include a regular user identity within a social application, as well as an enterprise user identity, a teacher identity, and so on. Taking a target user using terminal device 101 as an example, assuming the target user has already registered a first identity account as a regular user in a social application, and then wants to register a new identity account different from the regular one, the target user's terminal device 101 will send an identity account creation request to server 103. Upon receiving the creation request, server 103 will assign a new identity account (the second identity account) to the target user based on the identity account type of the requested new identity account. Then, the server will return some information related to this new identity account to terminal device 101. Terminal device 101 will then display relevant information about the second identity account based on the information returned by the server, such as service duration settings and smart reply message settings.

[0060] As mentioned above, both the first identity account and the second identity account belong to the target user. The target user can add some contacts from the first identity account to the second identity account. Contacts under the second identity account can initiate conversations with the target user under the second identity account. In this embodiment of the invention, conversation messages received using either the first or second identity account will be displayed on the message receiving interface of the currently logged-in identity account. For example, if the target user logs into a social application using the first identity account, and a contact under the first identity account sends conversation message 1 to the target user under the first identity account, and a contact under the second identity account sends conversation message 2 to the target user under the second identity account, then conversation message 1 and conversation message 2 will be displayed on the first message receiving interface of the social application. However, the display methods of conversation message 1 and conversation message 2 can be different. The display method of conversation message 1 is: directly display the conversation window identifier of the contact who sent conversation message 1 and the target user in the first identity account, as well as conversation message 1; while the display method of conversation message 2 can be: display a target type conversation message identifier, and when the target type conversation message identifier is triggered, display the second message receiving interface under the second identity account, and display the conversation window identifier of the contact who sent conversation message 2 and the target user, as well as conversation message 2, in the second message receiving interface.

[0061] Using this method, when the target user corresponding to the terminal device 101 logs in to the first identity account, they can receive not only the session messages under the first identity account, but also the session messages under the second identity account. This avoids the need to frequently switch between the first and second identity accounts to view the messages under the second identity account. It breaks down the barriers between the target user's first and second identity accounts and eliminates the mutual exclusion between accounts. The second identity account is directly bound to the first identity account so that all session messages received by the second identity account are transferred to the first identity account, thereby improving the target user's efficiency in managing session messages across multiple identity accounts.

[0062] Based on the aforementioned message display system and message display scheme, this embodiment of the invention provides a message display method. Please refer to... Figure 2 This is a flowchart illustrating a message display method according to an embodiment of the present invention. This message display method can be executed by a terminal device, which can be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, smart wearable device, or other device with display functionality. This embodiment of the present invention does not limit the scope of the terminal device. The message display method specifically includes the following steps:

[0063] S201. Display the first message receiving interface corresponding to the first identity account. The first message receiving interface includes a target type session message identifier, which is used to indicate that there is a target contact in the second identity account sending a target session message to the target user.

[0064] In one embodiment, a target user can simultaneously possess a primary identity account and a secondary identity account. The primary identity account is a user account applied for by the target user using a primary identity within a social application. This social application can be an instant application, such as QQ, WeChat, or WeChat Work; alternatively, it can be a non-instant application, such as Weibo or short video applications. The primary identity account is typically the target user's personal account used for social interactions. The secondary identity account is a user account applied for by the target user using a secondary identity within the social application. This secondary identity account can be a corporate identity account, such as those from gaming or educational companies. The user information for the primary and secondary identity accounts differs. This information may include the account's profile picture, nickname, QR code, and bio. When the primary identity account is a personal account, the bio may include the account's university and age. When the secondary identity account is a corporate account, the bio may include the account's creation date, reason for creation, and service objectives.

[0065] In one embodiment, the first message receiving interface corresponding to the first identity account is used to notify the target user under the first identity account that a session message has been received. Specifically, the notification method can be: displaying a session window identifier indicating a session between the target contact under the first identity account and the target user. Each session window identifier can include the identifier information of the target contact who initiated the session and the session message sent. When any session window identifier is triggered, the corresponding session window can be displayed, and the session message generated in that session can be displayed in the session window. The identifier information of the target contact can include an image identifier and a name identifier. The image identifier can be the avatar set by the target contact when registering an account in the social application. The name identifier can be the nickname set by the target contact when registering an account in the social application, or it can be a nickname set by the target user. For example, the target contact under the first identity account used the nickname "Tomorrow Will Be Better" when registering, and the target user changed the nickname to "Zhang Moumou".

[0066] For example, see Figure 3 This is a schematic diagram of a first message receiving interface corresponding to a first identity account, provided in an embodiment of the present invention. Figure 3 The first message receiving interface shown may include a conversation window identifier 301 for a conversation between the target contact Zhang Moumou under the first identity account and the target user, and a conversation window identifier 302 for a conversation between the target contact Chen Moumou under the first identity account and the target user. The target user can open a conversation window to communicate with the corresponding contact by triggering either conversation window identifier. In the conversation window, the target user can view and enter conversation messages.

[0067] In another embodiment, the first message receiving interface corresponding to the first identity account is also used to notify the target user under the second identity that a session message has been received. Specifically, the notification method may be: displaying a target type session message identifier in the first message receiving interface; the target user enters the second message receiving interface corresponding to the second identity account by triggering the target type session message identifier, and views the session message from the second message receiving interface.

[0068] In other words, this target type session message identifier is used to indicate that a target contact in the secondary identity account sends a target session message to the target user. Specifically, it can be understood as indicating that a target contact under the secondary identity account sends a target session message to the target user in the secondary identity, and the number of target contacts can be one or more. In practical applications, this target type session message identifier can be viewed as a message box or a message node. Managing session messages sent by target contacts under the secondary identity account through this identifier helps solve the problem of lost session messages when a target user has multiple identities. The target user can click on the target type session message identifier to open the secondary message receiving interface of the secondary identity account, and perform operations such as replying to session messages from target contacts and forwarding session messages sent by target contacts within this interface. The target type session message identifier can include the session name, session icon, and number of session messages associated with the secondary identity account. The session type can refer to whether the session belongs to "customer messages," the session icon is related to the specific identity of the secondary identity account (e.g., a teaching building if it's an education enterprise account), and the number of session messages can be displayed numerically, where the number represents the number of session messages. As mentioned above, there can be one or more target contacts. The number of conversation messages displayed here refers to the total number of conversation messages sent by multiple target contacts to the target user under the secondary identity. For example, if target contact Zhang under the secondary identity account sends one conversation message to the target user, and target contact Li under the secondary identity account sends two conversation messages to the target user, then the number of conversation messages displayed on the first message receiving interface is 3.

[0069] Optionally, to distinguish between session messages under the first identity account and session messages under the second identity account, the server records session messages under each identity account based on the account type identifier `id_type` and a key (key-value pair). `id_type` represents the account type identifier; one account type identifier indicates one identity account. Different identity accounts correspond to different values ​​of `id_type`. For example, `id_type` equal to 0 indicates the first identity account, and `id_type` equal to 1 indicates the second identity account. The key represents the number of session messages received under the corresponding identity account. Correspondingly, the user terminal can process the session messages based on the account type identifier `id_type` carried in each session message. If the account type identifier `id_type` in a session message is equal to 0, indicating that the session message belongs to the first identity account, the session message is displayed on the first message receiving interface of the first identity account according to the processing logic for session messages of the first identity account. If the account type identifier `id_type` in a session message is equal to 1, indicating that the session message belongs to the second identity account, a target type session identifier is created, such as a message node, and the session message is not directly displayed but collected under this target type session identifier. The session message will only be displayed after the target type session identifier is clicked. In other words, when a user terminal receives multiple session messages pushed by the server, it is necessary to filter out the session messages with the account type identifier of 1 and collect these session messages in the target type session identifier.

[0070] For example, in Figure 3 In the first message receiving interface shown, 303 represents the target type session message identifier. Assuming that the target user's second identity account is an enterprise identity account, the session name related to the second identity account in the target type session message identifier can be identified as "customer message". The session icon can be represented as shown in 31, and the number of session messages is 3.

[0071] In one embodiment, the target user may have multiple secondary identity accounts. In this case, the session messages of multiple secondary identity accounts can be displayed using the same target type session message identifier. Unlike displaying the session messages of a single secondary identity account, when the target type session message identifier is used to indicate that multiple secondary identity accounts have received the session messages, the target type session message identifier may include a session name, a session icon, and the number of secondary identities that received the session messages. The session name can be represented as "other identity accounts," and the session icon can be randomly assigned by the server or randomly generated by the terminal device. For example, see... Figure 4a This is a schematic diagram of a first message receiving interface under multiple second identity accounts provided in an embodiment of the present invention. Figure 4a In the text, 411 represents the target type session message identifier; the number 3 indicates that the session message was received under three secondary identity accounts.

[0072] In another embodiment, the session messages of each of the multiple second identity accounts can be displayed using a target type session message identifier. The information included in each target type session message identifier is the same as that included in the target type session message identifier when there is only one second identity account, and will not be repeated here. For example, see Figure 4b This is a schematic diagram of another first message receiving interface under multiple second identity accounts provided in an embodiment of the present invention. Figure 4b Assuming there are two secondary identity accounts, "Customer Message 1" and "Customer Message 2" represent the session names of the two different secondary identity accounts, and 410 and 420 are the target type session message identifiers corresponding to the two different secondary identity accounts. The number "3" in 410 indicates that the secondary identity account corresponding to Customer Message 1 received 3 session messages. The number "2" in 420 indicates that the secondary identity account corresponding to Customer Message 2 received 2 session messages.

[0073] As described above, when a target user receives a session message from a target contact, it will display the message based on feedback from the server. Specifically, when a target user receives a new session message, the server uses `id_type` to distinguish whether the message was sent by a contact of the first identity account or a contact of the second identity account. For example, if the `id_type` for the first identity account is pre-set to 0, and the `id_type` for the second identity account is not 0, then when the server receives a new session message from a target contact, it checks the value of `id_type`. If it is 0, then the session message was sent by the target contact of the first identity account; if it is not 0, then the session message was sent by the target contact of the second identity account. The server returns the result to the target user's terminal. If the target user's terminal detects that `id_type` is 0 in the result, it directly displays the message in the first message receiving interface using a session window identifier (e.g., ...). Figure 3 As shown in 301), if it is not 0, the session messages will be collected under the target type session message identifier. When the target type session message identifier is triggered (e.g., Figure 3 The session message will only be displayed if the 303 error is shown.

[0074] S202. When the target type session identifier is selected, the second message receiving interface of the target user under the second identity account is displayed, and the session window identifier of the conversation between the target user under the second identity account and the target contact is displayed on the second message receiving interface.

[0075] In one embodiment, if a target user clicks the target type session message identifier on the first message receiving interface of the first identity account, the user is redirected to the second message receiving interface under the second identity account. For example, when the target user clicks... Figure 3 If a 303 error occurs, it will redirect to the second message receiving interface, such as... Figure 5 As shown in Figure 500.

[0076] In one embodiment, the second message receiving interface may display session window identifiers for the target contacts and target users under the second identity account. It should be understood that there can be multiple target contacts; therefore, there can also be multiple session window identifiers on the second message receiving interface. For example, in... Figure 5 In the context of the target users, the target users can be "Little Piggy" and "Eat Five". The session window identifier for "Little Piggy" to have a conversation with the target user can be represented as 510, and the session window identifier for "Eat Five" to have a conversation with the target user can be 520.

[0077] Optionally, the second message receiving interface displays session window identifiers for target session messages from different target contacts and target users under the second identity account. Each session window identifier includes the number of session messages, which can be represented in numerical form, i.e., the size of the number represents the number of session messages sent by each target contact to the target user.

[0078] For example, Figure 5 The 500 shown includes 510 and 520, which represent the session window identifiers of the target contact and the target user. Each session window identifier displays the number of session messages. For example, 501 in 510 and 502 in 520 both represent the number of session messages. If 501 shows 2, it means that the target contact "Little Piggy" sent 2 target session messages to the target user "Guessing Song Planet Customer Service" under the second identity account. If 502 shows 1, it means that the target contact "Eat Five" sent 1 target session message to the target user "Guessing Song Planet Customer Service" under the second identity account.

[0079] S203. When the session window identifier is triggered, the session window of the target user under the second identity account and the target contact is displayed, and the target session message is displayed in the session window.

[0080] In one embodiment, the conversation window is primarily used to display target conversation messages between the target contact and the target user under the second identity account. Specifically, when the target user clicks the conversation window icon, a conversation window is displayed between the target user under the second identity account and the target contact. This conversation window displays conversation messages sent by the target contact to the target user, as well as conversation messages sent by the target user to the target contact. The target user can view, reply to, and forward the target conversation messages sent by the target contact. As seen through steps S201-S203, in this embodiment of the invention, if the target user's first identity account is logged in in the current social application, then the conversation messages received by the target user under the second identity account will be collected into a target type conversation message icon (specifically, it can be a message box or message node) and displayed through the message box or message node. The target user can reply to and forward the conversation messages received under the second identity account within the message node, effectively solving the problem of lost conversation messages under multiple identities and the problem of untimely viewing or replying to conversation messages. Optionally, the chat window may display identification information of the target contact, including image and text identifiers. The text identifier may be such as the target contact's nickname, and the image identifier may be such as the target contact's avatar.

[0081] Furthermore, if a session message is viewed by the target user, it can be considered to be in a read state; conversely, if the session message is not viewed by the target user, it can be considered to be in an unread state. Optionally, if a session window indicator is triggered, it can be considered that the session message has been viewed by the target user. In the message receiving interface (including the first message receiving interface and the second message receiving interface), a preset marker, such as a solid circle, can be used to indicate that the session message is in an unread state; if the session message changes from an unread state to a read state, the preset marker disappears.

[0082] In one embodiment, when a server pushes session messages to a social application, it does so based on the message's state. For example, when a session message is in a read state, it indicates that the message has been viewed by the target user and does not need to be pushed again; when a session message is in an unread state, it indicates that the message has not yet been viewed by the target user and needs to be pushed to them. Conversely, if a session message in the social application is viewed by the target user, the target user's terminal can send a notification to the server that the message is in a read state.

[0083] In existing technologies, a target user has only one identity account in a social application. The notification information sent by the target user's terminal includes the identity account and the target session message. That is, in the case of only having one identity account, the server records the read or unread status of a session message based on the identity account (such as a QQ number) as the key. However, in this embodiment of the invention, since the first identity account is also bound to a second identity account, meaning that the target user can have multiple identity accounts in the social application, the content included in the notification information sent by the target user's terminal to the server in this embodiment of the invention is different from the above. Specifically, it may include the identity account, the identity account identifier, and the target session message. In other words, in this embodiment of the invention, the server records the read or unread status of a session message based on the identity account identifier and the identity account as the key.

[0084] For example, please participate Figure 6 This is a schematic diagram of a conversation window interface disclosed in an embodiment of the present invention. The target contact is "Little Piggy". 601 displays the conversation message sent by the target contact "Little Piggy" to the target user. 602 displays the conversation message sent by the target user to the target contact "Little Piggy" using a second identity account. 611 is the avatar of the target contact "Little Piggy", and 612 is the nickname of the target contact "Little Piggy".

[0085] Based on the above description of steps S201 to S203, the present invention discloses a schematic diagram of a message display, as shown below. Figure 7 As shown, the specific steps are as follows: When the target user clicks on the target type session message identifier 711 in the first message receiving interface 710, the second message receiving interface 720 is displayed. As can be seen from the figure, the number of session messages in the target type session message identifier 711 in the first message receiving interface 710 is 3, which means that there are 3 unread session messages in the second message receiving interface 720. Assuming that among these 3 unread session messages, the contact "Little Piggy" sent 2 session messages and the contact "Eat Five" sent 1 session message. Further, when the target user clicks on the session window identifier 721 in the second message receiving interface 720, the session window 730 is displayed. The session window 730 includes the target session messages of the target contact and the target user under the second identity account. Since the number of session messages in the session window identifier 721 is "2", the session window 730 displays that the target contact "Little Piggy" sent 2 target session messages to the target user, as shown in 731 and 732.

[0086] Optionally, to improve the convenience and intelligence of chats between the target contact and the target user under the secondary identity account, this function can be implemented by sending a smart conversation message when the target contact first establishes a conversation window with the target user. Specifically, when the target contact creates a conversation between the target contact and the target user under the secondary identity account, a smart conversation message is displayed in the conversation window. This smart conversation message is entered by the target user using the secondary identity account. This smart conversation message can be customized by the target user in the smart conversation message settings interface, which is displayed when the target user triggers the smart conversation management option in the settings interface. The smart conversation message can include basic greeting messages, such as "Hi, how can I help you?"; it can also include predicted questions related to the secondary identity or the secondary identity account. For example, assuming the secondary identity is a customer service representative for a company, predicted questions could include "How to purchase xxx", or "How to perform a guessing game", etc., or predicted questions could include "How to block someone", or "How to find chat history", etc. These predicted questions can be derived from summarizing a large number of historical conversation messages or determined based on the characteristics of the secondary identity account.

[0087] Optionally, when setting these predictive questions, target users can also set corresponding response conversation messages. In this way, when a target contact user triggers one of the predictive questions, the corresponding response conversation message can be automatically and promptly displayed to the target contact user. This can avoid the situation where the target contact's problem cannot be resolved in a timely manner because the target user does not check the conversation message in time.

[0088] For example, see Figure 8 This is a schematic diagram of an intelligent conversation message disclosed in an embodiment of the present invention. When the target contact opens a conversation window 800 with the target user under the second identity account, intelligent conversation messages will be displayed in the conversation window 800, as shown in 801 and 802. If the target contact clicks on the intelligent conversation message "How to block someone", the pre-set reply conversation message corresponding to the intelligent conversation message will be displayed in the conversation window 800, such as "Click on the other party's avatar to see the blocking entry".

[0089] It should be understood that some functional modules may differ between different versions of social applications. In newer versions of social applications, certain functional modules may be updated, and some functions in newer versions may not be available in older versions. To ensure the smooth implementation of the function of binding a new identity account (i.e., the second identity account) to an existing identity account (i.e., the first identity account) and receiving conversation messages from the new identity account through the existing identity account, this embodiment of the invention considers the version compatibility between the social application used by the target user and the social application used by the target contact user when the target contact has a conversation with the target user under the second identity. When the versions of the two social applications are the same, they can have a conversation directly. When the versions of the two social applications are different, a prompt message is sent to the target contact under the second identity account to remind the user to update the version. Specifically, during a conversation between a target user under a secondary account and a target contact, when the target user enters any conversation message in the conversation window, the target user's terminal sends a conversation message sending request to the server. This request instructs the server to check if the version information of the social application on the target contact's terminal is the preset version. If the version information is the preset version, the server directly forwards the conversation message to the target contact's terminal, and simultaneously displays the conversation message sent by the target user in the target contact's message receiving interface. If the version information is not the preset version, the server returns a request response notification to the target user's terminal. This notification indicates that the version information is not the preset version, and a fifth prompt message is displayed on the target user's terminal interface. This fifth prompt message indicates that any conversation message sent by the target user to the target contact failed to be sent. Meanwhile, the fifth prompt message is also used to prompt the target contact to update the version of the social application. The prompt message can be sent to the target contact's terminal in the form of an SMS, or it can be prompted to the target contact in the conversation window between the target user and the target contact under the first identity account. The target contact can then see the prompt message "This user initiated a conversation with you under a second identity. Please update and check" in the conversation window.

[0090] In this implementation, a first message receiving interface corresponding to the first identity account is displayed. This interface includes a target type session message identifier, which indicates that a target contact in the second identity account is sending a target session message to the target user. When the target type session message identifier is selected, a second message receiving interface for the target user under the second identity account is displayed. This second message receiving interface also displays a session window identifier indicating a conversation between the target user and the target contact under the second identity account. When the session window identifier is triggered, a session window indicating a conversation between the target user and the target contact under the second identity account is displayed, along with the target session message. By using the target type session message identifier to distinguish messages received by different identity accounts, efficient management of session messages across multiple accounts is achieved without switching accounts. Specifically, the target user's multiple identities will generate separate message nodes in the message receiving interface of the first identity account. Session messages sent to the second identity account are all collected in this message node, making it more convenient for the target user to receive messages without switching identities.

[0091] Based on the aforementioned message display system and message display scheme, this embodiment of the invention provides another message display method. Please refer to... Figure 9 This is a flowchart illustrating another message display method disclosed in an embodiment of the present invention. This message display method can be executed by a terminal device, which can be a smartphone, tablet computer, laptop computer, desktop computer, smart speaker, smartwatch, smart wearable device, or other device with display functionality. This embodiment of the present invention does not limit the scope of the terminal device. The message display method specifically includes the following steps:

[0092] S901. Display the identity account management interface in the social application, which includes options for creating new identity accounts.

[0093] The identity account management interface is primarily used by target users to manage their identity accounts. This interface includes the account identification information (image icon, text icon, and account name) for the primary identity account. When a target user clicks on the account identification information of the primary identity account, they can manage it, such as deleting the primary identity account, modifying its image icon or text icon, etc. The identity account management interface may also include a new identity account creation option; triggering this option allows the creation of a new identity account. For example, Figure 10a The diagram shown is a schematic diagram of an identity account management interface disclosed in an embodiment of the present invention, wherein 1001 is the account identification information of the first identity account, and 1002 is the creation option for creating a second identity account.

[0094] In one embodiment, the target user can access the identity account management interface through the first message receiving interface. See details below. Figure 10b As shown, the first message receiving interface includes the first account identifier information of the first identity account, which may specifically be the profile picture of the target user under the first identity account in the social application, for example... Figure 3 The error message 304 is shown; when the target user clicks on the first account identification information 304 displayed on the first message receiving interface, the application management interface of the first identity account is displayed, such as... Figure 10b As shown in Figure 1020, the application management interface 1020 includes a settings option 1021; if this settings option 1021 is triggered, the account settings interface of the first identity account is displayed, such as... Figure 10b As shown in 1030, the account settings interface 1030 is mainly used by the target user to make relevant settings for the primary identity account, such as account security settings, account message notifications, etc. The account settings interface 1030 includes an account management option 1031. By clicking the account management option 1031, the identity account management interface 1040 of the social application is displayed.

[0095] Optionally, the account management interface also includes an account status setting option. Target users can use this option to configure whether they are allowed to be added as a contact under another contact's secondary account. Specifically, when the account status setting option is in the first state, the target user is allowed to be added by any contact as a target contact under that contact's secondary account. "Any contact" refers to a contact of the target user under the first account, and the secondary account of that contact must belong to a different account type than the first account. When the account status setting option is in the second state, the target user is not allowed to be added by any contact as a contact under that contact's secondary account. In other words, if contact A has two accounts, one private and one business, and contact A wants to add the target user as a friend using the business account, if the target user's account status setting option is in the first state, contact A can successfully add the target user as a friend; if the target user's account status setting option is in the second state, contact A cannot successfully add the target user as a friend.

[0096] For example, the account status settings option can be found in Figure 11 Configure it in the settings. Figure 11This is a schematic diagram of the interface display of an account status setting option disclosed in an embodiment of the present invention. 1101 represents the account status setting option, which is displayed in the identity account management interface of the first identity account. This account status setting option can be composed of two parts, 110 and 111. When 110 is to the right of 111, it can be assumed that the account status setting option is in the first state, such as... Figure 11 As shown in 1101; when 110 is to the left of 111, it can be assumed that the account status setting option is in the second state, such as... Figure 11 As shown in Figure 1102.

[0097] S902. When the option to create a new identity account is triggered, the interface for creating a new identity account is displayed. The interface for creating a new identity account includes an account identification information setting area and a confirmation creation control.

[0098] In one embodiment, a target user can create a new identity account through a new identity account creation interface. When the target user clicks the "Create New Identity Account" option in the identity account management interface of the first identity account, the new identity account creation interface is displayed directly. The new identity account creation interface includes an account identification information setting area and a confirmation creation control. The account identification information setting area is mainly used to set the image identification information of the new identity account, such as the avatar of the new identity account, and can also set the text identification information of the new identity account, such as the nickname and brief information of the new identity account.

[0099] Optionally, in addition to the method described above for displaying the new account creation interface, another approach can be used. Specifically, when the target user clicks the "Create New Account" option, an introduction interface for the new account is displayed, primarily to introduce the functional information of the new account. For example, if the target user is creating a corporate identity, the introduction interface will display information about the corporate identity. After the target user understands the details of the new identity, clicking the "Create" option in the introduction interface will redirect them to the new account creation interface.

[0100] For example, Figure 12This is a schematic diagram of the interface process for creating a second identity account according to an embodiment of the present invention. In the identity account management interface 1210 of the first identity account, 1211 is the option to create a new identity account. After the target user clicks 1211, the identity introduction display interface 1220 of the new identity account is displayed. In this interface, 1221 mainly introduces the new identity, and option 1222 is the option to confirm the creation of a new identity account. When the target user clicks 1222, the creation interface 1230 of the new identity account is displayed. In this interface, the account identification information setting area 1231 is mainly used by the user to set account information. The confirmation creation control 1232 is mainly used by the user to confirm the creation after editing the content of the account identification information setting area. After confirmation, it means that the new identity account has been successfully created.

[0101] In many cases, a target user may want to create multiple secondary identity accounts. Therefore, the primary identity account's account management interface can include multiple options for creating new identity accounts, meaning each new identity account corresponds to one creation option. The corresponding creation steps can also be as follows... Figure 12 As shown.

[0102] Optionally, besides directly opening the new identity creation interface by clicking the "Create New Identity" option in the identity account management interface, another method can be used: The first identity account's identity account management interface includes a second identity account management option. When the target user clicks this option, the second identity account's identity account management interface is displayed. This interface, in turn, includes the "Create New Identity Account" option. If the target user has already created a second identity account, its identity account management interface will also include the account identifier information, such as image and text identifiers. When the "Create New Identity Account" option in the second identity account's identity account management interface is triggered, the new identity account creation interface is displayed.

[0103] For example, such as Figure 13 As shown, Figure 13This is a schematic diagram of another interface process for creating a second identity account disclosed in an embodiment of the present invention. In this interface, 1311 in the identity account management interface 1310 of the first identity account is the second identity management option. When the target user clicks 1311, the identity account management interface 1320 of the second identity account is displayed. The identity account management interface 1320 displays a new identity creation option 1321. When the target user clicks the new identity creation option 1321, the identity introduction display interface 1330 of the new identity account is displayed. Area 1331 mainly introduces the identity type, and option 1332 is a confirmation option for creating a new identity account. When the target user clicks 1332, the new identity account creation interface 1340 is displayed. The account identification information setting area 1341 is where the user sets account information. After editing the content of the account identification information setting area, clicking the confirmation creation control 1342 confirms the creation, indicating that the new identity account has been successfully created.

[0104] S903. If it is confirmed that the creation control has been triggered, the creation success interface for the second identity account of the target user will be displayed, indicating that the second identity account has been created successfully.

[0105] In one embodiment, to determine whether the new identity has been successfully created, a creation success screen is displayed, showing relevant information about the new identity account. Specifically, if the target user clicks the "Confirm Creation" control on the new account creation screen, it indicates that the new identity account, i.e., the second identity account, has been successfully created. Correspondingly, when the "Confirm Creation" control is selected, the creation success screen for the second identity account is triggered. This screen can display the second account identifier information corresponding to the second identity account, as well as related functional information such as quick replies and self-service Q&A. The second account identifier information is the information entered by the target user in the account identifier information setting area.

[0106] For example, such as Figure 12 As shown, when the target user clicks the confirmation creation control 1232 in 1230, a creation success interface 1240 is displayed. This interface 1240 displays the second account identifier information 1241 and 1242 corresponding to the second identity account, and also includes a function display area 1243. For example, as... Figure 13 As shown, when the target user clicks the confirmation control 1342 in 1340, a creation success interface 1350 will be displayed. This interface 1350 displays the second account identifier information 1352 and 1352 corresponding to the second identity account, and also includes a function display area 1353. Correspondingly, after successful creation, the created second identity account's image identifier will be displayed in the first identity account's identity account management interface. For example, as... Figure 14The diagram shows a schematic of an image identifier. 1410 is a schematic of an image identifier when only one secondary identity account is created, where 1411 is an image identifier; 1420 is a schematic of an image identifier when multiple secondary identity accounts are created, where 1421 is the image identifier of the first secondary identity account and 1422 is the image identifier of the second secondary identity account.

[0107] Furthermore, after the second identity account (i.e., the new identity account) is successfully created, to facilitate the target user's management of the second identity account, the second account identification information of the second identity account will be displayed in the identity account management interface, including an image identifier and a text identifier. The image identifier can be understood as the profile picture of the second identity account, and the text identifier can be understood as the nickname of the second identity. It should be noted that, under normal circumstances, the nickname of the first identity account (i.e., the username used by the user when creating the account) can be noted by other contacts. Notes are made by changing the target user's nickname to a name that the target contact is familiar with. For example, if the target user's first identity account nickname is "Xiao xx", the target contact can change the nickname "Xiao xx" to "Zhang San" for easy memorization. However, under normal circumstances, the nickname of the second identity account is used to represent the function of the second identity account, therefore, the nickname of the target user's second identity account cannot be noted by other contacts. To prevent other contacts from using the nickname of a secondary identity account in their notes, the server needs to intercept the note-making operation based on the account type identifier of the secondary identity account. In practice, when the server detects that the target contact is modifying the note for a secondary identity account, the server will prohibit the operation and send a notification message indicating that the modification failed to the target contact who initiated the modification.

[0108] In one embodiment, when the target user is on the target user's terminal device (which may be such as...) Figure 1After the terminal device 101 shown creates the second identity account, the target user's terminal device will have an entry point to retrieve the account information of the second identity account from the server, and display the retrieved information on the terminal device's interface through this entry point. Specifically, the target user's terminal device retrieves the target user's account information by sending a pull list signaling (cmd_query_multi_id_list) to the server. The server obtains a JSON list based on the pull list signaling, as shown in the following code snippet. This JSON list includes the target user's first identity account and second identity account, as well as the data under the first identity account, the data under the second identity account, and the account type identifiers corresponding to the first and second identity accounts. The server returns the JSON list to the target user's terminal device. In the following code, the first identity account is "111111111111", which can be understood as the target user's original account, and the second identity account is "2222222222222", which can be understood as a new account. Both the new account and the original account belong to the target user, but they are different.

[0109]

[0110] Furthermore, since multiple identities are applied for using specific identity number ranges, multiple identity accounts and the primary identity account share some attributes, such as the same basic information, including profile pictures, nicknames, and QR codes. The server can distinguish them based on these identity number ranges; that is, the server can retrieve identity information for different identities simply by using these ranges. Because the identity number ranges are different, the retrieved information will also be different. Optionally, multiple identity accounts can also share the same attributes as the primary identity account, but the specific information corresponding to these attributes will differ. That is, multiple identity accounts can have entirely new image and text identifiers, specifically different profile pictures, different nicknames, and different QR codes, etc.

[0111] In one embodiment, after the secondary identity account is created, the target user can configure the relevant functions of the secondary identity account through its settings interface. Specifically, the settings interface for the secondary identity account may include: when the target user clicks the image icon in the identity account management interface of the primary identity account, the image icon appears as follows: Figure 14 The number 1411 displayed shows the settings interface for the secondary identity account. This interface includes several options for managing the secondary identity account, such as contact management, smart conversation message management, quick reply management, association management for linking the secondary identity account to associated applications, and an account deletion control, among others.

[0112] For example, the settings interface can be like... Figure 15a The diagram shown is a schematic of the settings interface for a second identity account disclosed in an embodiment of the present invention. In this diagram, 1501 represents the contact management option, 1502 represents the smart conversation message management option, 1503 represents the quick reply management option, 1504 represents the association management option for associating the second identity account with the associated application, and 1505 represents the identity account deletion control.

[0113] Optionally, in addition to displaying the settings interface for the second identity account as described above, another method can be used to display the settings interface for the second identity account. Specifically, when the target user clicks the "Second Identity Management" option in the first identity account's identity account management interface, the second identity account's identity account management interface is displayed. Then, when the target user clicks the icon in the second identity account's identity account management interface, the second identity account's settings interface is displayed. Furthermore, the target user can display the settings interface by clicking the settings controls in the second message receiving interface of the second identity account. These settings controls can be as follows: Figure 12 As shown in 530.

[0114] It should be understood that the above descriptions are from the perspective of the terminal device, detailing how the settings interface is displayed. The following section will explain the interaction between the terminal device and the server; a detailed flowchart can be found below. Figure 15bAs shown: When a target user selects the first account identifier information on their terminal device, the identity account management interface is triggered, which includes the option to create a new identity account. Selecting the new identity account creation option then triggers the creation interface for a new identity account, which includes an account identifier setting area and a confirmation control. When the target user clicks the confirmation control, the terminal device sends a creation request to the server to create a new identity account. This request carries the account type identifier of the new identity account; optionally, the account type identifier can be represented by `id_type`. Further, after the server determines the basic information corresponding to the new identity based on the `id_type` identifier, it sends an interface display instruction information corresponding to the new identity account type to the terminal device. The terminal device then displays the settings interface based on the interface display instruction returned by the server and the information entered in the account identifier area of ​​the new identity account creation interface. The server assigns a new identity account to the target user based on the account type identifier (id_type) carried in the creation request. This may include: determining a new number range based on the account type identifier; randomly selecting an account from the new number range as the target user's second identity account; and using the second identity account as the unique identifier for the target user under the second identity in the social application. This new number range is different from the number range of the first identity account; the new number range is specifically used for applying for multiple identities, and users without a first identity account in the social application cannot apply for one. This new number range also facilitates subsequent processing logic such as maintaining friend relationship chains and friend lists. Each identity account corresponds to an identity attribute. The identity attribute of the primary identity account can be a private identity, in other words, the primary identity account can be used by the target user for ordinary social interaction, such as chatting with friends. The identity attribute of a multi-identity account can be determined according to the type of the multi-identity account. For example, if the identity account type of a multi-identity account is enterprise identity, then the identity attribute is enterprise attribute, which means that the identity account is mainly used for social interaction with people related to the enterprise. As another example, if the identity account type of a multi-identity account is teacher identity, then the identity attribute is teacher attribute, which means that the identity account is mainly used for social interaction related to education.

[0115] Optionally, the target user terminal device can send a request to the server to create a new identity account by adding a multi-identity signaling (cmd_add_multi_id). This signaling can carry an account type identifier (id_type) to which the new identity account belongs. As mentioned above, in order to realize the multi-identity account creation function, the server can pre-set multiple types of identity accounts and their corresponding account type identifiers (id_type). For example, the id_type for a normal identity in a social application is 0, and the id_type for an enterprise identity is 1.

[0116] In summary, the social application in this embodiment of the invention can support setting multiple identities. When a target user adds a new identity, the server will create a new identity account by default (the new identity account can be considered as an identity account other than the first identity account (i.e., the existing account) and bind it to the existing identity account. However, the multiple identity accounts (such as the second identity account mentioned above) are new number segments. This number segment is specifically used for multiple identities, and external users (external users refer to users who have not applied for a first identity account in the social application) cannot apply for it. For example, Figure 15c This is a schematic diagram of the creation of a new identity account disclosed in an embodiment of this application. When a target user adds a new identity, the target user clicks the "Create New Identity Account" option and then clicks "Add New Identity." At this time, the target user terminal sends an add request to the server, carrying the id_type in the add request. After receiving the add request, the server first creates a new number segment, and then selects a number from the new number segment to determine the new identity account, and then binds the new identity account with the id_type. Furthermore, the server can also obtain the basic information of the new identity account based on the id_type carried in the new add request, and then send the obtained basic information to the target user terminal. The target user terminal then initializes the information page of the new identity account based on the basic information.

[0117] In one embodiment, the server pre-configures multiple types of identity accounts and the corresponding account type identifiers (id_type) for these multiple types of identity accounts, which can be represented by the following code. In the following code, assume the social application supports four account types for user applications, represented as kMultIDTypeDefault (which can be understood as the most common identity supported by the social application, such as the aforementioned primary identity), kMultIDTypeBusiness (which can be understood as a business identity account), kMultIDTypeOnlineService (which can be understood as an online customer service identity), and kMultIDTypeEnd. These four account type identifiers can be represented using 16-bit binary numbers. For example, in the following code, assume the account type kMultIDTypeDefault can be represented as 0000 0000 0000 0000, abbreviated as 0; the account type kMultIDTypeBusiness can be represented as 0x1<<0, meaning no left shift of the binary 0000 0000 0000 0001, which means the account type kMultIDTypeBusiness can be represented as 1; and the account type kMultIDTypeOnlineService can be represented as 0x1<<1, meaning no left shift of the binary 0000 0000 0000 0001. 0000 0001 is shifted left by one bit, and the result of shifting left by one bit is 0000 0000 0000 0010. That is to say, the account type identifier corresponding to kMultIDTypeOnlineService can be 2. Similarly, the account type identifier corresponding to kMultIDTypeEnd is obtained by shifting 0000 0000 0000 0001 left by two bits, which is represented as 0x1<<2.

[0118]

[0119] The server then initializes the basic information for different account identities based on the corresponding `id_type` and returns this information to the target user's terminal device. For example, when `id_type` is 1, which represents an enterprise identity, the corresponding basic information includes service hours, welcome message, self-service Q&A, and quick replies. The target user's terminal device will then display the identity information based on this information. This identity's basic information is returned to the client via JSON. The JSON information shown in the table below is an example; different fields represent different information, such as "service_time," which represents the service hours and is set to "all day."

[0120]

[0121] Since the settings interface for the secondary identity account includes multiple management options, target users can click on each management option to configure related settings, thereby enriching the functionality of the secondary identity account. These settings include the following:

[0122] In one embodiment, the settings interface includes an identity account deletion control, which is mainly used by the user to delete a secondary identity account. That is, when the target user clicks the identity account deletion control, the secondary identity account will be deleted, equivalent to deleting the secondary identity account with one click. For example, when the target user clicks... Figure 15a When the identity account deletion control 1505 shown is executed, such as "Delete Enterprise Identity", the corresponding second identity account will be deleted and will not be displayed in the social application interface of the target user's terminal device.

[0123] In another embodiment, the settings interface includes a contact management option. This contact management option is primarily used by the target user to add or remove target contacts under the second identity account when the target user triggers the contact management option. Specifically, when the contact management option is selected, the contact management interface is displayed. The contact management interface includes a contact addition control. When the target user clicks the contact addition control, the contact addition interface is displayed. This contact addition interface includes a first display area and a second display area. The first display area displays the user identification information of multiple candidate contacts, including the user's avatar and nickname. Here, the multiple candidate contacts are all contacts under the first identity account. The second display area displays the user identification information of the selected target contact from the multiple candidate contact user identification information. Furthermore, if the confirm add control in the contact addition interface is triggered, the user identification information of the target contact in the second display area is displayed in the contact management interface.

[0124] For example, as shown in 16a, it is a schematic diagram of the interface flow for adding contacts disclosed in an embodiment of the present invention. When the target user clicks the contact management option 1501 (such as "Customer Friends") in the settings interface 1610, the contact management interface 1620 is displayed. When the target user clicks the add control 1621 (such as "Import Friends") in the contact management interface 1620, the contact adding interface 1630 is displayed. The interface includes a first display area 1632 and a second display area 1631. The first display area 1632 displays the contacts under the first identity account, and the second display area 1631 displays the contacts selected from 1632. The contact adding interface 1630 also includes a confirmation add control 1633 (such as "Invite Now"). When 1633 is clicked, the contacts in the second display area 1631 will be displayed in the contact management interface 1620. For example, the contacts displayed in area 1622 are the contacts in the second display area 1631.

[0125] Correspondingly, by combining the server with the ability to add contacts for the secondary identity account, it can be done as follows: Figure 16b The diagram shows a flowchart of an implementation of this application for adding a contact. The target user on the target user's terminal device clicks the "Contact Management" option in the settings interface to display the Contact Management interface. Clicking the "Contact Management" option within the Contact Management interface displays the Contact Add interface, which includes a contact list for the first identity account. When the target user selects a target contact from the contact list and triggers the confirmation button in the Contact Add interface, the target user's terminal device sends a friend add request to the server. The server determines the type of the second identity account based on the `id_type` carried in the friend add request, updates the target friend relationship chain between the target user and the target contact based on the type of the second identity account, and returns the updated result to the target user's terminal device. The target user's terminal device then displays the target contact's user identification information in the Contact Management interface based on the updated result. This indicates that the target user has successfully added a target contact for the second identity account.

[0126] Furthermore, after a target user successfully adds a target contact to their secondary account, the target user's terminal can display the target contact's contact list item based on the target friend relationship chain, and can also display the target user in the contact list item associated with the secondary account. The server, in order to configure which target contacts can display multiple identity information, employs two methods:

[0127] The first method: Add a multi-identity flag (show_multi_id_flag) to the target user's and target contact's target friend relationship chain, such as... Figure 16bAs shown, after a target user adds a target contact as a contact under a second identity account, the server adds a multi-identity flag, `show_multi_id_flag`, to the friend relationship chain between the target user and the target contact. The target contact's terminal then selects which identities of the target user to display to the target contact based on the multi-identity flag. Optionally, the value of `show_multi_id_flag` is obtained by performing a bitwise AND operation on the `id_type` corresponding to the target user's first identity account and the `id_ype` of the second identity account pair. Therefore, the target contact's terminal's selection of which identities of the target user to display to the target contact based on the multi-identity flag includes: determining which account type identifiers were used to perform the bitwise AND operation on the multi-identity flag; and displaying the identities corresponding to the account type identifiers used in the bitwise AND operation to the target contact.

[0128] For example, suppose the first identity account is represented as kMultIDTypeDefault, and there are two second identity accounts: kMultIDTypeBusiness and kMultIDTypeOnlineService. When the value of show_multi_id_flag is 0, it means that the id_type used for the AND operation is 0, indicating that only the target user's first identity account is ANDed. Therefore, the target contact terminal only needs to display the target user's first identity account to the target contact. As another example, if the value of show_multi_id_flag is 3, it means that the id_types used for the AND operation are 0x1<<0 and 0x1<<1. id_type 0x1<<0 corresponds to the enterprise identity, and id_type 0x1<<1 corresponds to the online customer service identity. Therefore, the target contact terminal can display the target user's enterprise identity account and online customer service account in the corresponding contact list of the target contact. Specifically, the enterprise identity account can be displayed in the enterprise contact list, and the online customer service account can be displayed in the customer service contact list.

[0129] Optionally, when a target user under a secondary account deletes a target contact, the corresponding group for that target contact will also disappear. Based on the above description, if a target user wants to modify the visibility of any identity to a target contact, they only need to instruct the server to modify the multiple identity markers in the target friend relationship chain between the target user and the target contact.

[0130] The second approach involves storing the account type identifiers of the first and / or second identities on the target friend relationship chain between the target user and the target contact. After obtaining the target friend relationship chain, the target contact's terminal can display all identities corresponding to the account type identifiers stored in the chain to the target contact. Specifically, assuming the target user wants both their first and second identities to be visible to the target contact, the target user's terminal device can instruct the server to store both the account type identifiers of the first and second identities in the target friend relationship chain between the target user and the target contact. In this way, the target contact's terminal can display both the target user's first and second identities to the target contact based on this target friend relationship chain.

[0131] In another embodiment, after the target user successfully adds a target contact to the second identity account, a first target contact group list (i.e., a new contact group list, different from the ordinary contact group list of the first identity account) is displayed on the message receiving interface of the target user's social application to show the user identification information of the added target contact. Simultaneously, a second target contact group list is also displayed on the target contact's social application interface to show the second account identification information of the target user's second identity account. Specifically, the first message receiving interface of the first identity account includes a contact viewing option, such as... Figure 3 As shown in Figure 305, this is the contact viewing option. When the confirmation control in the contact addition interface is triggered, and when the contact viewing option is also triggered, N contact group list items are displayed. These N contact group list items include the first target contact group list item, where N is a positive integer. If the first target contact group list item is triggered, the user identification information of the target contact is displayed in the first target contact group list. This first target contact group list is essentially a separate group specifically for displaying target contacts under the second identity account. This allows the target user to manage contacts under both the first and second identity accounts simultaneously.

[0132] For example, such as Figure 17The diagram shown is an interface diagram of a contact group list disclosed in an embodiment of the present invention. Specifically, when a target user adds a contact to a second identity account, and the target user clicks the contact viewing option 305 in the first message receiving interface 1710, a contact display interface 1720 is displayed. 1720 includes multiple contact group list items, of which 1721 (“Customer”) is the first target contact group list item (i.e., a separate group). If the first target contact group list item is selected, a display area 1722 is displayed, which is mainly used to display the user identification information of the target contact added by the target user to the second identity account.

[0133] Correspondingly, the second target contact group list displayed in the target contact's social application interface shows the second account identifier information of the target user's second identity account. Specifically, when a target contact is successfully added as a target contact under a second identity account by the target user, the target user sends a success message to the server, which then sends the success message to the target contact's terminal. The target contact then knows that they have been added as a target contact under the target user's second identity account. Simultaneously, when the target contact's terminal is active in viewing contacts, the second target contact group list item is displayed, and when the second target contact group list item is triggered, the second account identifier information corresponding to the second identity account is displayed, including the second identity account's avatar and nickname. This second target contact group list is also a separate group specifically for displaying the target user's second identity accounts. A target user can have multiple second identity accounts; that is, a target contact can add different target users' second identity accounts, and the identifier information of each second identity account will be displayed in this second target contact group list.

[0134] For example, such as Figure 18 The diagram shown is an interface illustration of another contact group list disclosed in an embodiment of the present invention. When there is an operation to view contacts on the target contact's terminal, a second target contact group list item is displayed. The second target contact group list item is as follows: Figure 18 As shown in area 1802, when the second target contact group list item 1801 is triggered, the second account identifier information corresponding to the second identity account is displayed.

[0135] As mentioned above, the target user's primary identity account has an account status setting option, and similarly, the target contact's account also has an account status setting option. Therefore, whether the target user can successfully add a target contact under the primary identity account as a target contact under the secondary identity account depends on the selected contact's account status setting option. Specifically, if the confirmation button in the contact addition interface is triggered, and the selected target contact's account status setting option is in the second state, a first prompt message will be displayed in the contact addition interface. This first prompt message informs the target user that the target contact is not allowed to be added as a target contact under the secondary identity account. This first prompt message can be displayed as a pop-up window in the contact addition interface, or it can be displayed in other forms.

[0136] For example, such as Figure 19 The image shown is a schematic diagram of a first notification message disclosed in an embodiment of the present invention. Figure 19 In the contact addition interface 1910, display area 1911 shows the candidate contacts selected from display area 1912. The selected candidate contacts are "User 1" and "User 2". If the account status setting option of "User 1" is in the second state, and the confirmation add control 1913 is triggered, the first prompt message interface 1920 will be displayed. This interface includes the first prompt message 1921. The specific first prompt message can be "User 1's account status option is in the second state, and you are prohibited from adding him as a friend", which is used to inform the target user why he cannot be added.

[0137] In another embodiment, the settings interface also includes an association management option that links a second identity account with an associated application. This is primarily used by the target user to associate a target application with the second identity account, allowing other contacts to initiate conversations with the second identity account through the target application. The target application can be a standalone application or a sub-program, such as a mini-program, running within another application. Specifically, when the target user clicks the association management option, a selection interface for associated applications is displayed, including multiple associated applications linked to the second identity account. When the target application is selected among these multiple applications, its application identifier is displayed in the second identity account's settings interface. The association management option can be a mini-program management option within a social application or an external application management option within a non-social application. If the mini-program management option within a social application is triggered, a list of mini-programs is displayed directly. Selecting a target mini-program associates it with the second identity account. If the external application management option within a non-social application is triggered, the target user packages the source code corresponding to the second identity account and embeds it into the source code of the target application within the external application to achieve the association between the external application and the second identity account. Among them, the association management options for linking a secondary identity account with an associated application can be as follows: Figure 15a The 1504 error code shown includes the "Associate with Mini Program" option and the "Embedded into Other Applications" option.

[0138] As described above, once a target user is associated with a target application, other users can initiate conversations with a second identity account through that application. The relationship between the target user and the target application can be understood as a special pathway. When another user opens a conversation window with the target user through this pathway, the second identity account of the target user and that user's conversation window will be displayed. Here, the other user can be referred to as the first user, who is a non-contact of the target user under the first identity account. Specifically, if the first user initiates a conversation with the target user under the second identity account through the target application, a confirmation interface for adding a new contact will be displayed in the target user's social application interface. This confirmation interface includes an add confirmation option and a second prompt message. The second prompt message indicates that when the add confirmation option is triggered, the first user is added as a target contact under the first identity account, and the second identity account is allowed to receive conversation messages sent by the first user. This can be understood as follows: when a non-contact under the first identity account initiates a conversation to the second identity account through the target associated application, the user's corresponding terminal will by default send a friend request to the target user's first identity account. A confirmation screen for adding a new contact will then be displayed on the target user's first message receiving interface. The confirmation screen includes an add confirmation option and a second prompt message. The second prompt message is used to inform the target user that a non-contact wants to have a conversation with the second identity account. If the target user clicks the confirm option, the non-contact is added as a contact under the first identity account by default, and the user can then have a normal conversation with the target user under the second identity account through the target associated application.

[0139] For example, the second notification message could be like this: Figure 20a The diagram illustrates a second notification message disclosed in an embodiment of the present invention. The target associated application 2010 used by the first user (“earth”) includes an access option 2011 (“XX Customer Service”) for chatting with a second identity account. When the first user clicks access option 2011, a confirmation interface 2021 (displayed as a pop-up window in the target user's first message receiving interface 2020) is displayed. 2022 is the second notification message, and 2023 is the confirmation option. If the target user clicks 2023, the first user has been successfully added as a friend, and a request to open a conversation window between the first user and the target user under the second identity account will be responded to, as shown in 2030. Conversely, if the target user does not click 2023, it is equivalent to the first user failing to add the target user as a friend, and the first user's attempt to open a conversation window with the second identity account fails.

[0140] Correspondingly, in conjunction with the server, the first user initiates a session with the target user under the second identity account through the target-associated application. The corresponding flowchart can be as follows: Figure 20b As shown, the first user on the first user terminal device initiates a session with the second identity account through the target associated application, simultaneously carrying the id_type of the second identity account. The first user terminal device first confirms whether there is a contact relationship between the first user and the target user's first identity account. If so, the session message can be directly forwarded to the first message receiving interface of the first identity account. In the interface corresponding to the user information of the target user's second identity account, the first user can directly initiate a chat session with the second identity account and directly display the session window. For example, if the "Send Session Message" icon displayed in the first user's friend profile card indicates that a chat can be directly initiated with the target user's second identity account, then the identity AIO (i.e., the session window of the second identity account) with the target user will be directly displayed. If there is no contact relationship between the first user and the target user's first identity account, the first user terminal device will initiate a relationship chain establishment request, and the server will receive the relationship chain establishment request. Then, the first identity account corresponding to the second identity account is obtained through `id_type`. A relationship chain between the first identity account and the first user is then established. Correspondingly, a confirmation interface will be displayed in the target user's social application interface for the target user to confirm whether to establish the relationship chain. After the target user confirms, the server updates the first user's relationship chain and returns the updated result to the first user's terminal device. At this point, the first user on the first user's terminal device can initiate a conversation with the second identity account and display a conversation window. For example, if the first user initiates a chat with the target user's second identity through a mini-program channel, a contact relationship needs to be established first, and then the identity AIO with the target user will be displayed. Optionally, during this process, `id_type` will be carried in the conversation message to indicate which identity account corresponding to `id_type` initiated the chat. After receiving the conversation message, the target user will forward the conversation message according to `id_type`. Using this method, when the first user and the target user do not have a contact relationship, a conversation can be initiated by establishing a relationship. In this way, all conversation messages can be recorded in the corresponding relationship chain, and the target user can query and track the conversation messages through the relationship chain.

[0141] In another embodiment, to differentiate between different identity accounts, the display format of the second identity account and the target contact's ordinary friends differs in the message receiving interface after the second identity account is successfully added as a target contact. Specifically, when the target user enters a conversation message in the conversation window between the target contact and the target user under the second identity account, a first conversation identifier is displayed in the message receiving interface corresponding to the target contact account. The first conversation identifier carries a target tag, which is a special identifier that can be used to indicate that the target user is having a conversation with the target contact using the second identity account. The target contact account is the user account applied for by the target contact in the social application, and the target tag can also indicate the function of the second identity account. If it is an enterprise account, an enterprise account tag is displayed; if it is an educational account, an educational account tag is displayed. On the server, this can be understood as the target contact terminal device requesting a target tag (icon) from the server when id_type is not 0, so that the target contact terminal device can display the second identity account based on the target tag. Optionally, the display style of the target tag can also be dynamically controlled for convenient subsequent operation, that is, the server sends multiple tags to the terminal device, and the target contact terminal device selects and displays them according to its needs.

[0142] For example, the target label can be like Figure 21 The diagram shown is a schematic representation of a second account identification information disclosed in an embodiment of the present invention. In the message receiving interface of the target contact, the second account identification information 2101 of the second identity account is displayed. Correspondingly, 2102 is the target tag, indicating... Figure 21 The "XX Customer Service" in the text is an "Enterprise Account".

[0143] In another embodiment, the second identity account's settings interface or the second identity account creation success interface displays a QR code identifier for the second identity account. The QR code identifier can be as follows: Figure 12 In the successful creation interface 1240, 1241 can also be like... Figure 15a The settings interface shown in the image (1506) displays a QR code when the QR code identification information is triggered. The QR code is primarily used to store the account identification information of the secondary account, which can be displayed to other users, allowing them to add the secondary account. It's important to note that the QR code for the secondary account is different from the QR code for the primary account.

[0144] In yet another embodiment, the settings interface for the second identity account also includes a smart conversation message management option, such as... Figure 15aAs shown in 1502, the content of the smart conversation messages differs for different secondary identity accounts. For example, for a customer service enterprise account, the smart conversation messages may include greetings and self-service Q&A. When the target user clicks the smart conversation management option, the smart conversation management interface is displayed, where the user can customize and edit the smart conversation messages.

[0145] S904. When a target contact under a second identity account sends a target session message to the second identity account, the first message receiving interface corresponding to the first identity account is displayed. The first message receiving interface includes a target type session message identifier, which is used to indicate the target session message.

[0146] S905. When the target type session identifier is selected, the second message receiving interface of the target user under the second identity account is displayed, and the session window identifier of the conversation between the target user under the second identity account and the target contact is displayed on the second message receiving interface.

[0147] S906. When the session window identifier is triggered, the session window of the target user under the second identity account and the target contact is displayed, and the target session message is displayed in the session window.

[0148] In one embodiment, some feasible implementation methods included in steps S904 to S906 can be found in [reference needed]. Figure 2 The descriptions of the relevant steps in the embodiments will not be repeated here.

[0149] In one embodiment, the conversation window between the target contact and the target user under the second identity account includes a conversation message editing area and a conversation message display area. The conversation message editing area is used by the user to edit the conversation message to be sent, and the conversation message display area is used to display the conversation messages sent by the target contact and the target user. Specifically, the conversation message editing area includes a quick reply option. If the quick reply option is selected, a list of quick reply information is displayed in the conversation message editing area. The quick reply information list includes multiple quick reply information, mainly used by the target user to quickly reply to the target conversation message sent by the target contact. Furthermore, when a target quick reply information is selected in the quick reply information list, the target quick reply information is displayed in the conversation message area. Optionally, the quick reply information list also includes a settings option. The target user can click the settings option to customize and edit the quick reply information, which may include operations such as deleting, adding, or modifying quick reply information.

[0150] For example, this embodiment can be specifically as follows: Figure 22The diagram illustrates a quick reply method disclosed in an embodiment of the present invention. The conversation window 2210 includes a conversation message display area 2211 and a conversation message editing area 2212. The conversation message editing area 2212 includes a quick reply option 2213. When the user clicks the quick reply option 2213, the user is redirected to a new conversation window 2220. The new conversation window 2220 includes a quick reply information list 2222 and a conversation message display area 2221. When a target quick reply information 2223 in the quick reply information list 2222 is selected, the target quick reply information is displayed in the conversation message display area 2221, as shown by 2224 in 2221.

[0151] In another embodiment, to prevent the target contact from being disturbed by frequent chat messages, the time for sending messages from the second identity account can be limited. For example, in an enterprise scenario, it can be set that if the other party does not send a message actively for 48 hours, the user cannot chat with them to avoid harassment. The specific implementation process can be as follows: During a conversation between the target user (under the second identity account) and the target contact, if the target user enters any conversation message and the target contact does not respond within a preset time, a third prompt message is displayed in the conversation window. This third prompt message indicates that the target user is not allowed to enter new conversation messages in the conversation window. This can be understood as a preset time period, which developers can customize, such as 24 hours, 48 ​​hours, etc. If the target user sends a conversation message to the target contact and the target contact does not reply within the preset time, the target user is muted, meaning the target user cannot actively send conversation messages to the target contact in the conversation window. The third prompt message can be displayed in the conversation window or as a pop-up message box when the target user enters a conversation message.

[0152] For example, Figure 23a This is a schematic diagram of a third notification message disclosed in an embodiment of the present invention. Figure 23a In the session window shown, if the server detects that the target contact has not sent a feedback message to the target user within 48 hours, a third prompt message is displayed in the session window accordingly. The third prompt message is as follows: Figure 23a The example shown is 2301, which states, "The other party has not sent a message for more than 48 hours, and the enterprise account cannot proactively contact this user." In this case, the target user can no longer send new conversation messages to the target contact. Figure 23a This is merely an example illustration of a third-party notification message; the third-party notification message can also be displayed in other forms.

[0153] Correspondingly, when the server implements the display of the third prompt message, the main task performed by the server is to determine the time. When the server determines that the session window is the session window of the target user and the target contact under the second identity account based on the id_type, it determines the time when the target contact last sent a message. If it has not been sent for more than a preset time (such as 48 hours), then when the target user sends a session message to the target contact again, the server returns a message of sending failure to the target user's terminal device and displays the third prompt message in the session window.

[0154] Optionally, the server can determine whether the target user has opened a regular chat window (regular AIO, i.e., a chat window where the target user is using their primary identity account and contacts) or an identity-based chat window (identity-based AIO, i.e., a chat window where the target user is using their secondary identity account and contacts) based on the id_type. The corresponding server process is as follows: Figure 23b As shown, the server receives a request to open a chat window and determines the type of chat window the target user wants to open by checking the `id_type`. If `id_type` is 0, a normal chat window is opened; if `id_type` is not 0, an identity-based chat window is opened. Here, AIO, or All-In-One, refers to the common chat window component. In the QQ application terminal version, when users participate in various types of conversations such as friends, groups, and public accounts, the software provides a shared chat window component for different conversations to provide a consistent interactive experience. The user's input, click operations, and other behavioral habits within this component can be considered consistent. In the chat window of a second identity account (multiple identity accounts other than the first identity account), the target user can customize some special functions, such as setting a quick reply function (e.g., ...). Figure 22 As shown), disable the function of sending session messages (such as...). Figure 23a As shown), the function to view customer information is disabled (e.g. Figure 24 (as shown), etc.

[0155] In another embodiment, to protect the privacy of the target contact, when a target user under the second identity account clicks on the target contact's account identifier information in the conversation window, the server does not allow the target user to view the target contact's user information. Specifically, in the conversation window between the target user under the second identity account and the target contact, when the target user clicks on the target contact's account identifier information, a fourth prompt message is displayed. This fourth prompt message is mainly used to inform the target user under the second identity account that viewing the target contact's user information is not allowed. This method can protect the target contact's user information and prevent the target contact from being harassed. The target contact's account identifier information can be an image identifier, such as the target contact's avatar, or a text identifier, such as the target contact's nickname. Figure 6 The number 611 shown is the target contact's profile picture, and 612 is the target contact's nickname.

[0156] For example, the fourth notification message could be like this: Figure 24 As shown, Figure 24 This is a schematic diagram of a fourth prompt message disclosed in an embodiment of the present invention. When the target user clicks on the account identification information 611 or 612 of the target contact in the conversation window 2410, a new conversation window 2420 is displayed. The new conversation window 2420 is covered by a prompt interface 2421 for displaying the fourth prompt message. The prompt interface 2421 can be displayed in the form of a pop-up window. The fourth prompt message can specifically be "You are communicating with the other party as an enterprise and cannot view the other party's profile card", thereby avoiding the problem of the target contact being disturbed.

[0157] In another embodiment, since the first identity account and the second identity account are different identity accounts, the user information of the second identity account is also different from that of the first identity account. Specifically, viewing the user information of the second identity account involves the following: In the conversation window between the target user and the target contact under the second identity account, if the target contact selects the second account identifier information of the second identity account, the user information of the second identity account is displayed. The user information of the second identity account is displayed on the user information display interface, and it differs from that of the first identity account. The second account identifier information of the second identity account can be either the avatar or the nickname of the second identity account. Optionally, the target contact can also view the user information of the second identity account through the second account identifier information displayed in the aforementioned second target contact group list.

[0158] For example, such as Figure 25aThe diagram illustrates user information for a second identity account. When the target contact clicks on the second account identifier information 2511 or 2512 of the second identity account in the conversation window 2510, the user information display interface 2520 of the second identity account is displayed, in which area 2521 displays the user information of the second identity account.

[0159] Optionally, non-target contacts can also view the secondary identity account's user information through other means, such as friend referrals or related contacts. In this case, if a non-target contact wants to add the secondary identity account as a contact, they can click [the link / click]. Figure 25a The interface shown in section 2520 uses the option 2522 "Add as Enterprise Friend" to add a secondary identity account.

[0160] Based on the above description, combining the server and contact terminal device (which can be such as...) Figure 1 The flowchart shown for terminal device 101) obtaining user information can be as follows: Figure 25b The flowchart illustrates the process when a contact wants to view the target user's information during a conversation. When chatting with the target user (including a primary identity account and other multiple identity accounts such as a secondary identity account), the contact can click on an icon (e.g., an avatar) to view the corresponding identity's user information. This user information includes detailed information for that identity. When the contact clicks the target user's icon on their terminal device, the server receives a user information retrieval request from the terminal device. It first determines if the identity account corresponding to the icon belongs to a new number segment. If so, it retrieves and assembles the data for the secondary identity account. If the identity account does not belong to a new number segment, it retrieves and assembles the data for the primary identity account. Regardless of the situation, the server retrieves the corresponding `id_type` based on the identity number, then reassembles the `id_type` with the assembled data to obtain the complete user information for that identity account. This complete user information is then sent to the contact terminal device. The contact terminal device displays the corresponding user information based on the returned result and the different `id_type` values.

[0161] In this embodiment of the invention, the identity account management interface in the social application includes a new identity account creation option. When the new identity account creation option is triggered, a new identity account creation interface is displayed. The new identity account creation interface includes an account identification information setting area and a confirmation creation control. If the confirmation creation control is triggered, a successful creation interface for the second identity account for the target user is displayed, indicating that the second identity account has been successfully created. After the second identity account is successfully created, the target user can further configure the second identity account to enhance its functionality. Simultaneously, when a target contact under the second identity account sends a target conversation message to the second identity account, a first message receiving interface corresponding to the first identity account is displayed. The first message receiving interface includes a target type conversation message identifier, which indicates the target conversation message. When the target type conversation identifier is selected, a second message receiving interface for the target user under the second identity account is displayed, along with a conversation window identifier indicating a conversation between the target user and the contact. When the conversation window identifier is triggered, a conversation window for a conversation between the target user and the target contact under the second identity account is displayed, and the target conversation message is displayed in the conversation window. This method allows for the creation of multiple user accounts and effectively improves user management of conversation messages across these accounts. Displaying conversation messages from different user accounts in separate conversation windows protects user privacy while enhancing management efficiency.

[0162] Based on the above method embodiments, this invention also provides a schematic diagram of the structure of a message display device. See also... Figure 26 This is a schematic diagram of the structure of a message display device provided in an embodiment of the present invention. Figure 26 The message display device 2600 shown can operate the following units:

[0163] Display unit 2601 is used to display a first message receiving interface corresponding to the first identity account. The first message receiving interface includes a target type session message identifier. The target type session message identifier is used to indicate that there is a target contact in the second identity account sending a target session message to the target user. The target contact is a contact under the second identity account. The first identity account is a user account applied for by the target user in the social application with a first identity. The second identity account is a user account applied for by the target user in the social application with a second identity.

[0164] The display unit 2601 is further configured to display the second message receiving interface corresponding to the second identity account when the target type session message identifier is selected, and to display the session window identifier of the target user under the second identity account having a session with the target contact on the second message receiving interface;

[0165] The display unit 2601 is further configured to display a conversation window between the target user and the target contact under the second identity account when the conversation window identifier is triggered, and to display the target conversation message in the conversation window.

[0166] In one embodiment, the display unit 2601 is further configured to:

[0167] The social application displays an identity account management interface, which includes options for creating new identity accounts.

[0168] When the option to create a new identity account is triggered, the interface for creating a new identity account is displayed. The interface for creating a new identity account includes an area for setting account identification information and a confirmation control for creation.

[0169] If the confirmation creation control is triggered, a creation success interface for the second identity account created for the target user will be displayed, and the second account identifier information corresponding to the second identity account will be displayed on the creation success interface. The second account identifier information corresponding to the second identity account is the information entered in the account identifier information setting area.

[0170] In one embodiment, the second account identifier information corresponding to the second identity account includes an image identifier, and the display unit 2601 is further configured to:

[0171] The image identifier included in the second account identifier information is displayed on the identity account management interface;

[0172] If the image identifier is selected, the settings interface of the second identity account is displayed, and the settings interface includes an identity account deletion control;

[0173] When the identity account deletion control is triggered, the second identity account is deleted.

[0174] In one embodiment, the settings interface further includes contact management options, and the display unit 2601 is further configured to:

[0175] If the contact management option is selected, the contact management interface is displayed, which includes a contact addition control;

[0176] When the contact addition control is triggered, a contact addition interface is displayed. The contact addition interface includes a first display area and a second display area. The first display area is used to display the user identification information of multiple candidate contacts, which are contacts under the first identity account. The second display area is used to display the user identification information of the selected target contact among the multiple candidate contacts.

[0177] If the confirmation control in the contact addition interface is triggered, the user identification information of the target contact in the second display area will be displayed in the contact management interface.

[0178] In one embodiment, the first message receiving interface includes a contact viewing option; after the confirmation add control in the contact add interface is triggered, the display unit 2601 is further configured to:

[0179] When the contact viewing option is triggered, N contact group list items are displayed, including the first target contact group list item, where N is a positive integer;

[0180] If the first target contact group list item is triggered, the user identification information of the target contact will be displayed.

[0181] In one embodiment, the message display device further includes a sending unit 2602, which is configured to notify the target contact terminal that the target contact has been added as a contact of the target user under the second identity account if the confirmation add control in the contact add interface is triggered, so as to indicate that when there is an operation to view contacts in the target contact terminal, the second target contact group list item is displayed, and when the second target contact group list item is triggered, the second user identification information corresponding to the second identity account is displayed.

[0182] In one embodiment, the identity account management interface further includes an account status setting option, and the method further includes:

[0183] The identity account management interface also includes an account status setting option. When the account status setting option is in the first state, the target user is allowed to be added by any contact as a contact of any contact under other identity accounts. Any contact refers to the target user's contact under the first identity account. The identity account type of the other identity account corresponding to any contact is different from the identity account type of the first identity account.

[0184] When the account status setting option is in the second state, the target user is not allowed to be added as a contact of any contact under any other identity account.

[0185] In one embodiment, the display unit 2601 is further configured to:

[0186] If the confirmation add control in the contact add interface is triggered, and the account status setting option corresponding to the target contact is in the second state, a first prompt message is displayed. The first prompt message is used to prompt that the target contact is not allowed to be added as a contact under the second identity account by the target user.

[0187] In one embodiment, the settings interface further includes an association management option for associating the second identity account with an associated application, and the display unit 2601 is further configured to:

[0188] If the association management option is triggered, a selection interface for associated applications is displayed, which includes multiple associated applications associated with the second identity account;

[0189] When a target associated application is selected among the multiple associated applications, the application identifier of the target associated application is displayed in the settings interface of the second identity account.

[0190] In one embodiment, the display unit 2601 is further configured to:

[0191] If the first user initiates a conversation with the target user under the second identity account through the target associated application, a confirmation interface for adding a contact is displayed. The first user is a non-contact of the target user under the first identity account. The confirmation interface includes an add confirmation option and a second prompt message. The second prompt message indicates that when the add confirmation option is triggered, the first user is added as a contact under the first identity account, and the second identity account is allowed to receive conversation messages sent by the first user.

[0192] In one embodiment, the display unit 2601 is further configured to:

[0193] During a conversation between the target user and the target contact under the second identity account, if the target user enters any conversation message during the conversation and the target contact does not generate a conversation message within a preset time, a third prompt message is displayed in the conversation window. The third prompt message is used to indicate that the target user is not allowed to enter new conversation messages in the conversation window.

[0194] In one embodiment, the session window includes the account identification information of the target contact, and the display unit 2601 is further configured to:

[0195] In the conversation window where the target user under the second identity account is having a conversation with the target contact, if the account identification information of the target contact is triggered, a fourth prompt message is displayed. The fourth prompt message is used to prompt the target user under the second identity account that they are not allowed to view the user information of the target contact.

[0196] In one embodiment, the display unit 2601 is further configured to:

[0197] In the conversation window where the target user under the second identity account is having a conversation with the target contact, when the target user enters a conversation message, if the target contact's terminal displays the message receiving interface corresponding to the target contact's account, then a first conversation identifier is displayed on the message receiving interface corresponding to the target contact's account. The first conversation identifier carries a target tag, which is used to indicate that the target user is having a conversation with the target contact using the second identity account. The target contact's account is the user account that the target contact applied for in the social application.

[0198] In one embodiment, after the target contact sends the target session message to the target user, the display unit 2601 is further configured to:

[0199] When the target contact creates a session between the target contact and the target user under the second identity account, a smart session message is displayed in the session window between the target contact and the target user. The smart session message is entered by the target user using the second identity account and is set through the smart session message settings interface. The smart session message settings interface is displayed when the smart session message management option of the settings interface is triggered.

[0200] In one embodiment, if the confirmation creation control is triggered, displaying the settings interface of the second identity account includes:

[0201] The sending unit 2602 is used to send a creation request for creating a new identity account to the server if the confirmation creation control is triggered. The creation request includes an account type identifier to which the new identity account belongs. The creation request is used to instruct the server to allocate the second identity account to the target user and return the interface display indication information corresponding to the type to which the new identity account belongs.

[0202] The display unit 2601 is used to display the settings interface based on the interface display instruction information returned by the server and the information entered in the account identification area.

[0203] In one embodiment, the relationship between any candidate contact and the target user is maintained through a friend relationship chain, which includes the account type to which the first identity account belongs; if the confirmation add control in the contact add interface is triggered, the user identification information of the target contact in the second display area is displayed in the contact management interface, including:

[0204] The sending unit 2602 is used to send an add request to the server if the confirm add control in the contact add interface is triggered. The add request carries the account type to which the second identity account belongs. The add request is used to instruct the server to update the target friend relationship chain between the target user and the target contact according to the type to which the second identity account belongs and return the update result, so that when the target contact terminal displays the contact list item of the target contact based on the target friend relationship chain, the target user is displayed in the contact list item associated with the second identity account.

[0205] The display unit 2601 is used to display the user identification information of the target contact in the second display area on the contact management interface in response to the update result returned by the server.

[0206] In one implementation, the sending unit 2602 is further configured to, during a conversation between the target user under the second identity account and the target contact, send a conversation message sending request to the server when the target user enters any conversation message in the conversation window. The conversation message sending request is used to instruct the server to detect whether the version information of the social application in the target contact's terminal is preset version information and return a request response notification.

[0207] The display unit 2601 is configured to display any of the conversation messages in the conversation window if the request response notification sent by the server indicates that the version information of the social application in the target contact terminal is the preset version information.

[0208] The sending unit 2602 is further configured to output a fifth prompt message if the request response notification sent by the server indicates that the version information of the social application in the target contact terminal is not the preset version information. The fifth prompt message is used to indicate that the sending of any session message has failed.

[0209] According to one embodiment of this application, Figure 2 as well as Figure 9 The steps involved in the message display method shown can be derived from... Figure 26 The message display device shown is executed by each unit within it. For example, Figure 2 In the message display method shown, steps S201-S203 can be performed by... Figure 26 The message display device shown uses the display unit 2601 to perform the operation; for example, Figure 9 In the message display method shown, steps S901-S906 can be performed by... Figure 26 The message display device shown uses the display unit 2601 to perform the operation.

[0210] According to another embodiment of this application, Figure 26 The various units in the message display device shown can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above-mentioned units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the message display device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0211] According to another embodiment of this application, the following can be achieved by running on a general-purpose computing device, such as a computer, which includes processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), a device capable of performing operations such as... Figure 2 as well as Figure 9 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 26 The message display device shown herein, and the message display method for implementing embodiments of the present invention, are described. The computer program may be recorded on, for example, a computer-readable storage medium, loaded onto the aforementioned computing device via the computer-readable storage medium, and run therein.

[0212] In this embodiment of the invention, a first message receiving interface corresponding to a first identity account is displayed. The first message receiving interface includes a target type session message identifier, which indicates that a target contact in a second identity account is sending a target session message to a target user. When the target type session identifier is selected, a second message receiving interface for the target user under the second identity account is displayed. A session window identifier indicating a conversation between the target user and the target contact under the second identity account is also displayed on the second message receiving interface. When the session window identifier is triggered, a session window indicating a conversation between the target user and the target contact under the second identity account is displayed, and the target session message is displayed in the session window. By using the target type session message identifier to distinguish messages received by different identity accounts, efficient management of session messages under multiple accounts is achieved without switching accounts. Specifically, it can be understood that the multiple identities of a target user will generate separate message nodes in the message receiving interface of the first identity account. Session messages sent to the second identity account are all collected in this message node, and the target user does not need to switch identities, making message reception more convenient.

[0213] Based on the above methods and apparatus embodiments, this invention provides a terminal device. See also... Figure 27 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. Figure 27 The terminal device 2700 shown includes at least a processor 2701, an input interface 2702, an output interface 2703, a computer storage medium 2704, and a memory 2705. The processor 2701, input interface 2702, output interface 2703, computer storage medium 2704, and memory 2705 can be connected via a bus or other means.

[0214] The computer storage medium 2704 can be stored in the memory 2705 of the terminal device 2700. The computer storage medium 2704 is used to store computer programs, which include one or more computer programs. The processor 2701 is used to execute the one or more computer programs stored in the computer storage medium 2704. The processor 2701 (or CPU (Central Processing Unit)) is the computing and control core of the terminal device 2700. It is suitable for implementing one or more computer programs, specifically for loading and executing one or more computer programs to achieve corresponding method flows or corresponding functions.

[0215] This invention also provides a computer storage medium (memory), which is a memory device in a terminal device used to store programs and data. It is understood that the computer storage medium here can include both the built-in storage medium in the terminal device and extended storage media supported by the terminal device. The computer storage medium provides storage space, which stores the operating system of the terminal device. Furthermore, this storage space also stores one or more computer programs (including program code) suitable for loading and execution by the processor 2701. It should be noted that the computer storage medium here can be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer storage medium located remotely from the aforementioned processor.

[0216] In one embodiment, the computer storage medium may be loaded and executed by the processor 2701, along with one or more computer programs stored in the computer storage medium, to achieve the aforementioned related functions. Figure 2 as well as Figure 9 The corresponding steps of the message display method are shown. In specific implementation, one or more computer programs in the computer storage medium are loaded by the processor 2701 and executed as follows:

[0217] The first message receiving interface corresponding to the first identity account is displayed. The first message receiving interface includes a target type session message identifier. The target type session message identifier is used to indicate that there is a target contact in the second identity account to send a target session message to the target user. The target contact is a contact under the second identity account. The first identity account is a user account applied for by the target user in the social application with a first identity. The second identity account is a user account applied for by the target user in the social application with a second identity.

[0218] When the target type session message identifier is selected, the second message receiving interface corresponding to the second identity account is displayed, and the session window identifier of the conversation between the target user under the second identity account and the target contact is displayed on the second message receiving interface.

[0219] When the session window identifier is triggered, a session window is displayed showing the conversation between the target user and the target contact under the second identity account, and the target session message is displayed in the session window.

[0220] In one embodiment, the processor 2701 is further configured to:

[0221] The social application displays an identity account management interface, which includes options for creating new identity accounts.

[0222] When the option to create a new identity account is triggered, the interface for creating a new identity account is displayed. The interface for creating a new identity account includes an area for setting account identification information and a confirmation control for creation.

[0223] If the confirmation creation control is triggered, a creation success interface for the second identity account created for the target user will be displayed, and the second account identifier information corresponding to the second identity account will be displayed on the creation success interface. The second account identifier information corresponding to the second identity account is the information entered in the account identifier information setting area.

[0224] In one embodiment, the second account identifier information corresponding to the second identity account includes an image identifier, and the processor 2701 is further configured to:

[0225] The image identifier included in the second account identifier information is displayed on the identity account management interface;

[0226] If the image identifier is selected, the settings interface of the second identity account is displayed, and the settings interface includes an identity account deletion control;

[0227] When the identity account deletion control is triggered, the second identity account is deleted.

[0228] In one embodiment, the settings interface further includes contact management options, and the processor 2701 is further configured to:

[0229] If the contact management option is selected, the contact management interface is displayed, which includes a contact addition control;

[0230] When the contact addition control is triggered, a contact addition interface is displayed. The contact addition interface includes a first display area and a second display area. The first display area is used to display the user identification information of multiple candidate contacts, which are contacts under the first identity account. The second display area is used to display the user identification information of the selected target contact among the multiple candidate contacts.

[0231] If the confirmation control in the contact addition interface is triggered, the user identification information of the target contact in the second display area will be displayed in the contact management interface.

[0232] In one embodiment, the first message receiving interface includes a contact viewing option; after the confirmation add control in the contact add interface is triggered, the processor 2701 is further configured to:

[0233] When the contact viewing option is triggered, N contact group list items are displayed, including the first target contact group list item, where N is a positive integer;

[0234] If the first target contact group list item is triggered, the user identification information of the target contact will be displayed.

[0235] In one embodiment, the processor 2701 is further configured to:

[0236] If the confirmation add control in the contact add interface is triggered, the target contact terminal is notified that the target contact has been added as a contact of the target user under the second identity account. This indicates that when there is a contact viewing operation in the target contact terminal, the second target contact group list item is displayed, and when the second target contact group list item is triggered, the second user identification information corresponding to the second identity account is displayed.

[0237] In one embodiment, the identity account management interface further includes an account status setting option, and the method further includes:

[0238] The identity account management interface also includes an account status setting option. When the account status setting option is in the first state, the target user is allowed to be added by any contact as a contact of any contact under other identity accounts. Any contact refers to the target user's contact under the first identity account. The identity account type of the other identity account corresponding to any contact is different from the identity account type of the first identity account.

[0239] When the account status setting option is in the second state, the target user is not allowed to be added as a contact of any contact under any other identity account.

[0240] In one embodiment, the processor 2701 is further configured to:

[0241] If the confirmation add control in the contact add interface is triggered, and the account status setting option corresponding to the target contact is in the second state, a first prompt message is displayed. The first prompt message is used to prompt that the target contact is not allowed to be added as a contact under the second identity account by the target user.

[0242] In one embodiment, the settings interface further includes an association management option for associating the second identity account with an associated application, and the processor 2701 is further configured to:

[0243] If the association management option is triggered, a selection interface for associated applications is displayed, which includes multiple associated applications associated with the second identity account;

[0244] When a target associated application is selected among the multiple associated applications, the application identifier of the target associated application is displayed in the settings interface of the second identity account.

[0245] In one embodiment, the processor 2701 is further configured to:

[0246] If the first user initiates a conversation with the target user under the second identity account through the target associated application, a confirmation interface for adding a contact is displayed. The first user is a non-contact of the target user under the first identity account. The confirmation interface includes an add confirmation option and a second prompt message. The second prompt message indicates that when the add confirmation option is triggered, the first user is added as a contact under the first identity account, and the second identity account is allowed to receive conversation messages sent by the first user.

[0247] In one embodiment, the processor 2701 is further configured to:

[0248] During a conversation between the target user and the target contact under the second identity account, if the target user enters any conversation message during the conversation and the target contact does not generate a conversation message within a preset time, a third prompt message is displayed in the conversation window. The third prompt message is used to indicate that the target user is not allowed to enter new conversation messages in the conversation window.

[0249] In one embodiment, the session window includes the account identification information of the target contact, and the processor 2701 is further configured to:

[0250] In the conversation window where the target user under the second identity account is having a conversation with the target contact, if the account identification information of the target contact is triggered, a fourth prompt message is displayed. The fourth prompt message is used to prompt the target user under the second identity account that they are not allowed to view the user information of the target contact.

[0251] In one embodiment, the processor 2701 is further configured to:

[0252] In the conversation window where the target user under the second identity account is having a conversation with the target contact, when the target user enters a conversation message, if the target contact's terminal displays the message receiving interface corresponding to the target contact's account, then a first conversation identifier is displayed on the message receiving interface corresponding to the target contact's account. The first conversation identifier carries a target tag, which is used to indicate that the target user is having a conversation with the target contact using the second identity account. The target contact's account is the user account that the target contact applied for in the social application.

[0253] In one embodiment, after the target contact sends the target session message to the target user, the processor 2701 is further configured to:

[0254] When the target contact creates a session between the target contact and the target user under the second identity account, a smart session message is displayed in the session window between the target contact and the target user. The smart session message is entered by the target user using the second identity account and is set through the smart session message settings interface. The smart session message settings interface is displayed when the smart session message management option of the settings interface is triggered.

[0255] In one embodiment, if the confirmation creation control is triggered, the processor 2701 is used to display the settings interface of the second identity account, including:

[0256] If the confirmation creation control is triggered, a creation request for creating a new identity account is sent to the server. The creation request includes an account type identifier to which the new identity account belongs. The creation request is used to instruct the server to assign the second identity account to the target user and return the interface display instruction information corresponding to the type to which the new identity account belongs.

[0257] The settings interface is displayed based on the interface display instructions returned by the server and the information entered in the account identifier area.

[0258] In one embodiment, any candidate contact and the target user are maintained through a friend relationship chain, which includes the account type to which the first identity account belongs; if the confirmation add control in the contact add interface is triggered, the user identification information of the target contact in the second display area is displayed in the contact management interface, and the processor 2701 is further configured to:

[0259] If the confirmation add control in the contact add interface is triggered, an add request is sent to the server. The add request carries the account type to which the second identity account belongs. The add request is used to instruct the server to update the target friend relationship chain between the target user and the target contact according to the type to which the second identity account belongs and return the update result, so that when the target contact terminal displays the contact list item of the target contact based on the target friend relationship chain, the target user is displayed in the contact list item associated with the second identity account.

[0260] In response to the update result returned by the server, the user identification information of the target contact in the second display area is displayed in the contact management interface.

[0261] In one implementation, the processor 2701 is further configured to:

[0262] During a conversation between the target user and the target contact under the second identity account, when the target user enters any conversation message in the conversation window, a conversation message sending request is sent to the server. The conversation message sending request is used to instruct the server to detect whether the version information of the social application in the target contact's terminal is the preset version information and return a request response notification.

[0263] If the request response notification sent by the server indicates that the version information of the social application in the target contact terminal is the preset version information, then any of the conversation messages will be displayed in the conversation window;

[0264] If the request response notification sent by the server indicates that the version information of the social application in the target contact terminal is not the preset version information, then a fifth prompt message is output, which is used to indicate that any session message has failed to be sent.

[0265] In this embodiment of the invention, the processor 2701 is configured to display a target type session message identifier on the first message receiving interface corresponding to the first identity account, indicating that a target contact in the second identity account is sending a target session message to a target user. When the target type session message identifier is selected, the processor displays the second message receiving interface corresponding to the second identity account, and displays a session window identifier indicating that the target user under the second identity account is having a session with the target contact. Furthermore, when the session window identifier is triggered, the processor displays the session window indicating that the target user under the second identity account is having a session with the target contact, and displays the target session message in the session window. This method distinguishes the session messages received by the first identity account and the second identity account through the target type session message identifier. This method can effectively improve the user's management of session messages across multiple identity accounts. Displaying session messages from different identity accounts in different session windows protects user privacy and improves management efficiency.

[0266] According to one aspect of this application, embodiments of the present invention also provide a computer product including a computer program stored in a computer-readable storage medium. A processor 2701 reads the computer program from the computer-readable storage medium and executes the computer program, causing a computer device 2700 to perform... Figure 2 as well as Figure 9 The message display method shown.

[0267] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0268] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, and the division of modules described above is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0269] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A message display method, characterized in that, The method includes: The first message receiving interface corresponding to the first identity account is displayed. The first message receiving interface includes a target type session message identifier. The target type session message identifier is used to indicate that there is a target contact in the second identity account to send a target session message to the target user. The target contact is a contact under the second identity account. The first identity account is a user account applied for by the target user in the social application with a first identity. The second identity account is a user account applied for by the target user in the social application with a second identity. When the target type session message identifier is selected, the second message receiving interface corresponding to the second identity account is displayed, and the session window identifier of the conversation between the target user under the second identity account and the target contact is displayed on the second message receiving interface. When the conversation window identifier is triggered, a conversation window is displayed between the target user under the second identity account and the target contact, and the target conversation message is displayed in the conversation window; After the target contact sends the target session message to the target user, when the target contact creates a session between the target contact and the target user under the second identity account, a smart session message is displayed in the session window between the target contact and the target user. The smart session message is entered by the target user using the second identity account, and includes a prediction question related to the second identity or the second identity account. The smart session message is set through the smart session message settings interface, which is displayed when the smart session message management option in the settings interface of the second identity account is triggered.

2. The method as described in claim 1, characterized in that, The method further includes: The social application displays an identity account management interface, which includes options for creating new identity accounts. When the option to create a new identity account is triggered, the interface for creating a new identity account is displayed. The interface for creating a new identity account includes an area for setting account identification information and a confirmation control for creation. If the confirmation creation control is triggered, a creation success interface for the second identity account created for the target user will be displayed, and the second account identifier information corresponding to the second identity account will be displayed on the creation success interface. The second account identifier information corresponding to the second identity account is the information entered in the account identifier information setting area.

3. The method as described in claim 2, characterized in that, The second account identifier information corresponding to the second identity account includes an image identifier, and the method further includes: The image identifier included in the second account identifier information is displayed on the identity account management interface; If the image identifier is selected, the settings interface of the second identity account is displayed, which includes an identity account deletion control. When the identity account deletion control is triggered, the second identity account is deleted.

4. The method as described in claim 3, characterized in that, The settings interface for the second identity account also includes a contact management option, and the method further includes: If the contact management option is selected, the contact management interface is displayed, which includes a contact addition control; When the contact addition control is triggered, a contact addition interface is displayed. The contact addition interface includes a first display area and a second display area. The first display area is used to display the user identification information of multiple candidate contacts, which are contacts under the first identity account. The second display area is used to display the user identification information of the selected target contact among the multiple candidate contacts. If the confirmation control in the contact addition interface is triggered, the user identification information of the target contact in the second display area will be displayed in the contact management interface.

5. The method as described in claim 4, characterized in that, The first message receiving interface includes a contact viewing option; after the confirmation add control in the contact add interface is triggered, the method further includes: When the contact viewing option is triggered, N contact group list items are displayed, including the first target contact group list item, where N is a positive integer; If the first target contact group list item is triggered, the user identification information of the target contact will be displayed.

6. The method as described in claim 4, characterized in that, The method further includes: If the confirmation add control in the contact add interface is triggered, the target contact terminal is notified that the target contact has been added as a contact of the target user under the second identity account. This indicates that when there is a contact viewing operation in the target contact terminal, the second target contact group list item is displayed, and when the second target contact group list item is triggered, the second user identification information corresponding to the second identity account is displayed.

7. The method as described in claim 2, characterized in that, The identity account management interface also includes account status settings options, and the method further includes: The identity account management interface also includes an account status setting option. When the account status setting option is in the first state, the target user is allowed to be added by any contact as a contact of any contact under other identity accounts. Any contact refers to the target user's contact under the first identity account. The identity account type of the other identity account corresponding to any contact is different from the identity account type of the first identity account. When the account status setting option is in the second state, the target user is not allowed to be added as a contact of any contact under any other identity account.

8. The method as described in claim 7, characterized in that, The method further includes: If the confirmation add control in the contact add interface is triggered, and the account status setting option corresponding to the target contact is in the second state, a first prompt message is displayed. The first prompt message is used to prompt that the target contact is not allowed to be added as a contact under the second identity account by the target user.

9. The method as described in claim 3, characterized in that, The settings interface for the second identity account also includes an association management option for associating the second identity account with associated applications, and the method further includes: If the association management option is triggered, a selection interface for associated applications is displayed, which includes multiple associated applications associated with the second identity account; When a target associated application is selected among the multiple associated applications, the application identifier of the target associated application is displayed in the settings interface of the second identity account.

10. The method as described in claim 9, characterized in that, The method further includes: If the first user initiates a conversation with the target user under the second identity account through the target associated application, a confirmation interface for adding a new contact is displayed, where the first user is a non-contact of the target user under the first identity account; The confirmation interface for adding a new contact includes an add confirmation option and a second prompt message; the second prompt message indicates that when the add confirmation option is triggered, the first user is added as a contact under the first identity account, and the second identity account is allowed to receive conversation messages sent by the first user.

11. The method as described in claim 1, characterized in that, The method further includes: During a conversation between the target user and the target contact under the second identity account, if the target user enters any conversation message during the conversation and the target contact does not generate a conversation message within a preset time, a third prompt message is displayed in the conversation window. The third prompt message is used to indicate that the target user is not allowed to enter new conversation messages in the conversation window.

12. The method as described in claim 1, characterized in that, The conversation window includes the account identification information of the target contact, and the method further includes: In the conversation window where the target user under the second identity account is having a conversation with the target contact, if the account identification information of the target contact is triggered, a fourth prompt message is displayed. The fourth prompt message is used to prompt the target user under the second identity account that they are not allowed to view the user information of the target contact.

13. The method as described in claim 1, characterized in that, The method further includes: In the conversation window where the target user under the second identity account is having a conversation with the target contact, when the target user enters a conversation message, if the target contact's terminal displays the message receiving interface corresponding to the target contact's account, then a first conversation identifier is displayed on the message receiving interface corresponding to the target contact's account. The first conversation identifier carries a target tag, which is used to indicate that the target user is having a conversation with the target contact using the second identity account. The target contact's account is the user account that the target contact applied for in the social application.

14. The method as described in claim 2, characterized in that, If the confirmation creation control is triggered, the settings interface of the second identity account is displayed, including: If the confirmation creation control is triggered, a creation request for creating a new identity account is sent to the server. The creation request includes an account type identifier to which the new identity account belongs. The creation request is used to instruct the server to assign the second identity account to the target user and return the interface display instruction information corresponding to the type to which the new identity account belongs. The settings interface for the second identity account is displayed based on the interface display instructions returned by the server and the information entered in the account identifier area.

15. The method as described in claim 4, characterized in that, The relationship between any candidate contact and the target user is maintained through a friend relationship chain, which includes the account type to which the first identity account belongs; if the confirmation add control in the contact add interface is triggered, the user identification information of the target contact in the second display area is displayed in the contact management interface, including: If the confirmation add control in the contact add interface is triggered, an add request is sent to the server. The add request carries the account type to which the second identity account belongs. The add request is used to instruct the server to update the target friend relationship chain between the target user and the target contact according to the type to which the second identity account belongs and return the update result, so that when the target contact terminal displays the contact list item of the target contact based on the target friend relationship chain, the target user is displayed in the contact list item associated with the second identity account. In response to the update result returned by the server, the user identification information of the target contact in the second display area is displayed in the contact management interface.

16. The method as described in claim 1, characterized in that, The method further includes: During a conversation between the target user and the target contact under the second identity account, when the target user enters any conversation message in the conversation window, a conversation message sending request is sent to the server. The conversation message sending request is used to instruct the server to detect whether the version information of the social application in the target contact's terminal is the preset version information and return a request response notification. If the request response notification sent by the server indicates that the version information of the social application in the target contact terminal is the preset version information, then any of the conversation messages will be displayed in the conversation window; If the request response notification sent by the server indicates that the version information of the social application in the target contact terminal is not the preset version information, then a fifth prompt message is output, which is used to indicate that any session message has failed to be sent.

17. A message display device, characterized in that, The device includes: The display unit is used to display the first message receiving interface corresponding to the first identity account. The first message receiving interface includes a target type session message identifier. The target type session message identifier is used to indicate that there is a target contact in the second identity account sending a target session message to the target user. The target contact is a contact under the second identity account. The first identity account is a user account applied for by the target user in the social application with a first identity. The second identity account is a user account applied for by the target user in the social application with a second identity. The display unit is also configured to display the second message receiving interface corresponding to the second identity account when the target type session message identifier is selected, and to display the session window identifier of the conversation between the target user under the second identity account and the target contact in the second message receiving interface; The display unit is further configured to display a conversation window between the target user under the second identity account and the target contact when the conversation window identifier is triggered, and to display the target conversation message in the conversation window; The display unit is further configured to, after the target contact sends the target session message to the target user, when the target contact creates a session between the target contact and the target user under the second identity account, display a smart session message in the session window between the target contact and the target user. The smart session message is entered by the target user using the second identity account, and includes a prediction question related to the second identity or the second identity account. The smart session message is set through a smart session message settings interface, which is displayed when the smart session message management option in the settings interface of the second identity account is triggered.

18. A terminal device, characterized in that, The terminal device includes: A processor, suitable for implementing one or more computer programs; and, A computer storage medium storing one or more computer programs, said one or more computer programs being adapted to be loaded by the processor and executed as described in any one of claims 1-16.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores one or more computer programs adapted to be loaded by a processor and executed as described in any one of claims 1-16.

20. A computer program product, characterized in that, The computer program product includes a computer program stored in a computer-readable storage medium, wherein a processor of a computer device reads from the computer-readable storage medium and executes the computer program, causing the computer device to perform the message display method as described in any one of claims 1-16.

Images