Contact person adding method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a contact person adding method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: in an instant messaging application logged in by a first user identifier, a mailbox interface is displayed, an address book of the instant messaging application comprises a session contact person and a mailbox contact person of the first user identifier, and the first user identifier is used for carrying out instant messaging with the session contact person; a first mailbox account associated with the first user identifier is used for performing instant messaging with a mailbox contact; in response to a triggering operation on a target mail in the mailbox interface, a receiving and sending account of the target mail is displayed, and the receiving and sending account comprises a second mailbox account; and when the second mailbox account does not belong to the mailbox contact in the contacts of the first user identifier, adding the second mailbox account to the mailbox contact in the contacts of the first user identifier in response to the adding operation of the second mailbox account in the mail content interface, thereby realizing efficient management of the mailbox account.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, computer device, computer-readable storage medium, and computer program product for adding contacts. Background Technology

[0002] With the development of computer technology, email has become a multi-directional communication channel, both internally and externally. The email accounts involved come from a wide variety of sources, including normal contacts such as colleagues, groups, networks, upstream and downstream partners, and customers actively added by users. Many also come from external email accounts not currently in the collective contact list. Due to the diverse sources of email registrations, it is not yet supported to maintain these external email accounts as if they were conversational contacts in the contact list. Summary of the Invention

[0003] Therefore, it is necessary to provide a method, apparatus, computer device, computer-readable storage medium, and computer program product that can maintain email accounts as contacts in a contact address book and efficiently manage email accounts, addressing the aforementioned technical problems.

[0004] This application provides a method for adding contacts, including:

[0005] In an instant messaging application logged in with a first user identifier, an email interface is displayed. The email interface is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with the conversation contacts, and the first email account is used to communicate instantly with the email contacts.

[0006] In response to a trigger operation on a target email in the email interface, the email content interface of the target email is displayed, the email content interface including the sending and receiving accounts of the target email, and the sending and receiving accounts including a second email account;

[0007] If the second email account is not among the email contacts of the first user's contacts, in response to the add operation of the second email account in the email content interface, the second email account is added to the email contacts of the first user's contacts.

[0008] This application also provides a contact adding device, including:

[0009] The first interface display module is used to display an email interface in an instant messaging application logged in with a first user identifier. The email interface is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with the conversation contacts, and the first email account is used to communicate instantly with the email contacts.

[0010] The second interface display module is used to respond to the trigger operation of the target email in the email interface and display the email content interface of the target email. The email content interface includes the sending and receiving accounts of the target email, and the sending and receiving accounts include the second email account.

[0011] The first contact addition module is used to add the second email account to the email contacts of the first user's contacts in response to the addition operation of the second email account in the email content interface when the second email account is not among the email contacts of the first user's contacts.

[0012] In some embodiments, the first interface display module is configured to display an email service control in an instant messaging application logged in with a first user ID; and to display an email interface in response to a trigger operation on the email service control.

[0013] In some embodiments, the first contact adding module is configured to, in response to a triggering operation on the second email account in the email content interface, display an account adding control for the second email account when the second email account is not among the email contacts of the first user identifier; and in response to a triggering operation on the account adding control, add the second email account to the email contacts of the first user identifier.

[0014] In some embodiments, the device further includes a control display module, which is configured to display an operation pop-up window for the second email account in response to a selection operation of the second email account in the email content interface, the operation pop-up window including an account information viewing control; and to display an account addition control for the second email account in response to a trigger operation of the account information viewing control.

[0015] In some embodiments, the first contact adding module is configured to add the second email account to the email contacts of the first user identifier in response to an add operation on the second email account, when the second email account is not among the email contacts of the first user identifier and the domain name of the second email account is different from the domain name of the first email account.

[0016] In some embodiments, the device further includes a third interface display module, which is configured to display an address book interface in an instant messaging application logged in with the first user identifier, the address book interface including a list of email contacts of the first user identifier; and to display an email editing interface in response to a trigger operation on a second email account in the email contact list, the email editing interface including a second email account as an email receiving account.

[0017] In some embodiments, the apparatus further includes an email account display module, which is configured to display an email editing interface in an instant messaging application logged in with the first user identifier, and to display a list of email contacts of the first user identifier in response to a trigger operation of adding a control to an email account; and to display the second email account in the email editing interface in response to a trigger operation of the second email account in the list of email contacts.

[0018] In some embodiments, the device further includes an email style display module, which is configured to display an operation pop-up window about the second email account in response to a trigger operation on the second email account, the operation pop-up window including an account tagging control; in response to a trigger operation on the account tagging control, the second email account is designated as a tagged email account of the first user identifier; in the emails sent and received by the first user identifier, emails with the tagged email account as the sender and receiver are displayed in a preset style different from the remaining emails, the remaining emails being displayed in a normal style.

[0019] In some embodiments, the first contact adding module is further configured to, in response to a triggering operation of the quick add control, display a list of accounts to be selected when the sending and receiving accounts of the target email include multiple second email accounts that are not among the contacts of the first user identifier; and in response to a selection operation of at least one second email account in the list of accounts to be selected, add the at least one second email account to the email contacts of the contacts of the first user identifier.

[0020] In some embodiments, the first contact adding module is further configured to, in response to a simultaneous addition operation of multiple second email accounts, add all of the multiple second email accounts to the email contacts of the first user's contacts when none of the second email accounts in the target email belong to the email contacts of the first user's contacts.

[0021] This application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the above-described contact addition method.

[0022] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described contact addition method.

[0023] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the above-described contact addition method.

[0024] The aforementioned contact addition method, apparatus, computer device, computer-readable storage medium, and computer program product, by displaying an email interface within an instant messaging application logged in with a first user identifier, wherein the email interface is the email interface of a first email account associated with the first user identifier, and the instant messaging application's address book includes contacts of the first user identifier, including conversation contacts and email contacts, the first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts, thus providing another communication method embedded within the instant messaging application, namely, instant messaging via email. In response to a trigger operation on a target email in the email interface, the email content interface of the target email is displayed, including the sender and receiver accounts of the target email, which include a second email account; if the second email account is not among the email contacts of the first user identifier, in response to an add operation on the second email account in the email content interface, the second email account is added to the email contacts of the first user identifier. Throughout the process, the ability to add conversation contacts in instant messaging applications is reused to allow email accounts to be added as contacts within the instant messaging application. Furthermore, it supports one-click addition of email contacts from emails, eliminating the need for multiple addition operations. This enables efficient management of email accounts by maintaining them as contacts within the instant messaging application.

[0025] This application provides a method for adding contacts, including:

[0026] The system receives an email contact query request sent through an instant messaging application. The instant messaging application is logged in with a first user identifier, and the instant messaging application's address book includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used for instant messaging with the conversation contacts, and the first email account is used for instant messaging with the email contacts. The email contact query request includes a second email account to be added and an email identifier of a target email from which the second email account originates. The second email account belongs to the sending and receiving account of the target email, and the target email is an email sent and received through the first email account associated with the first user identifier.

[0027] If the email sending and receiving accounts corresponding to the email identifier include the first email account and the second email account, then based on the second email account, verify whether the second email identifier belongs to the email contacts of the first user identifier.

[0028] If the verification shows that the second email account does not belong to the email contacts of the first user's contacts, then the second email account is added to the email contacts of the first user's contacts.

[0029] This application also provides a contact adding device, including:

[0030] The request query module is used to receive email contact query requests sent through an instant messaging application. The instant messaging application is logged in with a first user identifier, and the address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with the conversation contacts, and the first email account is used to communicate instantly with the email contacts. The email contact query request includes a second email account to be added and an email identifier of the target email from which the second email account originates. The second email account belongs to the sending and receiving account of the target email, and the target email is an email sent and received through the first email account associated with the first user identifier.

[0031] The verification module is used to verify, based on the second email account, whether the second email identifier belongs to the email contacts of the first user identifier when the sending and receiving accounts of the email corresponding to the email identifier include the first email account and the second email account.

[0032] The second contact addition module is used to add the second email account to the email contacts of the first user's identified contacts when it is verified that the second email account does not belong to the email contacts of the first user's identified contacts.

[0033] In some embodiments, the verification module is configured to query the corresponding email contact list based on the first user identifier; if the email contact list contains the second email account, determine that the second email account belongs to the email contact among the contacts of the first user identifier; if the email contact list does not contain the second email account, determine that the second email account does not belong to the email contact among the contacts of the first user identifier.

[0034] In some embodiments, the second contact adding module is used to set the second email account as the corresponding email account of the first user identifier by synchronizing the email correspondence records between the first email account and the second email account; and, if the account information corresponding to the second email account is stored, to update the corresponding email account to the email contact in the contacts of the first user identifier.

[0035] In some embodiments, the apparatus further includes a storage module, configured to receive a tagging request for the second email account sent via the first user identifier, the tagging request including the second email account and a preset style for tagging the second email account; and to store the preset style and the second email account correspondingly in tagging data about the first user identifier.

[0036] In some embodiments, the device further includes a preset style determination module, which is configured to receive an email from a target email account, the recipient of which is the first email account; if the target email account and the first email account do not belong to the same group, verify whether the target email account belongs to an email contact of the first user identifier; if the target email account is found to belong to an email contact of the first user identifier, query the corresponding tag data according to the first user identifier; if the tag data indicates a preset style for emails originating from the target email account, then while forwarding the email to the first email account, return the preset style to instruct the instant messaging application to display the received email according to the preset style.

[0037] The aforementioned contact addition method, apparatus, computer device, computer-readable storage medium, and computer program product receive an email contact query request sent through an instant messaging application. The instant messaging application is logged in with a first user identifier, and its address book includes contacts associated with the first user identifier. These contacts include conversational contacts and email contacts. The first user identifier is used for instant messaging with conversational contacts, and the first email account is used for instant messaging with email contacts. The email contact query request includes a second email account to be added and an email identifier of the target email from which the second email account originates. The second email account belongs to the sender / receiver account of the target email, and the target email is sent / received through the first email account associated with the first user identifier. This provides another communication method embedded within the instant messaging application: instant messaging via email. If the query finds that the sender / receiver account corresponding to the email identifier includes both the first and second email accounts, the system verifies whether the second email identifier belongs to the email contacts listed under the first user identifier's contacts. This avoids duplicate addition of the second email account already being an email contact, ensuring the validity of the email contact addition process. If the verification indicates that the second email account does not belong to the email contacts listed under the first user identifier's contacts, the second email account is added to the email contacts listed under the first user identifier's contacts. Throughout the process, the ability to add conversation contacts in instant messaging applications is reused to allow email accounts to be added as contacts within the instant messaging application. Furthermore, it supports adding email contacts directly from emails, eliminating the need for multiple addition steps. This enables efficient management of email accounts by maintaining them as contacts within the instant messaging application. Attached Figure Description

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

