Contact management method and apparatus, electronic device, and readable storage medium

Abstract

The present application relates to the technical field of electronic devices, and discloses a contact management method and apparatus, an electronic device, and a readable storage medium. The contact management method comprises: receiving a first input in respect of a first contact identifier of a first social application; in response to the first input, executing a first operation on a first contact corresponding to the first contact identifier, and displaying at least one associated contact identifier, wherein an associated contact corresponding to the associated contact identifier and the first contact are the same registered user; receiving a second input in respect of a target associated contact identifier among the at least one associated contact identifier; and in response to the second input, executing the first operation on an associated contact corresponding to the target associated contact identifier.

Description

Contact management methods, devices, electronic devices, and readable storage media

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410510811.X, filed on April 25, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of electronic equipment technology, and specifically relates to a contact management method, apparatus, electronic device, and readable storage medium. Background Technology

[0004] With the development of electronic devices, the functions supported by applications on electronic devices are becoming increasingly rich. For example, applications can not only provide users with dynamic sharing and conversation functions, but also provide users with various function settings such as pinning, do not disturb, and blocking.

[0005] In existing technologies, the settings of different applications are independent of each other, and a user usually registers accounts in multiple applications. Thus, if user A wants to perform the same operation on user B's registered accounts in different applications, it is necessary to set up user B's registered accounts separately in each application, which is cumbersome. Summary of the Invention

[0006] The purpose of this application is to provide a contact management method, apparatus, electronic device, and readable storage medium that can solve the problem of cumbersome operations in the prior art for performing operations on the same user's registered accounts in different applications.

[0007] In a first aspect, embodiments of this application provide a contact management method, which includes:

[0008] Receive the first input for the identifier of the first contact in the first social application;

[0009] In response to the first input, a first operation is performed on the first contact corresponding to the first contact identifier, and at least one associated contact identifier is displayed; the associated contact corresponding to the associated contact identifier is the same registered user as the first contact.

[0010] Receive a second input for a target associated contact identifier among the at least one associated contact identifiers;

[0011] In response to the second input, the first operation is performed on the associated contact corresponding to the target associated contact identifier.

[0012] Secondly, embodiments of this application provide a contact management device, the contact management device comprising:

[0013] The first receiving module is used to receive a first input for the first contact identifier of the first social application;

[0014] A first execution module is configured to, in response to the first input, perform a first operation on the first contact corresponding to the first contact identifier, and display at least one associated contact identifier; the associated contact corresponding to the associated contact identifier is the same registered user as the first contact.

[0015] The second receiving module is configured to receive a second input for a target associated contact identifier among the at least one associated contact identifier;

[0016] The second execution module is used to perform the first operation on the associated contact corresponding to the target associated contact identifier in response to the second input.

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

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

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

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

[0021] In this embodiment, after receiving a first input regarding a first contact identifier of a first social application, a first operation can be performed on the first contact identifier and its corresponding first contact in response to the first input, and at least one associated contact identifier can be displayed. The associated contact corresponding to the at least one associated contact identifier is the same registered user as the first contact. Subsequently, in response to a received second input regarding a target associated contact identifier among the at least one associated contact identifiers, a first operation can be performed on the associated contact corresponding to the target associated contact identifier. Therefore, in this embodiment, when it is desired to perform the same operation on contact accounts registered by the same registered user, it is not necessary to enter the application where each contact account resides for individual settings. By executing the first and second inputs, unified operation settings for contact accounts registered by the same registered user can be achieved, reducing operational complexity. Attached Figure Description

[0022] Figure 1 is a flowchart of the contact management method provided in an embodiment of this application;

[0023] Figure 2a is a schematic diagram of the first input provided in an embodiment of this application;

[0024] Figure 2b is a schematic diagram of the operation window provided in an embodiment of this application;

[0025] Figure 3 is a schematic diagram of the data card provided in an embodiment of this application;

[0026] Figure 4a is one of the schematic diagrams of the contact association interface provided in the embodiments of this application;

[0027] Figure 4b is a second schematic diagram of the contact association interface provided in the embodiment of this application;

[0028] Figure 5a is a schematic diagram of the attention settings interface provided in an embodiment of this application;

[0029] Figure 5b is a schematic diagram of the encryption settings interface provided in an embodiment of this application;

[0030] Figure 5c is a schematic diagram of the hidden settings interface provided in an embodiment of this application;

[0031] Figure 5d is a schematic diagram of the blacklist settings interface provided in an embodiment of this application;

[0032] Figure 6a is one of the schematic diagrams of the social sharing information summary interface provided in the embodiments of this application;

[0033] Figure 6b is a second schematic diagram of the social sharing information aggregation interface provided in the embodiments of this application;

[0034] Figure 7a is one of the schematic diagrams of the social sharing information aggregation component provided in the embodiments of this application;

[0035] Figure 7b is a second schematic diagram of the social sharing information aggregation component provided in an embodiment of this application;

[0036] Figure 7c is a third schematic diagram of the social sharing information aggregation component provided in the embodiments of this application;

[0037] Figure 8 is a schematic diagram of the contact management control provided in an embodiment of this application;

[0038] Figure 9a is one of the schematic diagrams of the contact management interface provided in the embodiments of this application;

[0039] Figure 9b is a second schematic diagram of the contact management interface provided in an embodiment of this application;

[0040] Figure 9c is a third schematic diagram of the contact management interface provided in the embodiments of this application;

[0041] Figure 9d is a fourth schematic diagram of the contact management interface provided in the embodiment of this application;

[0042] Figure 10a is a fifth schematic diagram of the contact management interface provided in the embodiments of this application;

[0043] Figure 10b is a sixth schematic diagram of the contact management interface provided in the embodiments of this application;

[0044] Figure 10c is the seventh schematic diagram of the contact management interface provided in the embodiments of this application;

[0045] Figure 10d is the eighth schematic diagram of the contact management interface provided in the embodiment of this application;

[0046] Figure 11a is a schematic diagram of data viewing provided in an embodiment of this application;

[0047] Figure 11b is a schematic diagram of the user addition interface provided in an embodiment of this application;

[0048] Figure 12a is one of the schematic diagrams of the second operation provided in the embodiments of this application;

[0049] Figure 12b is a second schematic diagram of the second operation provided in the embodiments of this application;

[0050] Figure 12c is a third schematic diagram of the second operation provided in the embodiments of this application;

[0051] Figure 12d is a fourth schematic diagram of the second operation provided in the embodiments of this application;

[0052] Figure 13a is a verification schematic diagram provided in an embodiment of this application;