[0039] Figure 1 An application environment diagram of the contact addition method in one embodiment;

[0040] Figure 2 A flowchart illustrating a method for adding contacts in one embodiment;

[0041] Figure 3 This is a schematic diagram of the contacts interface in one embodiment;

[0042] Figure 4 A schematic diagram of the email account addition process in one embodiment;

[0043] Figure 5 This is a schematic diagram of the authentication process in one embodiment;

[0044] Figure 6 This is a schematic diagram of the email contact determination process in one embodiment;

[0045] Figure 7 This is a schematic diagram illustrating the email editing interface process in one embodiment;

[0046] Figure 8 This is a schematic diagram of the preset style setting process in one embodiment;

[0047] Figure 9 This is a schematic diagram showing a preset style in one embodiment;

[0048] Figure 10 This is a schematic diagram showing a preset style in another embodiment;

[0049] Figure 11 This is a schematic diagram of the preset style setting process in another embodiment;

[0050] Figure 12 This is a schematic diagram of the preset style setting process in another embodiment;

[0051] Figure 13 This is a schematic diagram of the preset style determination steps in one embodiment;

[0052] Figure 14 This is a flowchart illustrating the steps for updating avatar information in one embodiment;

[0053] Figure 15 A flowchart illustrating the method for adding contacts in another embodiment;

[0054] Figure 16 A structural block diagram of a contact adding device in one embodiment;

[0055] Figure 17 A structural block diagram of a contact adding device in another embodiment;

[0056] Figure 18 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0057] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0058] Before introducing this application, let's first explain the relevant concepts:

[0059] Unknown email account: There is no email exchange record between the user's email account and another email account, or the email exchange record has just been generated and the system has not yet synchronized the email exchange record. This email account is called an unknown email account of the user, or an unknown contact.

[0060] Contact Email Account: If a user's email account has a history of sending and receiving emails with another email account, and this history has been synchronized with the system, then this email account is called the user's contact email account. This contact email account can also be referred to as a recent contact.

[0061] Email contacts: Users can proactively add an email address from an email address in an instant messaging application as a contact for that user.

[0062] Email sending and receiving records: The actual records generated when both parties send and receive emails, such as the inbox or outbox in the email interface.

[0063] Email correspondence: Instant messaging applications use email sending and receiving records as source data, and generate them after a delay.

[0064] In related technologies, email accounts come from a variety of sources. Besides normal contacts such as colleagues, groups, networks, upstream and downstream partners, and customers actively added by users, many also originate from external email accounts not included in the collective address book. Due to the wide range of email registration sources, it's difficult to maintain these external email accounts like a collective contact list. Typically, the sender's identity is identified by remembering the email address or by information in the email body. When trying to reply to a user, that user's email record may have been pushed to the bottom of the inbox by other new emails, making it difficult to find. Therefore, related technologies cannot effectively maintain email accounts.

[0065] In this embodiment, an email interface is displayed within an instant messaging application logged in with a first user identifier. This email interface is the email interface of a first email account associated with the first user identifier. The instant messaging application's address book includes contacts associated with the first user identifier, including conversation contacts and email contacts. The first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts. This provides another communication method embedded within the instant messaging application: instant messaging via email. In response to a trigger operation on a target email in the email interface, the email content interface of the target email is displayed. The email content interface includes the sender and receiver accounts of the target email, including a second email account. If the second email account is not among the email contacts of the first user identifier, in response to an add operation on the second email account in the email content interface, the second email account is added to the email contacts of the first user identifier. Throughout this process, the ability to add conversation contacts within the instant messaging application is reused, enabling the addition of email accounts as contacts within the instant messaging application. Furthermore, it supports one-click addition of email contacts from emails, eliminating the need for multiple addition operations. This allows email accounts to be maintained as contacts in instant messaging applications, enabling efficient management of email accounts.

[0066] The contact addition method provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104, or it can be located in the cloud or on another network server.

[0067] In some embodiments, an instant messaging application is deployed on terminal 102. In the instant messaging application logged in with a first user identifier, terminal 102 displays an email interface, which is the email interface of a first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier, including conversation contacts and email contacts. The first user identifier is used to communicate instantly with conversation contacts, and the first email account is used to communicate instantly with email contacts. In response to a trigger operation on a target email in the email interface, terminal 102 displays the email content interface of the target email, which includes the sender and receiver accounts of the target email, including a second email account. In response to a selection operation on the second email account in the email content interface, terminal 102 sends an email contact query request to server 104. After receiving the email contact query request, server 104 verifies whether the second email account belongs to the email contacts of the first user identifier and returns the verification result to terminal 102. When the verification result indicates that the second email account does not belong to the email contacts of the first user's identified contacts, the terminal 102 responds to the addition operation of the second email account in the email content interface and adds the second email account to the email contacts of the first user's identified contacts.

[0068] The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, etc. The server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0069] In one exemplary embodiment, such as Figure 2 As shown, a method for adding contacts is provided, which can be applied to... Figure 1 Taking terminal 102 as an example, the explanation includes the following steps S202 to S206. Wherein:

[0070] Step S202: In the instant messaging application logged in with the first user identifier, an email interface is displayed. The email interface is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with conversation contacts, and the first email account is used to communicate instantly with email contacts.

[0071] Instant messaging applications support work communication among group members. These applications must at least have conversation and email functionality. Conversation is a real-time communication method that allows users to exchange information through text, voice, video, files, and other formats. Email functionality is an asynchronous communication method that facilitates information exchange via email. It supports sending, receiving, and editing emails.

[0072] The first user identifier is the account a user uses for conversations in the instant messaging application, and the first email account associated with the first user identifier is the email account the user uses for sending and receiving emails in the instant messaging application. Optionally, the first user identifier represents the user within the user's group. For example, the first user identifier may be the user's name, nickname, etc.

[0073] For example, within the user's group, the corresponding first email account is determined based on the first user identifier and the group identifier. For instance, the first email account for the first user identifier is 111@xxx.com, where the first user identifier is "111", and the first user identifier is used as the email address of the first email account. The group identifier of the group is "xxx", and the group identifier is used as the domain name of the email address.

[0074] The email interface is used to display emails received or sent by the primary email account.

[0075] The instant messaging application's address book records contacts of the first user identifier, including conversation contacts and email contacts.

[0076] A session contact is a contact who interacts with the first user identifier in a session. A session contact can be another user identifier that belongs to the same group as the first user identifier and is used for session interaction, or it can be another user identifier that does not belong to the same group as the first user identifier and is used for session interaction.

[0077] An email contact is a contact who interacts with the first email account of the first user identifier via email and whose email correspondence is synchronized. An email contact can be another email account that belongs to the same group as the first email account and is used for email interaction, or it can be another email account that does not belong to the same group as the first email account and is used for email interaction.

[0078] In some embodiments, displaying an email interface in an instant messaging application logged in with a first user ID includes: displaying an email service control in the instant messaging application logged in with the first user ID; and displaying the email interface in response to a triggering operation on the email service control.

[0079] The email service control is a control that provides email services. Triggering the email service control enables the instant messaging application's email sending and receiving functionality. The email service control is embedded within the instant messaging application.

[0080] For example, an instant messaging application runs on the terminal, and a first user logs in to the instant messaging application using a first user identifier. After logging in to the instant messaging application using the first user identifier, the main interface of the instant messaging application is displayed. The main interface is the first interface presented to the user after the instant messaging application starts. The main interface includes a session control for enabling conversation functionality and an email service control for enabling email sending and receiving functionality.

[0081] In response to a triggering action on the email service control, the main interface is switched to the email interface.

[0082] In this embodiment, in an instant messaging application logged in with a first user ID, a mailbox service control is displayed, providing the user with a way to convert the session service into an mailbox service. In response to a trigger operation on the mailbox service control, the mailbox interface is displayed to enable email sending and receiving functionality. That is, based on the mailbox service control, an alternative communication method to session communication is provided to the user, allowing the user to choose the desired communication method and improving the user experience.

[0083] Step S204: In response to the triggering operation on the target email in the email interface, the email content interface of the target email is displayed. The email content interface includes the sending and receiving accounts of the target email, and the sending and receiving accounts include a second email account.

[0084] The triggering operations involved in this application include, but are not limited to, voice operations, input operations, and click operations.

[0085] The sending and receiving accounts include at least the email account that sends the target email and the email account that receives the target email. For example, the sending and receiving accounts also include the CC email account (the CC recipient).

[0086] The target email is an email received or sent through the first email account. For example, the target email is an email received through the first email account, or an email sent through the first email account, or an email received through another email account and copied to the first email account.

[0087] The target email content interface displays the content of the target email, which includes the sender and recipient accounts, subject, and body.

[0088] The second email account is the email account to be added as an email contact for the first user. Optionally, the second email account is an unfamiliar email account for the first user. For example, the second email account is an email account with which there is an email exchange record with the first email account, but whose email exchange record is not synchronized with the first email account. For instance, if the second email account sends a target email to the first email account, an email exchange record is generated, but the email exchange record is not synchronized, then the second email account is considered an unfamiliar email account for the first user.

[0089] For example, if there is no email exchange record between the second email account and the first email account, such as the first email account not having sent any emails to the second email account before sending the target email to the second email account, then the second email account is an unfamiliar email account identified by the first user.

[0090] Optionally, in response to a triggering operation on the target email in the email interface's send / receive list, the terminal displays the email content of the target email. The second email account can be either the email account that sent the target email or the email account that received the target email. The send / receive list can be either the inbox or the outbox.