[0053] Figure 13b is one of the schematic diagrams illustrating the selection of the contact identifier provided in the embodiments of this application;

[0054] Figure 13c is a second schematic diagram of the selection of contact identifier provided in an embodiment of this application;

[0055] Figure 14 is a structural diagram of the contact management device provided in an embodiment of this application;

[0056] Figure 15 is a structural diagram of an electronic device provided in an embodiment of this application;

[0057] Figure 16 is a second structural diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

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

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

[0060] The contact management method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0061] The contact management method of this application embodiment can be executed by an electronic device, and the user using the electronic device is hereinafter referred to as the first user.

[0062] In this embodiment, a user can be understood as a unique person. Users can connect with other users by registering an account within an application (hereinafter referred to as an application); therefore, a user's registered account within an application can be called a contact. The same user's registered accounts in different applications can be referred to as related contacts.

[0063] As shown in Figure 1, contact management methods may include:

[0064] Step 101: Receive first input for the first contact identifier of the first social application.

[0065] The first contact identifier is the identifier of the first contact person. In the embodiments of this application, the contact identifier can be any identifier that can uniquely identify the contact person. In some embodiments, the contact identifier can be any of the following: avatar, nickname, remarks, contact information, conversation entry, conversation page, social sharing information (i.e. dynamic information).

[0066] The embodiments of this application do not limit the display interface of the first contact identifier. In some embodiments, the first contact identifier may be displayed on any of the following pages of the first social application: the conversation list page, the first contact's conversation box page, the address book list page, the first contact's profile page, or the dynamic post page.

[0067] The embodiments of this application do not limit the specific form of the first input. The first input can be: at least one click input, swipe input, long press input, etc.

[0068] In one example, as shown in Figure 2a, step 101 specifically involves receiving a long-press input on the identifier of contact 2 in the address book list page of the first social application. That is, in Figure 2a, the first contact is contact 2, and the identifier of the first contact is displayed in the address book list page of the first social application; the first input is a long-press input.

[0069] The first input is used to trigger the electronic device to perform unified operation and management on the different registered accounts of the second user. The specific response of the electronic device to the first input can be found in step 102, where the second user is the registered user of the first contact person.

[0070] Step 102: In response to the first input, perform a first operation on the first contact corresponding to the first contact identifier and display at least one associated contact identifier; the associated contact corresponding to the associated contact identifier is the same registered user as the first contact.

[0071] In step 102, the electronic device responds to the first input by performing the following two actions: a) performing a first operation on the first contact; b) displaying at least one associated contact identifier, i.e., displaying the identifier of another registered account of the second user.

[0072] The following provides a detailed explanation of the two actions mentioned above.

[0073] I. Regarding a).

[0074] The electronic device responds to the first input and performs a first operation on the first contact. The first operation can be an action such as following, encrypting, hiding, or blocking.

[0075] In some embodiments, the first operation may be preset.

[0076] In other embodiments, the first operation can be determined based on the input type of the first input. In these embodiments, the user can trigger the electronic device to perform different operations on the first contact by performing different types of first inputs. Specifically, the electronic device can pre-set the correspondence between input types and operation types, such as: long press corresponds to a follow operation, double-click corresponds to an encryption operation, etc. After receiving the first input, the electronic device can determine the input type of the first input, then determine the operation corresponding to that input type as the first operation, and perform the first operation on the first contact.

[0077] In other embodiments, the step of performing a first operation on the first contact corresponding to the first contact identifier and displaying at least one associated contact identifier in response to the first input may include:

[0078] In response to the first input, an operation window is displayed; the operation window includes at least one operation option.

[0079] Receive a ninth input for a first operation option among the at least one operation options;

[0080] In response to the ninth input, the first operation corresponding to the first operation option is performed on the first contact corresponding to the first contact identifier, and at least one associated contact identifier is displayed.

[0081] In this embodiment, the electronic device, in response to the first input, can display an operation window, where each operation option corresponds to an operation. The user can interact with the operation options in the operation window to trigger the electronic device to determine the first operation.

[0082] In specific implementations, in some ways, the electronic device can respond to the first input and display an operation window on the interface of the first social application; that is, the operation window is displayed floating on the current interface of the electronic device. In other implementations, the electronic device can respond to the first input and switch the displayed operation window; that is, the electronic device jumps from the current interface to the operation window.

[0083] For easier understanding, please refer to Figure 2b. In Figure 2b, the operation window is displayed floating on the interface of the first social application, including operation options such as follow, encrypt, hide, or block.

[0084] In Figure 2b, if the user inputs the "Follow" option, the electronic device can perform a "Follow" operation on the first contact; that is, the first operation is a "Follow" operation. If the user inputs the "Encrypt" option, the electronic device can perform an "Encrypt" operation on the first contact; that is, the first operation is an "Encrypt" operation. If the user inputs the "Hide" option, the electronic device can perform a "Hide" operation on the first contact; that is, the first operation is a "Hide" operation. If the user inputs the "Block" option, the electronic device can perform a "Block" operation on the first contact; that is, the first operation is a "Block" operation.

[0085] In this way, users can independently and explicitly select the type of operation to be performed on a contact through the operation window, which can improve the accuracy of contact management.

[0086] In this embodiment of the application, performing a first operation on a contact person can specifically mean performing a first operation on the contact person's relevant information.

[0087] The relevant information of a contact may include at least one of the following of the first contact: conversation entry, conversation notification method, identifier, dynamic information, interactive information, conversation content, files, transaction records, etc.

[0088] II. Regarding b)

[0089] In response to the first input, the electronic device may display at least one associated contact identifier.

[0090] The associated contact corresponding to the at least one associated contact identifier is the same registered user as the first contact, and both are second users. Therefore, the associated contact corresponding to the at least one associated contact identifier, i.e., the associated contact of the first contact, is another registered account of the second user.

[0091] Since the first contact and its associated contacts are registered by the same user, their contact information may have the same or similar parts. The contact information may include at least one of the following: avatar, nickname, notes, account, contact information, tags, address, etc.

[0092] Based on this, after responding to the first input, the electronic device can first obtain the information of the first contact. In one example, as shown in Figure 3, the electronic device can obtain the information of the first contact from the profile card of the first contact in the first social application.

[0093] Then, the information of the first contact can be matched with the information of contacts in other social applications. If the information of a contact in another social application matches the information of the first contact more than the matching threshold, it can be determined that the two were registered by the same user and can be identified as the first contact's associated contact.

[0094] After determining the associated contacts of the first contact, the electronic device may respond to the first input by jumping to display at least one associated contact identifier, or by displaying at least one associated contact identifier in a floating window. The specific settings can be configured according to actual needs, and this application embodiment does not limit this.

[0095] In this embodiment, the associated contact identifier is the identifier corresponding to the associated contact. Specifically, the identifier corresponding to the associated contact can be: the identifier of the associated contact; or, the identifier of the registered application of the associated contact, such as: the application's icon, name, etc.

[0096] In b), by displaying at least one associated contact identifier, users can easily select other registered accounts that the second user needs to operate uniformly.

[0097] Step 103: Receive a second input for the target associated contact identifier among the at least one associated contact identifiers.

[0098] The first user can select other registered accounts that the second user needs to operate uniformly by executing the second input.

[0099] In practice, the second input is used to select a target associated contact identifier from at least one associated contact identifier, triggering the electronic device to perform the same operation on the associated contact corresponding to the target associated contact identifier as on the first contact.

[0100] The target associated contact identifier may include some or all of the associated contact identifiers from at least one associated contact identifier.

[0101] Step 104: In response to the second input, perform the first operation on the associated contact corresponding to the target associated contact identifier.

[0102] In this way, electronic devices can perform unified operations on different registered accounts of a second user, which can simplify the complexity of operations.

[0103] The contact management method of this application embodiment, upon receiving a first input regarding a first contact identifier of a first social application, can, in response to the first input, perform a first operation on the first contact identifier and its corresponding first contact, and display at least one associated contact identifier, wherein the associated contact corresponding to the at least one associated contact identifier is the same registered user as the first contact. Subsequently, in response to a received second input regarding a target associated contact identifier among the at least one associated contact identifiers, the first operation can be performed on the associated contact corresponding to the target associated contact identifier. Therefore, in this application embodiment, when it is desired to perform the same operation on contact accounts registered by the same registered user, it is not necessary to enter the application where each contact account resides for individual settings. By executing the first and second inputs, unified operation settings for contact accounts registered by the same registered user can be achieved, reducing operational complexity.

[0104] In some embodiments, the display parameters of the at least one associated contact identifier are determined based on the activity level of the associated contact corresponding to the at least one associated contact identifier.

[0105] The display parameters of an icon may include at least one of the following: display size, display shape, and display color.

[0106] A contact's activity level can be determined based on at least one of the following: the contact's online duration and frequency. A contact's activity level can be positively correlated with their online duration and frequency; that is, the longer the contact's online time and the greater the frequency, the higher their activity level, and vice versa.

[0107] In practice, the relationship between the display parameters of the contact identifier and the contact's activity level can be preset. After obtaining the contact's activity level, the display parameters of the contact identifier can be determined based on the above relationship.

[0108] In one example, the display parameter can be represented as the display size. The activity level of a contact can be positively correlated with the display size of the contact icon; that is, the higher the activity level of a contact, the larger the display size of the contact icon, and vice versa.

[0109] In this way, the first user can know the activity level of a contact through the contact identifier, making it convenient for the user to select the second user's registered account for unified operation and improving the accuracy of contact management.

[0110] In some embodiments, displaying at least one associated contact identifier may include:

[0111] The contact association interface is displayed; the contact association interface includes at least one associated contact identifier.

[0112] In this embodiment, the electronic device can display at least one associated contact icon through the contact association interface, thereby improving the neatness of the associated contact icon display.

[0113] The embodiments of this application do not limit the specific presentation of the contact association interface.

[0114] In some implementations, the contact association interface may include a first area, a second area, and a first confirmation control; the at least one associated contact identifier includes a first associated contact identifier, which is located in the second area;

[0115] The contact management method may also include:

[0116] Receive a third input regarding the identifier of the first associated contact;

[0117] In response to the third input, the first associated contact identifier is moved to the first area;

[0118] The receiving of a second input for a target associated contact identifier among the at least one associated contact identifier includes:

[0119] Receive a second input to the first confirmation control;

[0120] The first operation, performed in response to the second input, on the associated contact corresponding to the target associated contact identifier, includes:

[0121] In response to the second input, the first operation is performed on the associated contact corresponding to the associated contact identifier in the first region.

[0122] In this embodiment, the contact association interface includes a first area and a second area. The first area can be used to display the identifiers of associated contacts who are expected to perform the same operation as the first contact, and the second area can be used to display the identifiers of associated contacts who are expected not to perform the same operation as the first contact.

[0123] The first user can trigger the electronic device to perform the same operation on the associated contact corresponding to the associated contact in the second area and the first contact by moving the associated contact icon from the second area to the first area.

[0124] For clarity, please refer to Figure 4a. In Figure 4a, 1 to 9 represent associated contact identifiers, with associated contact identifier 9 being the first associated contact identifier. Before the third input is executed, associated contact identifier 9 is displayed in the second area. If the first user wishes to perform the same operation on the associated contact corresponding to associated contact identifier 9 as on the first contact, they can execute the third input to move associated contact identifier 9 to the first area. Afterward, if the first user touches the confirmation control, all associated contact identifiers in the first area can be designated as the target associated contact identifier, including associated contact identifier 9, and the first operation can be performed on the associated contact corresponding to the target associated contact identifier.

[0125] In this embodiment, the first user can select the target associated contact ID by adjusting the display area of ​​the associated contact ID in the contact association interface, thereby improving the flexibility and fun of selecting the target associated contact ID.

[0126] In other embodiments, the contact association interface includes a seventh area, an eighth area, and a second confirmation control; the social application corresponding to the associated contact identifier in the seventh area contains the associated contact of the first contact; the social application corresponding to the associated contact identifier in the eighth area does not contain the associated contact of the first contact.

[0127] Before receiving the second input for at least a portion of the associated contact identifiers among the at least one associated contact identifier, the contact management method further includes:

[0128] Add the associated contact corresponding to the associated contact identifier in the seventh region to the candidate associated contact list corresponding to the first contact;

[0129] Receive the twelfth input for the fourth associated contact identifier in the seventh region;

[0130] In response to the twelfth input, the associated contact corresponding to the fourth associated contact identifier is deleted from the candidate associated contact list;

[0131] Receive the thirteenth input for the fifth associated contact identifier in the eighth region;

[0132] In response to the thirteenth input, if a new associated contact corresponding to the first contact has been created in the social application corresponding to the fifth associated contact identifier, the associated contact corresponding to the fifth associated contact identifier is added to the candidate associated contact list;

[0133] The receiving of a second input for at least a portion of the associated contact identifiers in the at least one associated contact identifier includes:

[0134] Receive a second input to the second confirmation control;