[0091] Optionally, in response to a triggering operation on the target email in the pending email list of the email interface, the terminal displays the email content interface of the target email. Here, the second email account is the email account to receive the target email. That is, the target email is currently in the drafts folder and has not yet been sent to the second email account.

[0092] Step S206: If the second email account is not among the email contacts of the first user's contacts, in response to the addition operation of the second email account in the email content interface, add the second email account to the email contacts of the first user's contacts.

[0093] The "add" operation refers to adding a second email account to the email contacts identified by the first user.

[0094] Optionally, if the second email account is not among the contacts identified by the first user, the terminal responds to the addition operation of the second email account in the email content interface and displays the result of the addition operation.

[0095] If the result indicates that the addition was successful, such as Figure 3 The image shown is a schematic diagram of the address book interface in one embodiment. The instant messaging application includes multiple controls, each used to activate a corresponding service within the application. Figure 3Icons are used to represent corresponding controls. For example, icon 1 represents the conversation control, used to enable the conversation service; icon 2 represents the email service control, used to enable the email service; and icon 3 represents the address book view control, used to enable the address book view service. In response to the selection of the address book view control in the instant messaging application, the address book interface is displayed, which includes controls for viewing other contact lists. Other contact lists are added through documents, calendar events, meetings, and emails. For example, through documents, the relevant document accounts are identified and added as document contacts identified by the first user; through calendar events, the relevant calendar accounts are identified and added as calendar contacts identified by the first user; through meetings, the relevant meeting accounts are identified and added as meeting contacts identified by the first user; and through emails, the relevant email accounts are identified and added as email contacts identified by the first user. Based on document contacts, calendar contacts, meeting contacts, and email contacts, other contact lists are determined.

[0096] In response to a trigger action on the control for viewing other contacts' lists, display the other contacts' display area in the address book interface. In response to a trigger action on the control for viewing the email contacts' list in the other contacts' display area, display the email contacts' list in the other contacts' display area. (Reference) Figure 3 If the first user identifier belongs to group 1, the email contact list includes email accounts belonging to group 2, such as 123@yyy.com, 234@yyy.com, and 5678@zzz.com, belonging to group 3.

[0097] In some embodiments, when the second email account is not among the email contacts of the first user's contacts, in response to an add operation on the second email account in the email content interface, the second email account is added to the email contacts of the first user's contacts, including: when the second email account is not among the email contacts of the first user's contacts, in response to a trigger operation on the second email account in the email content interface, displaying an account addition control for the second email account; and in response to a trigger operation on the account addition control, adding the second email account to the email contacts of the first user's contacts.

[0098] For example, during the process of displaying the email content interface of the target email on the terminal, in response to the triggering operation of the second email account in the email content interface, an email contact query request is sent to the server, so as to instruct the server to respond to the email contact query request, verify whether the second email account belongs to the email contact of the first user identifier, generate a verification result and return it to the terminal.

[0099] After receiving the verification result, if the verification result indicates that the second email account is not among the email contacts of the first user's contacts, the terminal displays an account addition control for the second email account; in response to the triggering operation of the account addition control, the second email account is added to the email contacts of the first user's contacts.

[0100] If the verification result indicates that the second email account does not belong to the email contacts of the first user's contacts, the terminal will not display the account addition control.

[0101] In this embodiment, when the second email account is not among the email contacts identified by the first user, the account addition control for the second email account will only be displayed in response to a triggering operation on the email content interface. This allows the second email account to be quickly added to the email contacts identified by the first user in response to a triggering operation on the account addition control, avoiding duplicate additions and ensuring the validity of the email contact addition.

[0102] In some embodiments, in response to a triggering operation on a second email account in the email content interface, an account addition control for the second email account is displayed, including: in response to a selection operation on the second email account in the email content interface, an operation pop-up window for the second email account is displayed, the operation pop-up window including an account information viewing control; and in response to a triggering operation on the account information viewing control, an account addition control for the second email account is displayed.

[0103] The operation pop-up window provides operation controls for performing related operations on the email account. For example, the operation controls include an account information viewing control for viewing email account information.

[0104] Optionally, in response to the selection of a second email account in the email content interface, an operation pop-up window for the second email account is displayed. If the second email account is not among the email contacts identified by the first user, in response to the triggering of the account information viewing control, an account information pop-up window is displayed, which includes an account addition control for the second email account. The account information pop-up window is used to display information about the email account.

[0105] If the second email account belongs to the email contacts of the first user's contacts, in response to the triggering operation of the account information viewing control, an account information pop-up window that does not contain the account addition control for the second email account is displayed.

[0106] For example, in response to the selection of a second email account in the email content interface, the terminal displays an operation pop-up window for the second email account and sends an email contact query request to the server, instructing the server to respond to the email contact query request, verify whether the second email account belongs to the email contacts of the first user identifier, generate a verification result and return it to the terminal.

[0107] In response to a triggering operation on the account information viewing control, a pop-up window displaying the account information corresponding to the verification result is shown. That is, if the verification result indicates that the second email account does not belong to the email contacts among the contacts identified by the first user, the account information viewing pop-up window includes the account addition control and account information. If the verification result indicates that the second email account belongs to the email contacts among the contacts identified by the first user, the account information viewing pop-up window includes the account information.

[0108] For example, such as Figure 4 The image shown is a schematic diagram of the email account addition process in one embodiment. (Reference) Figure 4 The first email account is 111@xxx.com; in response to the trigger operation of the email service control, the list of sent emails (sent items) is displayed, including email 1, etc. In response to the selection operation of email 1, which is the target email, the email content interface of the target email is displayed. The email content interface includes the sending and receiving accounts, such as the email account that sent the target email 1 (111@xxx.com) and the second email account that received the target email 1 (123@yyy.com).

[0109] In response to the selection of the second email account (123@yyy.com), an operation pop-up window is displayed. In addition to the account information viewing control, the operation pop-up window also includes controls for viewing emails exchanged with the second email account, controls for moving the second email account to the "no notifications" option, and controls for sending emails.

[0110] Figure 4 In the example, if the second email account is not among the contacts of the first user identifier, the account information pop-up will display the second email account, the corresponding second user identifier (123), and the account addition control for "Add as Contact".

[0111] It should be noted that in the relevant technology, when adding a second email account to the contacts, it is necessary to first synchronize the email correspondence between the first email account and the second email account, and then add the second email account as the user's contact email account. Next, the second email account is found in the user's list of recently contacted email accounts and added as an email contact for the user.

[0112] The above process involves at least two addition operations: the first operation of adding the second email account as a correspondent email account, and the second operation of adding the correspondent email account as an email contact. Furthermore, the synchronization process of email correspondence records is delayed, which increases time costs. Therefore, the email contact addition process using this technology is not only cumbersome but also time-consuming, resulting in low contact addition efficiency.

[0113] In this embodiment, the addition of email contacts is achieved through the target email, without waiting for the synchronization of email correspondence records. This avoids the lag in the addition operation caused by the synchronization of email correspondence records. Furthermore, the entire process only requires one addition operation, namely the triggering operation of the account addition control, without the need for multiple addition operations.

[0114] In this way, when the second email account does not belong to the email contact of the first user, the account addition control will only be displayed in response to the account information viewing control in the pop-up window for that operation. This avoids duplicate addition of the second email account that is already an email contact, ensuring the effectiveness of the email contact addition process. Based on this account addition control, a one-click process for adding email contacts can be achieved, avoiding the increased time cost caused by synchronizing email correspondence records and improving the efficiency of adding contacts.

[0115] The aforementioned email contact query request includes a second email account and an email identifier for the target email. In some embodiments, in response to the email contact query request, the server verifies whether the second email account belongs to the email contacts of the first user identifier, and the step of generating a verification result includes: the server, based on the email identifier, verifies whether the sending and receiving accounts of the corresponding email include the first email account and the second email account; if it is verified that the sending and receiving accounts of the email corresponding to the email identifier include the first email account and the second email account, the server, based on the second email account, verifies whether the second email identifier belongs to the email contacts of the first user identifier.

[0116] It should be noted that the above process of checking whether the sending and receiving accounts include the first email account and the second email account is an authentication process that adds permissions, that is, ensuring that the first email account belongs to the email account that sent the target email, or the email account that received the target email, or the person who copied the email. Figure 5 The diagram shown illustrates the authentication process in one embodiment. The specific steps are as follows:

[0117] Step 5.1: The server receives an email contact query request, which is generated by the terminal based on the first email account and email identifier.

[0118] Step 5.2: The server determines whether the first email account belongs to the first user identifier. Specifically, the server retrieves the email address from the first email account and obtains the pre-stored correspondence between the user identifier and the first email account. Based on this correspondence and the first email account, the server queries the corresponding user identifier. If the user identifier matches the email address, the server determines that the first email account belongs to the first user identifier and proceeds to step 5.2. If they do not match, the server determines that the first email account does not belong to the first user identifier and authentication fails.

[0119] Step 5.3: The server determines whether the first email account belongs to the sender / receiver account. Specifically, the server obtains the corresponding sender / receiver account based on the email identifier. If the sender / receiver account includes the first email account (e.g., the first email account is the email account that sent the target email, or the email account that received the target email, or a CC recipient), then proceed to step 5.4. If the first email account is not included (e.g., the first email account is neither the email account that sent the target email, nor the email account that received the target email, nor a CC recipient), then authentication fails.

[0120] Step 5.4: The server determines whether the second email account belongs to the sender / receiver account. Specifically, the server obtains the corresponding sender / receiver account based on the email identifier. If the second email account is not the same as the first email account, and the sender / receiver account includes the second email account (e.g., the second email account is the email account that sent the target email, or the email account that received the target email, or a CC recipient), then authentication is successful. If the second email account is not included (e.g., the second email account is neither the email account that sent the target email, nor the email account that received the target email, nor a CC recipient), then authentication fails.

[0121] In this way, by verifying whether the first email account belongs to the first user identifier, it is ensured that the first email account initiating the email contact addition process is correct. Then, it is verified that the adding email account (the first email account) belongs to a recipient, sender, or CC recipient of the target email. Finally, it is verified that the added email account (i.e., the second email account) also belongs to a recipient, sender, or CC recipient of the target email. Therefore, it is confirmed that the adding and added email accounts are associated with a genuine target email, thus completing the authentication and ensuring the validity of the email contact addition.

[0122] In some embodiments, when the second email account is not among the email contacts of the first user's contacts, in response to the addition operation of the second email account in the email content interface, the second email account is added to the email contacts of the first user's contacts, including: when the second email account is not among the email contacts of the first user's contacts and the domain name of the second email account is different from the domain name of the first email account, in response to the addition operation of the second email account, the second email account is added to the email contacts of the first user's contacts.

[0123] Within each email account belonging to the same group, the domain name is the same. For example, consider four email accounts: 111@xxx.com, 123@yyy.com, 234@yyy.com, and 777@xxx.com; their corresponding domain names are xxx, yyy, yyy, and yyy, respectively. xxx and yyy represent two different groups, Group 1 and Group 2. Therefore, 111@xxx.com and 777@xxx.com belong to Group 1, while 123@yyy.com and 234@yyy.com belong to Group 2.

[0124] It should be noted that if the first email account belongs to a certain group, and the domain name of the second email account is different from that of the first email account, it means that the second email account does not belong to the group to which the first email account belongs. Therefore, for the first user identifier, the second email account is an external email account.

[0125] For example, after the server verifies that the second email account does not belong to the email contact of the first user, it compares whether the domain name of the first email account is consistent with the domain name of the second email account, and returns the comparison result to the terminal. If the comparison result indicates inconsistency, in response to the triggering operation of the account information viewing control, the account addition control for the second email account is displayed.

[0126] If the comparison results are consistent, in response to the triggering of the account information viewing control, an account information pop-up window that does not contain the account addition control for the second email account is displayed. Alternatively, if the server verifies that the second email account belongs to the email contact of the first user, it returns the verification result to the terminal. Based on the verification result, the terminal determines that the second email account belongs to the email contact of the first user, and in response to the triggering of the account information viewing control, displays an account information pop-up window that does not contain the account addition control for the second email account.

[0127] In this embodiment, if it is determined that the second email account is not the email contact of the first user, the domain name of the first email account is further verified to be consistent with the domain name of the first email account. If they are inconsistent, it indicates that the second email account is an external email account. Thus, in response to the addition operation of the second email account, the second email account belonging to the external email account can be quickly added, realizing efficient management of external email accounts.

[0128] In some embodiments, verifying whether a second email address belongs to an email contact among the contacts of a first user based on a second email account includes: querying the corresponding email contact list based on the first user; if the email contact list contains the second email address, determining that the second email address belongs to an email contact among the contacts of the first user; if the email contact list does not contain the second email address, determining that the second email address does not belong to an email contact among the contacts of the first user.

[0129] In this way, based on the first user identifier, it is possible to quickly query whether the second email account is included in the pre-stored list of email contacts corresponding to the first user identifier, thereby enabling rapid verification and improving the efficiency of the verification process.

[0130] In this embodiment, the server uses an email identifier to query whether the sending and receiving accounts of the corresponding email include both a first email account and a second email account, in order to authenticate the addition permission and ensure the validity of the email contact addition process. If the query finds that the sending and receiving accounts of the email corresponding to the email identifier include both a first email account and a second email account, the server quickly verifies whether the second email identifier belongs to the email contacts of the first user identifier, improving the efficiency of the verification process.

[0131] In the above process, in response to the triggering operation of the account addition control, the terminal sends an addition request containing the first user identifier and the second email account to the server, so as to instruct the server to add the second email account to the email contacts of the first user identifier according to the first user identifier.

[0132] In some embodiments, the step of adding a second email account to the email contacts of a first user identifier includes: setting the second email account as the corresponding email account of the first user identifier by synchronizing the email correspondence records between the first email account and the second email account; and updating the corresponding email account to the email contacts of the first user identifier if the account information corresponding to the second email account is stored.

[0133] For example, such as Figure 6The diagram shown illustrates the process of determining email contacts in one embodiment. The specific steps are as follows:

[0134] Step 6.1: The server verifies whether the second email account is a corresponding email account. Specifically, the server verifies whether the email correspondence between the first and second email accounts has been synchronized. If synchronized, the second email account is determined to be a corresponding email account, and step 6.5 is executed. If not synchronized, the second email account is not a corresponding email account, and step 6.2 is executed.

[0135] Step 6.2: The server verifies whether there is account information for the second email account. If not, proceed to step 6.3; if so, proceed to step 6.4.

[0136] Step 6.3: The server sends an account information retrieval request to the terminal, instructing the terminal to display an account information fill-in pop-up window to retrieve the account information, and then returns it to the server. After storing the account information, the server executes step 6.4.

[0137] Step 6.4: The server changes the second email account to a regular email account and proceeds to step 6.5.

[0138] Specifically, the server adds the second email address to the list of contact email addresses, which can be displayed in the other contacts list in the address book interface, such as... Figure 3 As shown, the list of email addresses can be displayed in the email contact list.

[0139] Step 6.5: The server updates the email accounts of the correspondents to the email contacts.

[0140] It should be noted that the logic for adding email contacts in this embodiment is to first convert unfamiliar email accounts into existing email accounts, and then into email contacts. In related technologies, the required existing email accounts are retrieved from a list of existing email accounts, and then converted into email contacts. These related technologies require converting unfamiliar email accounts into existing email accounts beforehand; that is, the adding logic in this embodiment is essentially the same as that in existing technologies. Furthermore, in terms of user operation, unlike existing technologies which need to consider the lag in email correspondence records and involve multiple adding operations, this application only requires one adding operation, making it more efficient.

[0141] In this way, by synchronizing the email correspondence between the first and second email accounts, the second email account is set as the corresponding email account for the first user. After storing the account information corresponding to the second email account, the corresponding email account is then updated to the email contact among the contacts identified by the first user. This ensures that each email contact has corresponding email correspondence records and account information, facilitating subsequent email management for the user.

[0142] In the above contact addition method, an email interface is displayed within the instant messaging application logged in with the first user identifier. This email interface is the email interface of the first email account associated with the first user identifier. The instant messaging application's address book includes contacts of the first user identifier, including conversation contacts and email contacts. The first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts. This provides another communication method embedded within the instant messaging application: instant messaging via email. In response to a trigger operation on the target email in the email interface, the email content interface of the target email is displayed. The email content interface includes the sender and recipient accounts of the target email, including a second email account. If the second email account is not among the email contacts of the first user identifier, in response to an add operation on the second email account in the email content interface, the second email account is added to the email contacts of the first user identifier. Throughout this process, the ability to add conversation contacts within the instant messaging application is reused, enabling the addition of email accounts as contacts within the instant messaging application. Furthermore, it supports one-click addition of email contacts from emails, eliminating the need for multiple addition operations. This allows email accounts to be maintained as contacts in instant messaging applications, enabling efficient management of email accounts.

[0143] In some embodiments, after adding the second email account to the email contacts of the first user identifier, the method further includes: displaying an address book interface in an instant messaging application logged in with the first user identifier, the address book interface including a list of email contacts of the first user identifier; and displaying an email editing interface in response to a triggering operation on the second email account in the email contacts list, the email editing interface including the second email account as an email receiving account.

[0144] For example, such as Figure 7 The image shown is a schematic diagram illustrating the email editing interface process in one embodiment. After adding the second email account 123@yyy.com to the email contact of the first user identifier, refer to the preceding text... Figure 3 The example shows the list of email contacts, followed by a reference. Figure 7In response to the selection of the second email account 123@yyy.com in the email contact list, the terminal displays an email editing interface overlaid on the address book interface. This email editing interface includes emails in editing mode that are to be sent. The content of the emails to be sent includes the second email account 123@yyy.com as the email receiving account (recipient). Here, the email receiving account can also be understood as the email account used to receive the emails to be sent.

[0145] In this embodiment, in the instant messaging application logged in with the first user identifier, an address book interface is displayed, which includes a list of email contacts for the first user identifier. In response to a trigger operation on the second email account in the email contact list, an email editing interface is automatically displayed, and the second email address is automatically set as the sender in the email editing interface. This realizes an email editing method that switches from the address book interface to the email editing interface, improving the flexibility of email editing.

[0146] In some embodiments, after adding the second email account to the email contacts of the first user's contacts, the method further includes: displaying an email editing interface in an instant messaging application logged in with the first user's identity; displaying a list of email contacts of the first user's identity in response to a triggering operation of the email account addition control; and displaying the second email account in the email editing interface in response to a triggering operation of the second email account in the email contact list.

[0147] The email account addition control refers to a control for adding email accounts to receive emails to be sent, or it can be a control for adding CC recipients for emails to be sent.

[0148] Optionally, after adding the second email account to the email contacts of the first user's contacts, the terminal displays an email service control in the instant messaging application logged in with the first user's identity. In response to a triggering operation on the email service control, the email interface is displayed. In response to a triggering operation on the email editing control in the email interface, an email editing interface is displayed, which includes a first area for displaying the email account to receive the email to be sent, and a second area for displaying the CC recipients of the email to be sent.

[0149] In response to a triggering operation of adding a control to an email account in the first area, or in response to a triggering operation of adding a control to an email account in the second area, a contact list containing the first user's identifier is displayed; in response to a triggering operation of a second email account in the email contact list, the second email account is displayed in the first area, or the second email account is displayed in the second area.

[0150] Optionally, in an instant messaging application logged in with a first user identifier, an address book interface is displayed, which includes a list of email contacts for the first user identifier. In response to a triggering operation on a second email account in the email contacts list, an email editing interface is displayed, where a first area displays the second email account used as the email receiving account. In response to a triggering operation on adding a control to an email account in the second area of ​​the email editing interface, an address book interface containing a list of email contacts is displayed. In response to a selection operation on another email contact (an email contact different from the second email account) in the email contacts list, that other email contact is displayed in the second area of ​​the email editing interface.

[0151] This not only allows for the automatic addition of email accounts for receiving emails in the email editing interface, but also automatically adds CC recipients for the emails to be sent, improving the flexibility and convenience of adding email accounts when editing emails.