[0135] The first operation, performed in response to the second input, on the associated contacts corresponding to the at least partial associated contact identifiers, includes:

[0136] In response to the second input, the first operation is performed on the associated contact corresponding to the associated contact identifier in the candidate associated contact list.

[0137] In this embodiment, the electronic device can divide the installed applications into two categories based on whether the installed applications have a second user's account, that is, whether the installed applications have an associated contact of the first contact: the first category of applications are those with an associated contact corresponding to the first contact, and the second category of applications are those without an associated contact corresponding to the first contact.

[0138] Accordingly, the contact association interface can be divided into a seventh area and an eighth area. The seventh area is used to display the identifiers of associated contacts in the first type of applications, and the eighth area is used to display the application icons of the second type of applications.

[0139] Since the identifiers displayed in the seventh area all correspond to the identifiers of the first contact's associated contacts, all associated contacts corresponding to the identifiers in the seventh area can be directly added to the second user's candidate associated contact list. To improve the flexibility of selecting associated contacts, the first user can interact with the identifiers in the seventh area to delete their corresponding associated contacts from the candidate associated contact list.

[0140] Although the application corresponding to the identifier in the eighth area does not currently have a registered account of the second user, in this embodiment, the first user can pre-select the application corresponding to the identifier. In this way, if the electronic device detects that the application corresponding to the identifier in the eighth area has created a new associated contact of the first contact, it can add the associated contact to the candidate associated contact list immediately, thereby reducing the probability of missing the first contact's associated contact.

[0141] The embodiments of this application do not limit the interaction method between the first user and the identifier. In some implementations, it can be a long press or a click on the identifier. In other implementations, a "remove" control can be displayed at the corresponding position of the identifier in the seventh area, and an "add" control can be displayed at the corresponding position of the identifier in the eighth area. In the example shown in Figure 4b, the "remove" control is represented by "-", and the "add" control is represented by "+".

[0142] First, users can remove the associated contact from the list of candidate associated contacts by touching the "Remove" control corresponding to the icon; and select the application corresponding to the icon by touching the "Add" control corresponding to the icon.

[0143] After the first user completes the selection, they can touch the second confirmation control to confirm the second user's candidate associated contact list. The electronic device can then identify all associated contact identifiers in the second user's candidate associated contact list as target associated contact identifiers and perform the first operation on the associated contacts corresponding to the target associated contact identifiers.

[0144] In this embodiment, the electronic device can default the associated contacts of the first contact in the application to the candidate associated contacts who perform the same operation as the first contact. In addition, for applications that do not have associated contacts of the first contact, the application can be selected in advance. In this way, if the electronic device detects that the application has created an associated contact of the first contact, it can add the associated contact to the candidate associated contact list as soon as possible, thereby reducing the probability of missing the associated contacts of the first contact.

[0145] In some embodiments of this application, performing the first operation on the associated contact corresponding to the target associated contact identifier in response to the second input may include:

[0146] In response to the second input, the first operation settings interface is displayed;

[0147] Receive the fourth input to the first operation settings interface;

[0148] In response to the fourth input, the first operation is performed on the associated contact corresponding to the target associated contact identifier based on the operation setting information corresponding to the first operation setting interface.

[0149] Furthermore, the electronic device can perform a first operation on the first contact based on the operation settings information corresponding to the first operation settings interface.

[0150] In this embodiment, to clarify the specific implementation of the first operation, the electronic device may respond to the second input by first displaying the first operation setting interface, so that the first user can set the specific operation information of the first operation through the first operation setting interface.

[0151] The embodiments of this application do not limit the specific content of the first operation settings interface.

[0152] If the first action is to follow, the first action settings interface will be the follow settings interface, which can be, but is not limited to, the one shown in Figure 5a. In Figure 5a, the follow settings information can include: pinning the conversation, receiving dynamic notifications, special notification sound, special follow icon, summarizing and displaying the TA's dynamics across multiple applications, and adding the TA's latest dynamics to the desktop.

[0153] If the first operation is encryption, the first operation settings interface will be the encryption settings interface, which can be, but is not limited to, the one shown in Figure 5b. In Figure 5b, the encryption settings information can include: encrypting instant messages and incoming calls, encrypting conversation content, encrypting status updates and interactions, encrypting photos containing the other party, encrypting files from the other party, and encrypting transaction records.

[0154] If the first operation is to hide, the first operation settings interface will be the hiding settings interface, which can be, but is not limited to, as shown in Figure 5c. In Figure 5c, the hiding settings information can include: hiding instant messages and call logs, hiding conversation content, hiding activity and interactions, hiding photos containing the other party, hiding files from the other party, and hiding transaction records.

[0155] If the first action is to block, the first action settings interface will be the block settings interface, which can be, but is not limited to, the one shown in Figure 5d. In Figure 5d, the block settings information can include: refusing to receive messages and calls from the other party, unfollowing all accounts of the other party, not showing the other party's activity feed, refusing to receive files from the other party, refusing to receive transfers from the other party, and deleting all information related to the other party.

[0156] In Figures 5a to 5d, each operation setting information corresponds to a switch control. If the corresponding switch control is "on", it means that the operation setting information is selected; if the corresponding switch control is "off", it means that the operation setting information is not selected. The first user can select the operation setting information by changing the on / off state of the switch control corresponding to the operation setting information.

[0157] As shown in Figures 5a to 5d, a prompt message can be displayed on the first operation settings interface to indicate which contact's operation settings interface is currently being set.

[0158] In this embodiment, the electronic device can perform a first operation on the first contact and its associated contacts based on the operation settings information selected by the first user in the first operation settings interface. This makes the specific implementation of the first operation conform to the expectations of the first user, thereby improving the reliability of contact management.

[0159] In some embodiments, the first operation is a focus operation;

[0160] The contact management method also includes:

[0161] Receive a fifth input regarding the identifier of the first contact;

[0162] In response to the fifth input, a social sharing information summary interface corresponding to the first contact identifier is displayed; the social sharing information summary interface includes a third area and a fourth area, the third area including the first contact identifier and the at least one associated contact identifier;

[0163] Receive a sixth input for the second associated contact identifier in the third region;

[0164] In response to the sixth input, the social sharing information of the associated contact corresponding to the second associated contact identifier in the social application corresponding to the second associated contact identifier is displayed in the fourth area.

[0165] In this embodiment, the aforementioned "dynamic summary display of TA across multiple applications" can be achieved through a social sharing information aggregation interface.