[0152] In this embodiment, in the instant messaging application logged in with the first user ID, an email editing interface is displayed. In response to the trigger operation of adding a control to the email account, the page switches to the address book interface and displays the email contact list of the first user ID. In response to the trigger operation of the second email account in the email contact list, the second email account is displayed in the email editing interface. This realizes another way of email editing, from the email editing interface to the address book interface containing the email contact list and then back to the email editing interface, improving the flexibility of email editing.

[0153] In some embodiments, after adding the second email account to the email contacts of the first user identifier, the method further includes: in response to a triggering operation on the second email account, displaying an operation pop-up window about the second email account, the operation pop-up window including an account tagging control; in response to a triggering operation on the account tagging control, using the second email account as a tagged email account of the first user identifier; and in the sent and received emails of the first user identifier, displaying emails with the tagged email account as the sender and receiver in a preset style different from the remaining emails, while the remaining emails are displayed in a normal style.

[0154] The account tagging control is used to determine the corresponding preset style for displaying email accounts. Preset styles define how email contacts are tagged. For example, preset style 1 uses a specific image to tag email contacts; in this case, a star symbol is displayed next to the contact in the email contact list, and the contact will be displayed first in the list. Preset styles also define how emails sent by email contacts receive special notifications; for example, preset style 2 uses a specific sound or color to notify the contact of an email sent. The default style is the style used by the email service.

[0155] For example, after adding the second email account to the email contacts of the first user identifier, the terminal responds to the triggering operation of the second email account in the target email and displays an operation pop-up window about the second email account, which includes at least one account tag control.

[0156] In response to a selection operation of any one of the at least one account tagging controls, the terminal uses the second email account as the tagged email account of the first user identifier.

[0157] In the emails sent and received by the first user identifier, emails with the marked email address as the sender and receiver will be displayed in a preset style that differs from the remaining emails, which will be displayed in the normal style. This preset style is related to the selected account tagging control.

[0158] In other embodiments, the pop-up window also includes a message notification exemption control, which is used to exempt notifications for emails sent to an email account.

[0159] In other embodiments, after adding the second email account to the email contacts of the first user identifier, the terminal, in response to a triggering operation on the second email account in the target email, displays an operation pop-up window containing an account tag selection entry. In response to a triggering operation on the account tag selection entry, a selection list of account tag controls is displayed. In response to a selection operation on at least one account tag control in the selection list, the terminal uses the second email account as the tagged email account of the first user identifier.

[0160] For example, such as Figure 8 The diagram illustrates the preset style setting process in one embodiment. After determining the second email account (123@yyy.com) as the email contact, when displaying the email content interface of Email 1 (the target email), in response to the triggering operation on the second email account (123@yyy.com), an operation pop-up window is displayed, where "..." represents the account tag selection entry. In response to the triggering operation on the account tag selection entry, a selection list is displayed, including two account tag controls: "Add Star Tag" and "Special Reminder." For example, after selecting the "Special Reminder" account tag control, options for the reminder method are displayed, such as sound reminder or text reminder. If a text reminder is selected, the preset style is to use a specific font for tagging, and the second email account is the tagged email account.

[0161] When the tagged email account sends an email to the primary email account, the email will be displayed in a special font in the sent email list after the primary email account's email interface is shown, such as... Figure 9The image shown is a schematic diagram of a preset style display in one embodiment. After receiving an email from the second email account (123@yyy.com), it is marked with "Special Reminder Email" in bold to remind the first user to view it.

[0162] For example, after selecting "Add Star Mark" for the second email account (123@yyy.com), as shown... Figure 10 As shown, this is a schematic diagram of a preset style display in another embodiment. Email contacts selected for "Add Star Mark" are displayed at the top of the email contact list. Figure 10 The starred contact is the email contact marked with a star, including the second email account (123@yyy.com). Figure 1 234@yyy.com and 5678@zzz.com are other email addresses with standard format.

[0163] Of course, you can also use the pop-up window to cancel the default style for marking email accounts. For example... Figure 11 The diagram shown is a schematic representation of the preset style setting process in another embodiment. Figure 11 The second email account has selected a special notification with sound alerts, displayed as a bell icon in the pop-up window. The selection list also includes a control to uncheck the account tagging option, such as... Figure 11 The "Cancel Special Reminder" control is for removing the account tagging for special reminders. To cancel a special reminder, in response to the triggering of the "Cancel Account Tag" control in the selection list, the reminder will be displayed in the preset style corresponding to the special reminder, and the special reminder for the tagged email account will be canceled.

[0164] In other examples, you can also set a tag for the email account during the process of adding an email contact. Specifically, as mentioned earlier, after displaying the account addition control for the second email account, in response to the triggering operation of the account addition control, an account information editing pop-up is displayed, such as... Figure 12 The diagram shown is a schematic representation of the preset style setting process in another embodiment. Figure 12 The document demonstrates the settings for a second email account. The account information editing pop-up includes an input area and a selection area. The input area requires the first user to enter a nickname and the group to which the second email account belongs. The selection area includes a list of options. After completing the input in the input area and selecting at least one account tag control from the selection list in the second area, in response to the confirmation action of the control in the account information editing pop-up, the second email account is added to the first user's email contacts and set as a tag email account.

[0165] This allows for the simultaneous addition of email contacts and tagging of email accounts, improving the convenience of email account management.

[0166] In some embodiments, the method further includes: receiving a tagging request for a second email account sent via a first user identifier, the tagging request including the second email account and a preset style for tagging the second email account; and storing the preset style and the second email account correspondingly in tagging data about the first user identifier.

[0167] For example, in response to a triggering operation of the account tagging control, the terminal generates a tagging request for a second email account based on a first user identifier and a preset style of the account tagging control. The terminal sends the tagging request to the server. The server stores the preset style and the second email account in the tagging data for the first user identifier.

[0168] In this way, after the preset style is determined, the selected preset style and the second email account are sent to the server for corresponding storage. This ensures that after the server receives the email, it can quickly determine the preset style corresponding to the email based on the stored tag data. This ensures that the terminal can accurately display the email according to the preset style, helping users quickly locate the email sent by the tagged email account.

[0169] In some embodiments, the method further includes: receiving an email from a target email account, wherein the recipient of the email is a first email account; if the target email account and the first email account do not belong to the same group, verifying whether the target email account belongs to an email contact of a first user identifier; if the target email account is found to belong to an email contact of the first user identifier, querying the corresponding tag data according to the first user identifier; if the tag data indicates a preset style for emails originating from the target email account, then while forwarding the email to the first email account, returning the preset style to instruct the instant messaging application to display the received email according to the preset style.

[0170] For example, such as Figure 13 The diagram shown illustrates the preset style determination step in one embodiment. The specific steps are as follows:

[0171] Step 13.1: After receiving an email from the target email account, the server determines whether the target email account is bound to the user identifier of the instant messaging application.

[0172] Specifically, the server parses the email, determines that the recipient is the first email account, and verifies whether the target email account belongs to the same group as the first email account based on the respective domains of the first and second email accounts. If they do, it means that the target email account is bound to a user identifier within the same group, and proceeds to step 13.2. If they do not belong to the same group, proceed to step 13.3.

[0173] Step 13.2: The server determines whether the user identifier is bound. Specifically, the server queries whether the user identifiers associated with the target email account belonging to that group are included in the tagging data of the first user identifier. If they are included, it means that the user identifier of the target email account is tagged by the first user identifier, that is, the user identifier is bound. The corresponding preset style is determined, and step 13.6 is performed. If they are not included, it means that the user identifier of the target email account is not tagged by the first user identifier, that is, the user identifier is not bound. Step 13.3 is performed.

[0174] Step 13.3: The server determines whether it has stored the target email account's account information. Specifically, if it has, the server proceeds to step 13.4; if it has not, it proceeds to step 13.7.

[0175] Step 13.4: The server determines whether the target email account belongs to the email contacts of the first user identifier. If yes, proceed to step 13.5; otherwise, proceed to step 13.7.

[0176] Step 13.5: The server determines whether the target email account belongs to the marked email account of the first user identifier. If it belongs to the marked email account, proceed to step 13.6; if it does not belong to the marked email account, proceed to step 13.7.

[0177] Specifically, the server queries the corresponding tagging data based on the first user identifier. If the tagging data indicates a preset style for emails originating from the target email account, then while forwarding the email to the first email account, step 13.6 is executed. If no preset style is indicated, then the email does not belong to the tagged email account, and step 13.7 is executed.

[0178] Step 13.6: The server returns a message to the terminal indicating that a preset style exists.

[0179] Step 13.7: The server returns that the preset style does not exist to the terminal.

[0180] In this embodiment, after the server receives an email from the target email account, it first verifies whether the target email account belongs to the same group as the first email account in the email. If they do, it further verifies whether the user identifier associated with the target email account is marked by the first user identifier. If they do not belong to the same group, it determines the preset style by judging whether the target email account is a marked email account. In this way, the server can accurately and promptly determine whether the email needs to be marked with high priority when receiving emails, avoiding users missing important emails and optimizing email account management.

[0181] In some embodiments, after adding the second email account as an email contact of the first user identifier, the method further includes: at preset time intervals, the terminal obtains the target avatar information of the second email account from the server, and obtains the pre-stored avatar information from local storage according to the second email account; if it is found that the avatar information is inconsistent with the target avatar information, the locally stored avatar information is updated to the target avatar information.

[0182] For example, such as Figure 14 The diagram illustrates a flowchart of the profile picture information update step in one embodiment. Specifically, every preset time interval, the terminal retrieves the target profile picture information of a second email account from the first server, and retrieves pre-stored profile picture information from local storage based on the second email account. The terminal determines whether the profile picture information matches the target profile picture information. If they match, no action is taken. If they do not match, the terminal downloads the link to the target profile picture information and stores the link locally to update the profile picture information to the target email information. The link and the second email account are then sent to the second server for corresponding storage to complete the update.

[0183] The first server is the email server corresponding to the email service embedded in the instant messaging application; the server mentioned earlier is the first server. The second server is the application server for the instant messaging application. In the first server, the link to the target avatar is stored in a corresponding data structure, which retrieves the link using the field `qyy_head_pic_url`. The second server also stores the retrieved link in a corresponding data structure, with the `head_pic_url` field also storing the retrieved link in the data result.