[0166] In a specific implementation, the first user can interact with the first contact's identifier to trigger the electronic device to display the social sharing information summary interface corresponding to the first contact's identifier, which is the second user's social sharing information summary interface. However, this does not limit the way the second user's social sharing information summary interface is displayed. In other embodiments, the first user can also interact with the associated contact identifier of the first contact to trigger the electronic device to display the second user's social sharing information summary interface, but it is not limited to this.

[0167] The second user's social sharing information summary interface is a summary interface for viewing the social sharing information posted by the second user through different registered accounts. It can be used to display the social sharing information posted by the second user through different registered accounts.

[0168] This application does not limit the specific form of the social sharing information aggregation interface. In this embodiment, the social sharing information aggregation interface includes a third area and a fourth area. The third area is used to display contact identifiers, and the fourth area is used to display the social sharing information of the second user on the social application corresponding to a certain identifier. Furthermore, to help the first user know which social application's social sharing information is currently being displayed, the identifier corresponding to that social application can be highlighted in the third area.

[0169] In practice, the first user can interact with the contact icon in the third area to trigger the fourth area to switch and display the second user's social sharing information in different applications.

[0170] For easier understanding, please refer to Figures 6a and 6b. In Figure 6a, the fourth area displays the social sharing information of the second user in social application 1 corresponding to identifier 1. When the first user performs input on identifier 2, in response to this input, as shown in Figure 6b, the fourth area displays the social sharing information in social application 2 corresponding to identifier 2.

[0171] In this embodiment, the first user can view the social sharing information posted by the second user through different registered accounts in a unified manner through the social sharing information summary interface of the second user, without having to enter the corresponding social applications one by one, which can improve the viewing efficiency of social sharing information.

[0172] In some embodiments, the contact management method may further include:

[0173] Receive the seventh input to the social sharing information summary interface corresponding to the first contact identifier;

[0174] In response to the seventh input, a social sharing information aggregation component corresponding to the first contact identifier is displayed on the desktop interface.

[0175] In this embodiment, the aforementioned "adding TA's latest updates to the desktop" can be achieved through a social sharing information aggregation component.

[0176] In practice, the first user can interact with the social sharing information summary interface corresponding to the first contact's identifier to trigger the electronic device to display the social sharing information summary component corresponding to the first contact's identifier on the desktop interface, which is the second user's social sharing information summary component. However, this does not limit the way the second user's social sharing information summary component is displayed. In other embodiments, if the first user sets the switch control corresponding to "Add TA's latest activity to desktop" in the second user's follow settings interface to "on", the electronic device can be triggered to display the second user's social sharing information summary component, but it is not limited to this.

[0177] The second user's social sharing information summary component is a component for viewing the summary of social sharing information posted by the second user through different registered accounts. It can be used to display the social sharing information posted by the second user through different registered accounts.

[0178] In this embodiment, the first user can view all social sharing information posted by the second user through different registered accounts using the social sharing information aggregation component, without having to access each social application individually, thus improving the efficiency of viewing social sharing information. Furthermore, since the social sharing information aggregation component is displayed on the desktop, there is no need to perform a component retrieval operation compared to the social sharing information aggregation interface, further improving the efficiency of viewing social sharing information.

[0179] This application does not limit the specific form of the social sharing information aggregation component. In some embodiments, the social sharing information aggregation component includes a fifth area and a sixth area, wherein the fifth area includes the first contact identifier and the at least one associated contact identifier;

[0180] Receive an eighth input for the third associated contact identifier in the fifth region;

[0181] In response to the eighth input, the social sharing information of the associated contact corresponding to the third associated contact identifier in the social application corresponding to the third associated contact identifier is displayed in the sixth area.

[0182] In this embodiment, the social sharing information aggregation component includes a fifth area and a sixth area. The fifth area is used to display contact identifiers, and the sixth area is used to display social sharing information of a second user in a social application corresponding to a certain identifier.

[0183] In some implementations, the social sharing information aggregation component and the social sharing information aggregation interface can have the same appearance.

[0184] In some other implementations, the display state of the fifth area can be changed.

[0185] In practice, the fifth area can initially be in the first display state, only displaying the contact ID of the application to which the social sharing information currently displayed in the sixth area belongs.

[0186] When the first user wants to adjust the social applications displayed in the sixth area, they can input the application icon in the fifth area, triggering the electronic device to switch the fifth area's first display state to a second display state. In the second display state, the fifth area displays multiple contact icons of the second user. In this way, the first user can interact with the fifth area to adjust the social applications displayed in the sixth area.

[0187] In response to the first user's input of a contact identifier in the fifth area, the electronic device can, on the one hand, adjust the displayed content of the sixth area to the social sharing information posted by the second user through the social application corresponding to that contact identifier; on the other hand, the electronic device can switch the display state of the fifth area to a third display state. Both the third and first display states only display the contact identifier corresponding to the application to which the currently displayed social sharing information in the sixth area belongs. However, because the social application corresponding to the current displayed content in the sixth area changes, the contact identifier displayed in the fifth area in the third display state differs from that in the first display state.

[0188] For ease of understanding, please refer to Figures 7a to 7c. In Figure 7a, the fifth area is in the first display state, displaying contact identifier 1, and the sixth area displays the dynamic information posted by the second user through the social application 1 corresponding to contact identifier 1. After the first user performs input on contact identifier 1, the electronic device responds to the input by displaying the component shown in Figure 7b, and the fifth area is in the second display state, displaying multiple contact identifiers of the second user. At this time, the display content of the sixth area remains unchanged. After the first user performs input on contact identifier 2, the electronic device responds to the input by displaying the component shown in Figure 7c, and the fifth area is in the third display state, displaying contact identifier 2, and the sixth area displays the dynamic information posted by the second user through the social application 2 corresponding to contact identifier 2.

[0189] In this implementation, without needing to adjust the social applications corresponding to the content displayed in the sixth area, the fifth area only displays the contact icons corresponding to the content displayed in the sixth area. This allows the first user to quickly identify the contacts corresponding to the content displayed in the sixth area through the icons displayed in the fifth area, thus improving information retrieval efficiency.

[0190] It should be noted that when the first user views social sharing information posted by the second user through different registered accounts via the social sharing information aggregation component or the social sharing information aggregation interface, they can interact with the contact identifier in the social sharing information aggregation component or the social sharing information aggregation interface to quickly access the application interface of the application corresponding to the contact identifier. This can enrich the ways to access the application interface.

[0191] In addition, social sharing information aggregation components or interfaces can also support comments on social sharing information, thus improving the efficiency of comment sharing.

[0192] In some embodiments, the contact management method may further include:

[0193] Receive the tenth input;

[0194] In response to the tenth input, the contact management controls corresponding to each operation option are displayed;

[0195] Receive the eleventh input from the first contact management control in the contact management control corresponding to each of the operation options;

[0196] In response to the eleventh input, the contact management interface corresponding to the first contact management control is displayed.

[0197] In some implementations, as shown in Figure 8, the electronic device can display the contact management controls corresponding to each operation option through the "person relationship management card", but does not limit the display method of the contact management controls corresponding to each operation option.

[0198] The embodiments of this application do not limit the contact management interface.

[0199] In some implementations, if the first contact management control is a "following" management control, the contact management interface corresponding to the first contact management control can be the "My Following" management interface as shown in Figure 9a, which can display multiple followed users. The first user can interact with a user in this interface, triggering the electronic device to display the user's operation controls in this interface. In Figure 10a, the operation controls are represented by the following controls: TA's profile, TA's activity, and following settings.

[0200] In practice, the first user can touch the profile control of User 1 to trigger the electronic device to display User 1's profile interface as shown in Figure 11a. The first user can touch the activity feed of User 1 to trigger the electronic device to display a summary interface of social sharing information. The first user can touch the follow settings to trigger the electronic device to display the follow settings interface, and view or modify User 1's follow settings information.

[0201] In some implementations, if the first contact management control is an "encryption" management control, the contact management interface corresponding to the first contact management control can be the "My Encryption" management interface as shown in Figure 9b, which can display multiple encrypted users. The first user can interact with a user in this interface, triggering the electronic device to display the user's operation controls in this interface. In Figure 10b, the operation controls are represented by the following controls: TA's information and encryption settings.

[0202] In some implementations, if the first contact management control is a "hidden" management control, the contact management interface corresponding to the first contact management control can be the "My Hidden" management interface as shown in Figure 9c, which can display multiple hidden users. The first user can interact with a user in this interface, triggering the electronic device to display the user's operation controls in this interface. In Figure 10c, the operation controls are represented by the following controls: TA's profile, hidden settings, and hidden information viewing entry.

[0203] In practice, the first user can view a user's hidden information by touching the hidden information viewing entry control.

[0204] In some implementations, if the first contact management control is a "block" management control, the contact management interface corresponding to the first contact management control can be the "My Blacklist" management interface as shown in Figure 9d, which can display multiple blocked users. The first user can interact with a user in this interface, triggering the electronic device to display the user's operation controls in this interface. In Figure 10d, the operation controls are represented by the following controls: the user's profile and blocking settings.

[0205] In this embodiment, users can call the corresponding contact management interface through the contact management control to achieve unified management of contacts and further improve contact management efficiency.

[0206] Furthermore, the contact management interface can include an "Add" control, which is represented by a "+" symbol in Figures 10a to 10d. The first user can input information into the "Add" control, triggering the electronic device to display the user addition interface, allowing for the addition of the corresponding user and improving management efficiency.

[0207] In one example, the first user inputs information using the "Add" control in the "My Follows" management interface, and the electronic device can display the Add Follows interface as shown in Figure 11b. In the Add Follows interface shown in Figure 11b, the first user can enter information about a new user and select an application icon to have the electronic device follow the user's registered accounts in the applications corresponding to those icons.

[0208] In some embodiments of this application, after performing a first operation on the registered account of a second user, the electronic device can perform a second operation on the session entry and other related information of the registered account of the second user.

[0209] If the first operation is a follow operation, as shown in Figure 12a, the second operation may include: pinning the conversation entry of contact 2 to the top and displaying the "follow" icon in the conversation entry.

[0210] If the first operation is an encryption operation, as shown in Figure 12b, the second operation may include: encrypting the session entry identified by contact 2 and displaying an "encrypted" label on the session entry. In this case, if the user performs input on the session entry identified by contact 2, the electronic device may display an interface as shown in Figure 13a, prompting the user to enter a privacy password. Only after the privacy password is verified can the electronic device enter the session interface of contact 2.

[0211] If the first operation is a hiding operation, as shown in Figure 12c, the second operation may include: hiding the conversation entry of the contact 2 identifier and displaying a "hidden" identifier in the conversation entry.

[0212] If the first operation is to block, as shown in Figure 12d, the second operation may include: displaying a "Block" icon at the session entry point.

[0213] This allows the first user to be prompted with the appropriate actions for their contacts, making it easier for them to manage them.

[0214] In some embodiments, considering the need for the first user to batch determine management users, a method for quickly determining multiple management users can be provided to improve operational efficiency. Specifically, in response to received input for a contact identifier, as shown in Figure 13b, the electronic device can display a selection box (a bolded box), the size of which can be adjusted. As shown in Figure 13c, the first user can adjust the selection box according to their needs, making it include multiple contact identifiers. If a selection box overlaps with a contact identifier, the selection box is considered to include that contact identifier. After detecting that the first user has finished inputting, all included contact identifiers can be identified as the first contact identifier.

[0215] It should be noted that the various optional embodiments described in this application can be combined with each other or implemented individually without conflict, and this application does not limit the implementation of these embodiments.

[0216] The contact management method provided in this application can be executed by a contact management device. This application uses the execution of the contact management method by a contact management device as an example to illustrate the contact management device provided in this application.

[0217] As shown in Figure 14, the contact management device 1400 may include:

[0218] The first receiving module 1401 is used to receive a first input for the first contact identifier of the first social application;

[0219] The first execution module 1402 is configured to, in response to the first input, perform a first operation on the first contact corresponding to the first contact identifier, and display at least one associated contact identifier; the associated contact corresponding to the associated contact identifier is the same registered user as the first contact.

[0220] The second receiving module 1403 is configured to receive a second input for a target associated contact identifier among the at least one associated contact identifier;

[0221] The second execution module 1404 is configured to perform the first operation on the associated contact corresponding to the target associated contact identifier in response to the second input.

[0222] In some embodiments, the first execution module 1402 is configured to:

[0223] The contact association interface is displayed; the contact association interface includes at least one associated contact identifier.

[0224] In some embodiments, the contact association interface includes a first area, a second area, and a first confirmation control; the at least one associated contact identifier includes a first associated contact identifier, which is located in the second area;

[0225] The contact management device 1400 further includes:

[0226] The third receiving module is used to receive a third input regarding the identifier of the first associated contact.

[0227] A mobile module is configured to move the first associated contact identifier to the first area in response to the third input;

[0228] The second receiving module 1403 is used for:

[0229] Receive a second input to the first confirmation control;

[0230] The second execution module 1404 is used for:

[0231] In response to the second input, the first operation is performed on the associated contact corresponding to the associated contact identifier in the first region.

[0232] In some embodiments, the display parameters of the at least one associated contact identifier are determined based on the activity level of the associated contact corresponding to the at least one associated contact identifier.

[0233] In some embodiments, the second execution module 1404 includes:

[0234] The first display unit is configured to display a first operation setting interface in response to the second input;

[0235] The first receiving unit is used to receive the fourth input to the first operation setting interface;

[0236] The first execution unit is configured to respond to the fourth input and, based on the operation setting information corresponding to the first operation setting interface, perform the first operation on the associated contact corresponding to the target associated contact identifier.

[0237] In some embodiments, the first operation is a focus operation;

[0238] The contact management device 1400 further includes:

[0239] The fourth receiving module is used to receive a fifth input regarding the first contact identifier;

[0240] A first display module is configured to respond to the fifth input by displaying a social sharing information summary interface corresponding to the first contact identifier; the social sharing information summary interface includes a third area and a fourth area, the third area including the first contact identifier and the at least one associated contact identifier;

[0241] The fifth receiving module is used to receive a sixth input for the second associated contact identifier in the third region;

[0242] The second display module is used to respond to the sixth input by displaying, in the fourth area, the social sharing information of the associated contact corresponding to the second associated contact identifier in the social application corresponding to the second associated contact identifier.

[0243] In some embodiments, the contact management device 1400 further includes:

[0244] The sixth receiving module is used to receive the seventh input from the social sharing information summary interface corresponding to the first contact identifier;

[0245] The third display module is used to respond to the seventh input by displaying a social sharing information summary component corresponding to the first contact identifier on the desktop interface.

[0246] In some embodiments, the social sharing information aggregation component includes a fifth region and a sixth region, wherein the fifth region includes the first contact identifier and the at least one associated contact identifier;

[0247] The seventh receiving module is used to receive an eighth input for the third associated contact identifier in the fifth area;

[0248] The fourth display module is used to respond to the eighth input and display the social sharing information of the associated contact corresponding to the third associated contact identifier in the social application corresponding to the third associated contact identifier in the sixth area.

[0249] In some embodiments, the first execution module 1402 includes:

[0250] A second display unit is configured to display an operation window in response to the first input; the operation window includes at least one operation option.

[0251] The second receiving unit is configured to receive a ninth input for the first operation option among the at least one operation options;

[0252] The second execution unit is configured to, in response to the ninth input, perform the first operation corresponding to the first operation option on the first contact corresponding to the first contact identifier, and display at least one associated contact identifier.

[0253] In some embodiments, the contact management device 1400 further includes:

[0254] The eighth receiving module is used to receive the tenth input;

[0255] The fifth display module is used to respond to the tenth input by displaying the contact management controls corresponding to each operation option;

[0256] The ninth receiving module is used to receive the eleventh input to the first contact management control in the contact management control corresponding to each of the operation options;

[0257] The sixth display module is used to display the contact management interface corresponding to the first contact management control in response to the eleventh input.

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

[0259] The contact management device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit it.

[0260] The contact management device provided in this application embodiment can implement the various processes of the method embodiment, and will not be described again here to avoid repetition.

[0261] Optionally, as shown in FIG15, this application embodiment also provides an electronic device 1500, including a processor 1501 and a memory 1502. The memory 1502 stores a program or instructions that can run on the processor 1501. When the program or instructions are executed by the processor 1501, they implement the various steps of the above-described contact management method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

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

[0263] Figure 16 is a schematic diagram of the hardware structure of an electronic device that implements an embodiment of this application.

[0264] The electronic device 1600 includes, but is not limited to, components such as: radio frequency unit 1601, network module 1602, audio output unit 1603, input unit 1604, sensor 1605, display unit 1606, user input unit 1607, interface unit 1608, memory 1609, and processor 1610.

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

[0266] The user input unit 1607 is used to receive a first input for the identifier of a first contact in the first social application;

[0267] Processor 1610 is configured to, in response to the first input, perform a first operation on the first contact corresponding to the first contact identifier, and display at least one associated contact identifier through display unit 1606; the associated contact corresponding to the associated contact identifier is the same registered user as the first contact.

[0268] User input unit 1607 is configured to receive a second input for a target associated contact identifier among the at least one associated contact identifiers;

[0269] Processor 1610 is configured to perform the first operation on the associated contact corresponding to the target associated contact identifier in response to the second input.

[0270] In some embodiments, the display unit 1606 is used to display a contact association interface; the contact association interface includes the at least one associated contact identifier.

[0271] In some embodiments, the contact association interface includes a first area, a second area, and a first confirmation control; the at least one associated contact identifier includes a first associated contact identifier, which is located in the second area;

[0272] User input unit 1607 is used to receive a third input for the first associated contact identifier;

[0273] Processor 1610 is configured to move the first associated contact identifier to the first area in response to the third input;

[0274] User input unit 1607 is used to receive a second input to the first confirmation control;

[0275] Processor 1610 is configured to perform the first operation on an associated contact corresponding to an associated contact identifier in the first region in response to the second input.

[0276] In some embodiments, the display parameters of the at least one associated contact identifier are determined based on the activity level of the associated contact corresponding to the at least one associated contact identifier.

[0277] In some embodiments, the display unit 1606 is configured to display a first operation setting interface in response to the second input;

[0278] User input unit 1607 is used to receive a fourth input to the first operation setting interface;

[0279] The processor 1610 is configured to, in response to the fourth input, perform the first operation on the associated contact corresponding to the target associated contact identifier according to the operation setting information corresponding to the first operation setting interface.

[0280] In some embodiments, the first operation is a focus operation;

[0281] User input unit 1607 is used to receive a fifth input regarding the first contact identifier;

[0282] Display unit 1606 is configured to display a social sharing information summary interface corresponding to the first contact identifier in response to the fifth input; the social sharing information summary interface includes a third area and a fourth area, the third area including the first contact identifier and the at least one associated contact identifier;

[0283] User input unit 1607 is used to receive a sixth input for the second associated contact identifier in the third area;

[0284] Display unit 1606 is configured to, in response to the sixth input, display in the fourth area the social sharing information of the associated contact corresponding to the second associated contact identifier in the social application corresponding to the second associated contact identifier.

[0285] In some embodiments, the user input unit 1607 is configured to receive a seventh input to the social sharing information summary interface corresponding to the first contact identifier;

[0286] Display unit 1606 is used to display a social sharing information summary component corresponding to the first contact identifier on the desktop interface in response to the seventh input.

[0287] In some embodiments, the social sharing information aggregation component includes a fifth region and a sixth region, wherein the fifth region includes the first contact identifier and the at least one associated contact identifier;

[0288] User input unit 1607 is used to receive an eighth input for the third associated contact identifier in the fifth area;

[0289] Display unit 1606 is configured to, in response to the eighth input, display in the sixth area the social sharing information of the associated contact corresponding to the third associated contact identifier in the social application corresponding to the third associated contact identifier.

[0290] In some embodiments, the display unit 1606 is configured to display an operation window in response to the first input; the operation window includes at least one operation option;

[0291] User input unit 1607 is configured to receive a ninth input for a first operation option among the at least one operation options;

[0292] The processor 1610 is configured to, in response to the ninth input, perform a first operation corresponding to the first operation option on the first contact corresponding to the first contact identifier, and display at least one associated contact identifier through the display unit 1606.

[0293] In some embodiments, the user input unit 1607 is configured to receive a tenth input;

[0294] Display unit 1606 is used to display contact management controls corresponding to each operation option in response to the tenth input;

[0295] User input unit 1607 is used to receive the eleventh input to the first contact management control in the contact management control corresponding to each of the operation options;

[0296] Display unit 1606 is used to display the contact management interface corresponding to the first contact management control in response to the eleventh input.

[0297] The electronic device 1600 provided in this application embodiment can implement the various processes of the method embodiment, and will not be described again here to avoid repetition.

[0298] It should be understood that, in this embodiment, the input unit 1604 may include a graphics processing unit (GPU) 16041 and a microphone 16042. The GPU 16041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1606 may include a display panel 16061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1607 includes at least one of a touch panel 16071 and other input devices 16072. The touch panel 16071 is also called a touch screen. The touch panel 16071 may include a touch detection device and a touch controller. Other input devices 16072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

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

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

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

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

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

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

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

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

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

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

Claims

1. A contact management method, comprising: Receive the first input for the identifier of the first contact in the first social application; In response to the first input, a first operation is performed on the first contact corresponding to the first contact identifier, and at least one associated contact identifier is displayed; The associated contact identifier corresponds to the same registered user as the first contact. Receive a second input for a target associated contact identifier among the at least one associated contact identifiers; In response to the second input, the first operation is performed on the associated contact corresponding to the target associated contact identifier.

2. The method according to claim 1, wherein, The display of at least one associated contact identifier includes: The contact association interface is displayed; the contact association interface includes at least one associated contact identifier.

3. The method according to claim 2, wherein, The contact association interface includes a first area, a second area, and a first confirmation control; the at least one associated contact identifier includes a first associated contact identifier, which is located in the second area; The method further includes: Receive a third input regarding the identifier of the first associated contact; In response to the third input, the first associated contact identifier is moved to the first area; The receiving of a second input for a target associated contact identifier among the at least one associated contact identifier includes: Receive a second input to the first confirmation control; The first operation, performed in response to the second input, on the associated contact corresponding to the target associated contact identifier, includes: In response to the second input, the first operation is performed on the associated contact corresponding to the associated contact identifier in the first region.

4. The method according to claim 1, wherein, The display parameters of the at least one associated contact identifier are determined based on the activity level of the associated contact corresponding to the at least one associated contact identifier.

5. The method according to claim 1, wherein, The first operation, performed in response to the second input, on the associated contact corresponding to the target associated contact identifier, includes: In response to the second input, the first operation settings interface is displayed; Receive the fourth input to the first operation settings interface; In response to the fourth input, the first operation is performed on the associated contact corresponding to the target associated contact identifier based on the operation setting information corresponding to the first operation setting interface.

6. The method according to claim 1, wherein, The first operation is a follow operation; The method further includes: Receive a fifth input regarding the identifier of the first contact; In response to the fifth input, a social sharing information summary interface corresponding to the first contact identifier is displayed; the social sharing information summary interface includes a third area and a fourth area, the third area including the first contact identifier and the at least one associated contact identifier; Receive a sixth input for the second associated contact identifier in the third region; In response to the sixth input, the social sharing information of the associated contact corresponding to the second associated contact identifier in the social application corresponding to the second associated contact identifier is displayed in the fourth area.

7. The method according to claim 6, further comprising: Receive the seventh input to the social sharing information summary interface corresponding to the first contact identifier; In response to the seventh input, a social sharing information aggregation component corresponding to the first contact identifier is displayed on the desktop interface.

8. The method according to claim 7, wherein, The social sharing information aggregation component includes a fifth area and a sixth area, wherein the fifth area includes the first contact identifier and the at least one associated contact identifier; Receive an eighth input for the third associated contact identifier in the fifth region; In response to the eighth input, the social sharing information of the associated contact corresponding to the third associated contact identifier in the social application corresponding to the third associated contact identifier is displayed in the sixth area.

9. The method according to claim 1, wherein, The step of responding to the first input by performing a first operation on the first contact corresponding to the first contact identifier and displaying at least one associated contact identifier includes: In response to the first input, an operation window is displayed; the operation window includes at least one operation option. Receive a ninth input for a first operation option among the at least one operation options; In response to the ninth input, the first operation corresponding to the first operation option is performed on the first contact corresponding to the first contact identifier, and at least one associated contact identifier is displayed.

10. The method according to claim 9, further comprising: Receive the tenth input; In response to the tenth input, the contact management controls corresponding to each operation option are displayed; Receive the eleventh input from the first contact management control in the contact management control corresponding to each of the operation options; In response to the eleventh input, the contact management interface corresponding to the first contact management control is displayed.

11. A contact management device, comprising: The first receiving module is used to receive a first input for the first contact identifier of the first social application; A first execution module is configured to, in response to the first input, perform a first operation on the first contact corresponding to the first contact identifier, and display at least one associated contact identifier; The associated contact identifier corresponds to the same registered user as the first contact. The second receiving module is configured to receive a second input for a target associated contact identifier among the at least one associated contact identifier; The second execution module is used to perform the first operation on the associated contact corresponding to the target associated contact identifier in response to the second input.

12. An electronic device comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the contact management method as claimed in any one of claims 1 to 10.

13. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the contact management method as described in any one of claims 1 to 10.

14. A computer program product stored in a storage medium, the program product being executed by at least one processor to implement the steps of the contact management method as claimed in any one of claims 1 to 10.

15. A chip comprising a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the contact management method as described in any one of claims 1 to 10.

16. An electronic device configured to perform the steps of the contact management method as claimed in any one of claims 1 to 10.

Images