[0184] The profile picture information is used to display the corresponding email account in the pop-up window.

[0185] For example, if the user identifier corresponding to the second email account belongs to a certain group, or if the domain name in the second email account is a preset domain name, the step of retrieving the target avatar information of the second email account from the first server every preset time period is started.

[0186] In this way, the profile picture information is verified and dynamically refreshed in real time at preset intervals, making it easier for users to quickly identify the users associated with the email account and manage email accounts more efficiently and conveniently.

[0187] In this embodiment, in response to a trigger operation on the second email account, an operation pop-up window regarding the second email account is displayed, including an account tagging control. This provides a high-priority tagging function for email accounts, optimizing email account management. In response to a trigger operation on the account tagging control, the second email account is designated as the tagged email account for the first user identifier. In the emails sent and received by the first user identifier, emails with the tagged email account as the sender or receiver are displayed in a preset style different from the remaining emails, while the remaining emails are displayed in a normal style. This preset style display helps users quickly locate emails sent by the tagged email account, preventing users from missing important emails and further optimizing email account management.

[0188] In some embodiments, the email content interface further includes a quick add control. After displaying the email content interface of the target email, the method further includes: if the sending and receiving accounts of the target email include multiple second email accounts that are not among the email contacts of the first user identifier, in response to the triggering operation of the quick add control, displaying a list of accounts to be selected; in response to the selection operation of at least one second email account in the list of accounts to be selected, adding at least one second email account to the email contacts of the first user identifier.

[0189] The quick add control is used to initiate the simultaneous addition of at least one second email account, where each second email account is an email account in the target email that is not a contact of the first user. For example, if both the CC recipient and the recipient in the target email are second email accounts (i.e., neither is a contact of the first user), then the quick add control can initiate the simultaneous addition of at least one email account from the CC recipient and the recipient.

[0190] The list of accounts to be selected includes all secondary email accounts that are not part of the primary user's contact in the target email. For example, if the target email includes Recipient 1, Recipient 2, CC 3, and the primary email account as the sender, Recipient 1 and CC 3 are both secondary email accounts (i.e., neither is a primary contact), while Recipient 2 is a primary contact but not a secondary email account, then the list of accounts to be selected includes Recipient 1 and CC 3.

[0191] For example, if the sender and receiver accounts of the target email include multiple second email accounts that are not among the email contacts of the first user identifier, a quick add control is displayed in the target email. In response to a triggering operation on the quick add control, a list of accounts to be selected is displayed. In response to the selection of at least one second email account from the list of accounts to be selected, at least one second email account is added to the email contacts of the first user identifier.

[0192] For example, the list of accounts to be selected includes Recipient 1 and CC 3. Each second email account in the list of accounts to be selected includes a selection control in its display area. In response to triggering the selection control corresponding to Recipient 1 and the selection control corresponding to CC 3, Recipient 1 and CC 3 are simultaneously added as email contacts associated with the first user identifier of the first email account.

[0193] In other embodiments, if the sender and receiver accounts of the target email include a second email account that is not a contact of the first user identifier's email address, or if the second email account does not include a contact of the first user identifier's email address, the quick add control is not displayed in the target email.

[0194] In this embodiment, when the sender and receiver accounts of the target email include multiple second email accounts that are not among the contacts identified by the first user, a list of accounts to be selected is displayed in response to the triggering operation of the quick add control. That is, the quick add control can filter out and display all second email accounts in the target email for the user to choose from. In response to the selection of at least one second email account in the list of accounts to be selected, at least one second email account is added to the email contacts of the contacts identified by the first user. Thus, when a user needs to add multiple second email accounts from the target email to their contacts, this quick add control allows for simultaneous addition of multiple second email accounts, eliminating the need to add them one by one, improving efficiency and convenience.

[0195] In some embodiments, there are multiple second email accounts. After displaying the email content interface of the target email, the method further includes: when each of the second email accounts in the target email does not belong to the email contacts in the contacts identified by the first user, in response to the simultaneous addition operation of multiple second email accounts, adding all the second email accounts to the email contacts in the contacts identified by the first user.

[0196] For example, when each of the second email accounts in the target email does not belong to the email contacts of the first user's contacts, in response to the simultaneous selection of multiple second email accounts, an account addition control for adding multiple second email accounts at the same time is displayed, and in response to the triggering operation of the account addition control, multiple second email accounts are added to the email contacts of the first user's contacts.

[0197] In this embodiment, when each of the second email accounts in the target email does not belong to the email contacts of the first user identifier, when it is necessary to add email contacts for multiple second email accounts in the target email, the simultaneous addition of multiple second email accounts is achieved, eliminating the need to add second email accounts one by one, thus improving the efficiency and convenience of adding.

[0198] In some embodiments, such as Figure 15 As shown, a method for adding contacts is provided. This method is applied to... Figure 1 Taking server 104 as an example, the following steps are included:

[0199] Step S1502: Receive an email contact query request sent through an instant messaging application. The instant messaging application is logged in with a first user identifier. The instant messaging application's address book includes contacts with the first user identifier. These contacts include conversation contacts and email contacts. The first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts. The email contact query request includes a second email account to be added and the email identifier of the target email from which the second email account originates. The second email account belongs to the sender / receiver account of the target email, and the target email is an email sent / received through the first email account associated with the first user identifier.

[0200] For example, during the process of displaying the email content interface of the target email on the terminal, in response to the triggering operation of the second email account in the email content interface, an email contact query request is generated based on the second email account to be added and the email identifier of the target email, and the terminal sends the email contact query request to the server.

[0201] Step S1504: If the sending and receiving accounts of the email corresponding to the email identifier include the first email account and the second email account, then based on the second email account, verify whether the second email identifier belongs to the email contacts of the first user identifier.

[0202] Optionally, if the sender and receiver accounts of the email corresponding to the email identifier include both the first email account and the second email account, the server queries the corresponding email contact list based on the first user identifier; if the email contact list contains the second email account, it determines that the second email account belongs to the email contacts among the contacts of the first user identifier; if the email contact list does not contain the second email account, it determines that the second email account does not belong to the email contacts among the contacts of the first user identifier.

[0203] Step S1506: If it is verified that the second email account does not belong to the email contacts of the first user's contacts, add the second email account to the email contacts of the first user's contacts.

[0204] Optionally, if the second email account is not found to be an email contact among the contacts of the first user identifier, the terminal responds to the trigger operation of the account addition control by sending an addition request containing the first user identifier and the second email account to the server. The server sets the second email account as the corresponding email account of the first user identifier by synchronizing the email correspondence records between the first and second email accounts. If the account information corresponding to the second email account is stored, the corresponding email account is updated to the email contact among the contacts of the first user identifier.

[0205] In some embodiments, the method further includes: the server receiving a tagging request for a second email account sent via a first user identifier, the tagging request including the second email account and a preset style for tagging the second email account; and storing the preset style and the second email account correspondingly in tagging data about the first user identifier.

[0206] In some embodiments, the method further includes: receiving an email from a target email account, wherein the recipient of the email is a first email account; if the target email account and the first email account do not belong to the same group, verifying whether the target email account belongs to an email contact of a first user identifier; if it is verified that the target email account belongs to an email contact of the first user identifier, querying the corresponding tag data according to the first user identifier; if the tag data indicates a preset style for emails originating from the target email account, then while forwarding the email to the first email account, returning the preset style to instruct the instant messaging application to display the received email according to the preset style.

[0207] In the above contact addition method, an email contact query request is received from an instant messaging application. The instant messaging application is logged in with a first user identifier, and its address book includes contacts associated with the first user identifier. These contacts include conversation contacts and email contacts. The first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts. The email contact query request includes the second email account to be added and the email identifier of the target email from which the second email account originates. The second email account belongs to the sender / receiver account of the target email, and the target email is sent / received through the first email account associated with the first user identifier. This provides another communication method embedded within the instant messaging application: instant messaging via email. If the query finds that the sender / receiver account corresponding to the email identifier includes both the first and second email accounts, the system verifies whether the second email identifier belongs to the email contacts in the first user identifier's contacts list. This avoids duplicate addition of the second email account, ensuring the validity of the email contact addition process. If the verification shows that the second email account does not belong to the email contacts in the first user identifier's contacts list, the second email account is added to the email contacts in the first user identifier's contacts list. Throughout the process, the ability to add conversation contacts in instant messaging applications is reused to allow email accounts to be added as contacts within the instant messaging application. Furthermore, it supports adding email contacts directly from emails, eliminating the need for multiple addition steps. This enables efficient management of email accounts by maintaining them as contacts within the instant messaging application.

[0208] This application also provides an application scenario in which the above-described contact addition method is applied. Specifically, the application of the contact addition method in this scenario is as follows:

[0209] In an instant messaging application logged in with a first user identifier, an email receiving interface (inbox interface) is displayed. This interface is the email interface of the first email account associated with the first user identifier. The instant messaging application's address book includes contacts associated with the first user identifier, including conversation contacts and email contacts. The first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts. In response to a trigger operation on a target email in the email receiving interface, the email content interface of the target email is displayed. This interface includes the first email account and a second email account. When the first email account is the email account receiving the target email, the second email account can be the email account sending the target email or a CC email account. When the first email account is a CC email account, the second email account is either the email account sending the target email or the email account receiving the target email. If the second email account is not among the email contacts of the first user identifier, in response to an add operation on the email content interface, the second email account is added to the email contacts of the first user identifier. This allows for the maintenance of both the sender and recipient as contacts in instant messaging applications, enabling efficient management of email accounts.

[0210] Of course, it is not limited to this. The contact addition method provided in this application can also be applied to the email sending interface, where the first email account is the email account that sends the target email, and the second email account is the email account that receives the target email or the email account that is copied to it.

[0211] The above application scenarios are merely illustrative. It is understood that the contact addition methods provided in the embodiments of this application are not limited to the above scenarios.

[0212] In one specific embodiment, a method for adding contacts is provided, which involves interaction between a terminal and a server, and the specific steps include:

[0213] 1. In an instant messaging application logged in with the first user identifier, the terminal displays an email interface, which is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with conversation contacts, and the first email account is used to communicate instantly with email contacts.

[0214] For example, in an instant messaging application logged in with a first user ID, the terminal displays an email service control; in response to a trigger operation on the email service control, the email interface is displayed.

[0215] 2. The terminal responds to the trigger operation of the target email in the email interface and displays the email content interface of the target email. The email content interface includes the sending and receiving accounts of the target email, and the sending and receiving accounts include a second email account.

[0216] 3. During the display of the target email's content on the terminal, in response to the selection of a second email account in the email content interface, the terminal displays an operation pop-up window for the second email account and sends an email contact query request to the server. The operation pop-up window includes controls for viewing account information.

[0217] 4. In response to the email contact query request, the server verifies whether the second email account belongs to the email contacts identified by the first user. If the server verifies that the second email account does not belong to the email contacts identified by the first user, it compares whether the domain name of the first email account is consistent with the domain name of the second email account and returns the comparison result to the terminal.

[0218] Specifically, if the server finds that the sending and receiving accounts of the email corresponding to the email identifier include the first email account and the second email account, it retrieves the corresponding email contact list based on the first user identifier. If the email contact list contains the second email account, it determines that the second email account belongs to the email contacts of the first user identifier. If the email contact list does not contain the second email account, it determines that the second email account does not belong to the email contacts of the first user identifier.

[0219] 5. In the event of inconsistencies in the comparison results, the terminal responds to the triggering operation of the account information viewing control by displaying the account addition control for the second email account.

[0220] If the comparison results are consistent, the terminal responds to the triggered operation of the account information viewing control by displaying an account information pop-up window that does not include the account addition control for the second email account.

[0221] Alternatively, if the server verifies that the second email account belongs to the email contact of the first user, it returns the verification result to the terminal. Based on the verification result, the terminal determines that the second email account belongs to the email contact of the first user and, in response to the triggering operation of the account information viewing control, displays an account information pop-up window that does not contain the account addition control for the second email account.

[0222] 6. First method: During the process of displaying the account addition control for the second email account, the terminal responds to the trigger operation of the account addition control, adds the second email account to the email contacts in the contacts of the first user identifier, and sends an addition request to the server.

[0223] The second method involves verifying, as described in steps 3-5 above, whether each secondary email account in the target email belongs to an email contact, thus confirming the existence of multiple secondary email accounts that do not belong to an email contact.

[0224] In this case, the terminal responds to the triggering operation of the quick add control in the email content interface by displaying a list of accounts to be selected; in response to the selection operation of at least one second email account in the list of accounts to be selected, it adds at least one second email account to the email contacts in the contacts of the first user identifier and sends an add request to the server.

[0225] The third method involves verifying, in steps 3-5 above, whether each secondary email account in the target email belongs to an email contact, thus confirming that there are multiple secondary email accounts that do not belong to an email contact.

[0226] In response to the simultaneous addition of multiple secondary email accounts, the terminal adds all the secondary email accounts to the email contacts of the first user's contacts and sends an add request to the server.

[0227] 7. After receiving the add request from the terminal, the server synchronizes the email correspondence records between the first email account and the second email account, and sets the second email account as the corresponding email account of the first user. If the account information corresponding to the second email account is stored, the server updates the corresponding email account to the email contact in the contacts of the first user.

[0228] 8. After the terminal adds each second email account to the email contacts of the first user identifier, it performs the following steps 8.1 and 8.2:

[0229] 8.1. In response to a trigger operation on the second email account, the terminal displays an operation pop-up window about the second email account, which includes an account tagging control; in response to a trigger operation on the account tagging control, the terminal tags the second email account as the first user identifier and generates a tagging request to the server.

[0230] In response to the tagging request, the server stores the preset style and the second email account included in the tagging request in the tagging data about the first user identifier.

[0231] When the server receives an email from a target email account, where the recipient is a primary email account; if the target email account and the primary email account do not belong to the same group, the server verifies whether the target email account belongs to the email contacts identified by the primary user. If the target email account is found to belong to the email contacts identified by the primary user, the server queries the corresponding tag data based on the primary user identifier. If the tag data indicates a preset style for emails originating from the target email account, the server forwards the email to the primary email account while returning the preset style to the terminal; otherwise, it returns a normal style to the terminal.

[0232] If the terminal receives a preset style from the server, the email will be displayed according to the preset style. If the terminal receives a normal style from the server, the email will be displayed according to the normal style.

[0233] 8.2 In an instant messaging application logged in with the first user identifier, the terminal displays an address book interface, which includes a list of email contacts associated with the first user identifier. In response to a trigger operation on a second email account in the email contact list, an email editing interface is displayed, which includes the second email account used as the email receiving account.

[0234] Alternatively, in an instant messaging application logged in with the first user identifier, an email editing interface is displayed, and in response to a triggering operation of adding a control to an email account, a list of email contacts for the first user identifier is displayed; in response to a triggering operation of a second email account in the email contact list, the second email account is displayed in the email editing interface.

[0235] In this embodiment, an email interface is displayed within an instant messaging application logged in with a first user identifier. This email interface is the email interface of a first email account associated with the first user identifier. The instant messaging application's address book includes contacts associated with the first user identifier, including conversation contacts and email contacts. The first user identifier is used for instant messaging with conversation contacts, and the first email account is used for instant messaging with email contacts. This provides another communication method embedded within the instant messaging application: instant messaging via email. In response to a trigger operation on a target email in the email interface, the email content interface of the target email is displayed. The email content interface includes the sender and receiver accounts of the target email, including a second email account. If the second email account is not among the email contacts of the first user identifier, in response to an add operation on the second email account in the email content interface, the second email account is added to the email contacts of the first user identifier. Throughout this process, the ability to add conversation contacts within the instant messaging application is reused, enabling the addition of email accounts as contacts within the instant messaging application. Furthermore, it supports one-click addition of email contacts from emails, eliminating the need for multiple addition operations. This allows for the maintenance of email accounts as contacts within instant messaging applications, enabling efficient email account management. Furthermore, it allows for high-priority tagging of email contacts, making it easier for users to find important contacts and avoid missing important emails from them.

[0236] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0237] Based on the same inventive concept, this application also provides a contact adding device for implementing the contact adding method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more contact adding device embodiments provided below can be found in the limitations of the contact adding method described above, and will not be repeated here.

[0238] In one exemplary embodiment, such as Figure 16As shown, a contact adding device 1600 is provided, including: a first interface display module 1602, a second interface display module 1604, and a first contact adding module 1606, wherein:

[0239] The first interface display module 1602 is used to display an email interface in an instant messaging application logged in with a first user identifier. The email interface is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with conversation contacts, and the first email account is used to communicate instantly with email contacts.

[0240] The second interface display module 1604 is used to respond to the trigger operation of the target email in the email interface and display the email content interface of the target email. The email content interface includes the sending and receiving accounts of the target email, and the sending and receiving accounts include the second email account.

[0241] The first contact addition module 1606 is used to add the second email account to the email contacts of the first user's identified contacts when the second email account is not among the email contacts identified by the first user.

[0242] In some embodiments, the first interface display module 1602 is used to display an email service control in an instant messaging application logged in with a first user ID; and to display an email interface in response to a trigger operation on the email service control.

[0243] In some embodiments, the first contact adding module 1606 is configured to, in response to a triggering operation on the second email account in the email content interface, display an account adding control for the second email account when the second email account is not among the email contacts of the first user identifier; and in response to a triggering operation on the account adding control, add the second email account to the email contacts of the first user identifier.

[0244] In some embodiments, the device further includes a control display module, which is configured to display an operation pop-up window for the second email account in response to the selection operation of the second email account in the email content interface, the operation pop-up window including an account information viewing control; and to display an account addition control for the second email account in response to the triggering operation of the account information viewing control.

[0245] In some embodiments, the first contact adding module 1606 is configured to add the second email account to the email contacts of the first user's contacts in response to an add operation on the second email account, when the second email account is not among the email contacts of the first user's contacts and the domain name of the second email account is different from the domain name of the first email account.

[0246] In some embodiments, the device further includes a third interface display module, which is used to display an address book interface in an instant messaging application logged in with a first user identifier, the address book interface including a list of email contacts of the first user identifier; and to display an email editing interface in response to a trigger operation on a second email account in the email contact list, the email editing interface including the second email account as an email receiving account.

[0247] In some embodiments, the device further includes an email account display module, which is used to display an email editing interface in an instant messaging application logged in with a first user identifier, and to display a list of email contacts of the first user identifier in response to a trigger operation of adding a control to an email account; and to display a second email account in the email editing interface in response to a trigger operation of a second email account in the list of email contacts.

[0248] In some embodiments, the device further includes an email style display module, which is used to display an operation pop-up window about the second email account in response to a trigger operation on the second email account. The operation pop-up window includes an account tagging control. In response to a trigger operation on the account tagging control, the second email account is used as a tagged email account of the first user identifier. In the emails sent and received by the first user identifier, emails with the tagged email account as the sender and receiver are displayed in a preset style that is different from the remaining emails. The remaining emails are displayed in a normal style.

[0249] In some embodiments, the first contact adding module 1606 is further configured to, in response to a triggering operation of the quick add control, display a list of accounts to be selected, and in response to a selection operation of at least one second email account in the list of accounts to be selected, add at least one second email account to the email contacts of the first user identifier when the sending and receiving accounts of the target email include multiple second email accounts that are not second email contacts among the contacts of the first user identifier.

[0250] In some embodiments, the first contact adding module 1606 is further configured to, in response to the simultaneous addition operation of multiple second email accounts, add all the second email accounts to the email contacts of the first user's contacts when none of the second email accounts in the target email belong to the email contacts of the first user's contacts.

[0251] Based on the same inventive concept, this application also provides a contact adding device for implementing the contact adding method described above. The solution provided by this device is similar to the solution described in the above method; therefore, the specific limitations in one or more contact adding device embodiments provided below can be found in the limitations of the contact adding method described above, and will not be repeated here.

[0252] In one exemplary embodiment, such as Figure 17 As shown, a contact adding device 1700 is provided, including: a request query module 1702, a verification module 1704, and a second contact adding module 1706, wherein:

[0253] The request query module 1702 is used to receive an email contact query request sent through an instant messaging application. The instant messaging application is logged in with a first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with conversation contacts, and the first email account is used to communicate instantly with email contacts. The email contact query request includes a second email account to be added and the email identifier of the target email from which the second email account originates. The second email account belongs to the sending and receiving account of the target email, and the target email is an email sent and received by the first email account associated with the first user identifier.

[0254] The verification module 1704 is used to verify whether the second email identifier belongs to the email contacts of the first user identifier when the sender and receiver accounts of the email corresponding to the email identifier include the first email account and the second email account.

[0255] The second contact addition module 1706 is used to add the second email account to the email contacts of the first user's identified contacts when it is verified that the second email account does not belong to the email contacts of the first user's identified contacts.

[0256] In some embodiments, the verification module 1704 is configured to query the corresponding email contact list based on the first user identifier; if the email contact list contains the second email account, determine that the second email account belongs to the email contact among the contacts of the first user identifier; if the email contact list does not contain the second email account, determine that the second email account does not belong to the email contact among the contacts of the first user identifier.

[0257] In some embodiments, the second contact adding module 1706 is used to set the second email account as the corresponding email account of the first user by synchronizing the email correspondence records between the first email account and the second email account; and, if the account information corresponding to the second email account is stored, to update the corresponding email account to the email contact in the contacts of the first user.

[0258] In some embodiments, the apparatus further includes a storage module, configured to receive a tagging request for a second email account sent via a first user identifier, the tagging request including the second email account and a preset pattern for tagging the second email account; and to store the preset pattern and the second email account correspondingly in tagging data about the first user identifier.

[0259] In some embodiments, the device further includes a preset style determination module, which is configured to receive an email from a target email account, wherein the recipient of the email is a first email account; if the target email account and the first email account do not belong to the same group, verify whether the target email account belongs to an email contact of a first user identifier; if the target email account is found to belong to an email contact of the first user identifier, query the corresponding tag data according to the first user identifier; if the tag data indicates a preset style for emails originating from the target email account, then while forwarding the email to the first email account, return the preset style to instruct the instant messaging application to display the received email according to the preset style.

[0260] The various modules in the aforementioned contact adding device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0261] In one exemplary embodiment, a computer device is provided, which may be a server or a terminal, and its internal structure diagram may be as follows. Figure 18As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and databases. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media to run. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a contact addition method.

[0262] Those skilled in the art will understand that Figure 18 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0263] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0264] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0265] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0266] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0267] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0268] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0269] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for adding contacts, characterized in that, The method includes: In an instant messaging application logged in with a first user identifier, an email interface is displayed. The email interface is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with the conversation contacts, and the first email account is used to communicate instantly with the email contacts. In response to a trigger operation on a target email in the email interface, the email content interface of the target email is displayed, the email content interface including the sending and receiving accounts of the target email, and the sending and receiving accounts including a second email account; If the second email account is not among the email contacts of the first user's contacts, in response to the add operation of the second email account in the email content interface, the second email account is added to the email contacts of the first user's contacts.

2. The method according to claim 1, characterized in that, The provision of an email interface in an instant messaging application logged in with a first user ID includes: Display email service controls in instant messaging applications where the user logs in with the first user ID; In response to a trigger operation on the email service control, the email interface is displayed.

3. The method according to claim 1, characterized in that, When the second email account is not among the email contacts of the first user identifier, in response to the add operation of the second email account in the email content interface, the second email account is added to the email contacts of the first user identifier, including: If the second email account is not among the email contacts of the first user identifier, in response to the triggering operation on the second email account in the email content interface, an account addition control for the second email account is displayed; In response to a triggered operation on the account addition control, the second email account is added to the email contacts of the first user's contacts.

4. The method according to claim 3, characterized in that, In response to a triggering operation on the second email account in the email content interface, an account addition control for the second email account is displayed, including: In response to the selection of the second email account in the email content interface, an operation pop-up window for the second email account is displayed, the operation pop-up window including an account information viewing control; In response to a triggering operation on the account information viewing control, an account addition control for the second email account is displayed.

5. The method according to claim 1, characterized in that, When the second email account is not among the email contacts of the first user identifier, in response to the add operation of the second email account in the email content interface, the second email account is added to the email contacts of the first user identifier, including: If the second email account is not among the email contacts of the first user identifier and the domain name of the second email account is different from the domain name of the first email account, in response to the addition operation of the second email account, the second email account is added to the email contacts of the first user identifier.

6. The method according to claim 1, characterized in that, After adding the second email account to the email contacts of the first user identifier, the method further includes: In an instant messaging application logged in with the first user identifier, an address book interface is displayed, which includes a list of email contacts for the first user identifier. In response to a triggered operation on the second email account in the email contact list, an email editing interface is displayed, which includes the second email account as the email receiving account.

7. The method according to claim 1, characterized in that, After adding the second email account to the email contacts of the first user identifier, the method further includes: In the instant messaging application logged in with the first user identifier, an email editing interface is displayed. In response to a trigger operation that adds a control to the email account, a list of email contacts for the first user identifier is displayed. In response to a trigger operation that adds a second email account to the email contacts list, the second email account is displayed in the email editing interface.

8. The method according to claim 1, characterized in that, After adding the second email account to the email contacts of the first user identifier, the method further includes: In response to a triggering operation on the second email account, an operation pop-up window about the second email account is displayed, the operation pop-up window including an account tagging control; In response to a trigger operation on the account tagging control, the second email account is used as the tagging email account of the first user identifier; In the emails sent and received by the first user identifier, emails with the marked email account as the sender and receiver will be displayed in a preset style that differs from the remaining emails, which will be displayed in a normal style.

9. The method according to claim 1, characterized in that, The email content interface also includes a quick add control. After displaying the email content interface of the target email, the method further includes: If the sender and receiver accounts of the target email include multiple second email accounts of email contacts that are not among the contacts of the first user identifier, in response to the triggering operation of the quick add control, a list of accounts to be selected is displayed; In response to the selection of at least one second email account from the list of accounts to be selected, the at least one second email account is added to the email contacts of the contacts of the first user identifier.

10. The method according to any one of claims 1 to 9, characterized in that, There are multiple second email accounts. After displaying the email content interface of the target email, the method further includes: If none of the second email accounts in the target email belong to the email contacts of the first user's contacts, in response to the simultaneous addition operation of multiple second email accounts, all of the multiple second email accounts are added to the email contacts of the first user's contacts.

11. A method for adding contacts, characterized in that, The method includes: The system receives an email contact query request sent through an instant messaging application. The instant messaging application is logged in with a first user identifier, and the instant messaging application's address book includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used for instant messaging with the conversation contacts, and the first email account is used for instant messaging with the email contacts. The email contact query request includes a second email account to be added and an email identifier of a target email from which the second email account originates. The second email account belongs to the sending and receiving account of the target email, and the target email is an email sent and received through the first email account associated with the first user identifier. If the email sending and receiving accounts corresponding to the email identifier include the first email account and the second email account, then based on the second email account, verify whether the second email identifier belongs to the email contacts of the first user identifier. If the verification shows that the second email account does not belong to the email contacts of the first user's contacts, then the second email account is added to the email contacts of the first user's contacts.

12. The method according to claim 11, characterized in that, The step of verifying whether the second email address belongs to the email contacts of the first user's contacts based on the second email account includes: Based on the first user identifier, retrieve the corresponding email contact list; If the email contact list contains the second email account, it is determined that the second email account belongs to the email contact among the contacts of the first user identifier; If the second email account is not included in the email contact list, it is determined that the second email account is not an email contact among the contacts of the first user identifier.

13. The method according to claim 11, characterized in that, The step of adding the second email account to the contacts of the first user identifier includes: By synchronizing the email correspondence between the first email account and the second email account, the second email account is set as the corresponding email account of the first user identifier; If the account information corresponding to the second email account is stored, the corresponding email account is updated to the email contact in the contacts of the first user identifier.

14. The method according to claim 11, characterized in that, The method further includes: Receive a tagging request for the second email account sent via the first user identifier, the tagging request including the second email account and a preset style for tagging the second email account; The preset style and the second email account are stored in the tag data about the first user identifier.

15. The method according to claim 11, characterized in that, The method further includes: Receive emails from the target email account, where the recipient of the emails is the first email account; If the target email account and the first email account do not belong to the same group, verify whether the target email account belongs to the email contact of the first user identifier; When it is verified that the target email account belongs to the email contact of the first user identifier, the corresponding tag data is queried according to the first user identifier; If the tagging data indicates a preset style for emails originating from the target email account, then while forwarding the email to the first email account, the preset style is returned to instruct the instant messaging application to display the received email according to the preset style.

16. A contact adding device, characterized in that, The device includes: The first interface display module is used to display an email interface in an instant messaging application logged in with a first user identifier. The email interface is the email interface of the first email account associated with the first user identifier. The address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with the conversation contacts, and the first email account is used to communicate instantly with the email contacts. The second interface display module is used to respond to the trigger operation of the target email in the email interface and display the email content interface of the target email. The email content interface includes the sending and receiving accounts of the target email, and the sending and receiving accounts include the second email account. The first contact addition module is used to add the second email account to the email contacts of the first user's contacts in response to the addition operation of the second email account in the email content interface when the second email account is not among the email contacts of the first user's contacts.

17. A contact adding device, characterized in that, The device includes: The request query module is used to receive email contact query requests sent through an instant messaging application. The instant messaging application is logged in with a first user identifier, and the address book of the instant messaging application includes contacts of the first user identifier. The contacts include conversation contacts and email contacts. The first user identifier is used to communicate instantly with the conversation contacts, and the first email account is used to communicate instantly with the email contacts. The email contact query request includes a second email account to be added and an email identifier of the target email from which the second email account originates. The second email account belongs to the sending and receiving account of the target email, and the target email is an email sent and received through the first email account associated with the first user identifier. The verification module is used to verify, based on the second email account, whether the second email identifier belongs to the email contacts of the first user identifier when the sending and receiving accounts of the email corresponding to the email identifier include the first email account and the second email account. The second contact addition module is used to add the second email account to the email contacts of the first user's identified contacts when it is verified that the second email account does not belong to the email contacts of the first user's identified contacts.

18. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 15.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

20. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 15.

Images