Methods for establishing associations

Abstract

This application discloses a method for establishing association relationships, belonging to the field of computer technology. The method includes: displaying a relationship establishment request interface by logging into a first application client with a first user identifier; in response to a relationship establishment confirmation operation detected in the relationship establishment request interface, sending a first establishment request to an application server, the first establishment request indicating that the first user identifier requests to establish an association relationship with a second user identifier; the application server receiving the first establishment request, receiving a second establishment request, the second establishment request indicating that the second user identifier requests to establish an association relationship with the first user identifier; in response to the first and second establishment requests, establishing an association relationship between the first user identifier and the second user identifier, returning a relationship establishment notification; and receiving and displaying the relationship establishment notification sent by the application server, thus enriching the methods for establishing association relationships.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method for establishing association relationships. Background Technology

[0002] With the continuous development of computer technology, social applications have gradually permeated people's daily lives. People can interact with others in social applications, such as establishing connections and chatting.

[0003] For example, a first user can request to establish a connection with a second user. After obtaining the second user's consent, the connection can be successfully established. However, the second user may miss the first user's request, thus preventing the connection from being established. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for establishing association relationships, which can enrich the ways to establish association relationships and improve the efficiency of establishing association relationships. The technical solution is as follows:

[0005] On the one hand, a method for establishing association relationships is provided, the method comprising:

[0006] By logging into the first application client with the first user identifier, a relationship establishment request interface is displayed, which includes the second user identifier;

[0007] In response to the relationship establishment confirmation operation detected in the relationship establishment request interface, a first establishment request is sent to the application server. The first establishment request indicates that the first user identifier requests to establish an association relationship with the second user identifier.

[0008] Receive the relationship establishment notification sent by the application server and display the relationship establishment notification;

[0009] The application server is configured to receive the first establishment request, receive the second establishment request, the second establishment request indicating that the second user identifier requests to establish an association relationship with the first user identifier, and in response to the first establishment request and the second establishment request, establish the association relationship between the first user identifier and the second user identifier, and return the relationship establishment notification.

[0010] Optionally, receiving and displaying the relationship establishment notification sent by the application server includes:

[0011] Upon receiving the relationship establishment notification, the second user identifier and the relationship establishment notification are displayed in the user identifier display interface. The user identifier display interface is used to display user identifiers that have established an association with the first user identifier.

[0012] Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the establishment time of the association, or the method of establishing the association.

[0013] On the other hand, a method for establishing association relationships is provided, the method comprising:

[0014] Receive a first establishment request, the first establishment request indicating that the first user identifier requests to establish an association relationship with the second user identifier;

[0015] Receive a second establishment request, the second establishment request indicating that the second user identifier requests to establish an association relationship with the first user identifier;

[0016] In response to the first establishment request and the second establishment request, an association relationship is established between the first user identifier and the second user identifier;

[0017] Send a relationship establishment notification to the first application client logged in with the first user identifier and the second application client logged in with the second user identifier.

[0018] Optionally, the relationship establishment notification carries at least one of the following: the first user identifier, the second user identifier, the first relationship identifier, the establishment time of the association, or the method of establishing the association.

[0019] On the other hand, an apparatus for establishing association relationships is provided, the apparatus comprising:

[0020] The display module is used to display a relationship establishment request interface through a first application client with a first user identifier, wherein the relationship establishment request interface includes a second user identifier;

[0021] The sending module is used to send a first establishment request to the application server in response to the relationship establishment confirmation operation detected in the relationship establishment request interface. The first establishment request indicates that the first user identifier requests to establish an association relationship with the second user identifier.

[0022] The display module is used to receive the relationship establishment notification sent by the application server and display the relationship establishment notification;

[0023] The application server is configured to receive the first establishment request, receive the second establishment request, the second establishment request indicating that the second user identifier requests to establish an association relationship with the first user identifier, and in response to the first establishment request and the second establishment request, establish the association relationship between the first user identifier and the second user identifier, and return the relationship establishment notification.

[0024] Optionally, the display module is further configured to display the relationship establishment notification on the current interface when the relationship establishment notification is received;

[0025] The display module is further configured to stop displaying the relationship establishment notification in response to the display duration of the relationship establishment notification reaching a first preset duration.

[0026] Optionally, the display module is further configured to, after receiving the relationship establishment notification, display the second user identifier and the relationship establishment notification in the user identifier display interface, wherein the user identifier display interface is used to display user identifiers that have established an association with the first user identifier.

[0027] Optionally, the display module is further configured to display the relationship establishment notification on the conversation interface between the first user identifier and the second user identifier after receiving the relationship establishment notification.

[0028] Optionally, the display module is configured to display the relationship establishment notification on a notification display interface after receiving the relationship establishment notification, and the notification display interface is configured to display the notification received by the first user identifier.

[0029] Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the establishment time of the association, or the method of establishing the association.

[0030] Optionally, the device further includes:

[0031] A creation module is used to create a correspondence between the second user identifier and the interaction identifier after receiving the relationship establishment notification. The interaction identifier indicates that the first user identifier and the second user identifier establish an association relationship by sending establishment requests to each other.

[0032] The display module is further configured to display the interaction identifier according to the correspondence when displaying the second user identifier.

[0033] Optionally, the display module is further configured to display the second user identifier and the interaction identifier correspondingly in the user identifier display interface, wherein the user identifier display interface is used to display user identifiers that have established an association with the first user identifier; or,

[0034] The display module is further configured to display the second user identifier and the interaction identifier in the session interface between the first user identifier and the second user identifier.

[0035] Optionally, the display module includes:

[0036] The acquisition unit is used to acquire the display parameters of the interactive identifier, wherein the display parameters indicate the display style of the interactive identifier;

[0037] The display unit is used to display the interactive identifier according to the display parameters.

[0038] Optionally, the device further includes:

[0039] The cancellation module is used to cancel the correspondence if no session message sent by the second user identifier is received within a second preset time period before the current time.

[0040] Optionally, the display module is further configured to redirect from the relationship establishment request interface to a user identifier display interface, wherein the user identifier display interface is used to display user identifiers that have established an association with the first user identifier; or,

[0041] The display module is further configured to redirect from the relationship establishment request interface to the establishment request display interface, which displays the establishment request received by the first user identifier; or,

[0042] The display module is further configured to redirect from the relationship establishment request interface to a user identifier recommendation interface, wherein the user identifier recommendation interface is configured to display at least one user identifier recommended to the first user identifier; or,

[0043] The display module is also used to jump from the relationship establishment request interface to the information display interface of the second user identifier.

[0044] Optionally, the device further includes:

[0045] The display module is further configured to scan a graphic code containing the second user identifier via a graphic code scanning interface, and then redirect from the graphic code scanning interface to the relationship establishment request interface; or...

[0046] The display module is further configured to display a user identifier recommendation interface, and in response to a confirmation operation of the second user identifier in the user identifier recommendation interface, redirect from the user identifier recommendation interface to the relationship establishment request interface; or,

[0047] The display module is further configured to display an information display interface for the second user identifier, and in response to a relationship establishment request operation detected in the information display interface, display the relationship establishment request interface.

[0048] Optionally, the device further includes:

[0049] The display module is further configured to receive the second establishment request, display the second establishment request, and the status of the second establishment request is a pending state;

[0050] The update module is also configured to update the status of the second establishment request to a processed status in response to the received relationship establishment notification.

[0051] Furthermore, an association establishment device is provided, the device comprising:

[0052] The request receiving module is used to receive a first establishment request, wherein the first establishment request indicates that the first user identifier requests to establish an association relationship with the second user identifier;

[0053] The request receiving module is further configured to receive a second establishment request, wherein the second establishment request indicates that the second user identifier request establishes an association relationship with the first user identifier;

[0054] The module is configured to establish an association between the first user identifier and the second user identifier in response to the first establishment request and the second establishment request.

[0055] The notification sending module is used to send a relationship establishment notification to the first application client logged in with the first user identifier and the second application client logged in with the second user identifier.

[0056] Optionally, the establishment module is further configured to establish the association relationship if the time interval between the receipt time of the first establishment request and the second establishment request does not exceed a third preset duration.

[0057] Optionally, the device further includes:

[0058] The request sending module is configured to send the second establishment request to the first application client if the reception time of the first establishment request is earlier than the reception time of the second establishment request, and the time interval between the reception times of the first establishment request and the second establishment request exceeds the third preset duration.

[0059] The establishment module is further configured to establish the association relationship if it receives a confirmation notification from the second application client regarding the first establishment request, or if it receives a confirmation notification from the first application client regarding the second establishment request.

[0060] Optionally, the device further includes:

[0061] The request sending module is used to send the first establishment request to the second application client;

[0062] The notification receiving module is used to establish the association relationship if it receives a confirmation notification from the second application client regarding the first establishment request.

[0063] Optionally, the relationship establishment notification carries at least one of the following: the first user identifier, the second user identifier, the first relationship identifier, the establishment time of the association, or the method of establishing the association.

[0064] In another aspect, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one instruction, the at least one instruction being loaded and executed by the processor to perform the operations performed in the association establishment method described above.

[0065] In another aspect, a computer-readable storage medium is provided, wherein at least one instruction is stored therein, the at least one instruction being loaded and executed by a processor to perform the operations performed as described in the association establishment method.

[0066] The beneficial effects of the technical solutions provided in this application include at least the following:

[0067] The association establishment method, apparatus, device, and storage medium provided in this application embodiment allow the application server to establish an association between a first user identifier and a second user identifier after receiving a first establishment request and a second establishment request. The first establishment request instructs the first user identifier to request an association with the second user identifier, and the second establishment request instructs the second user identifier to request an association with the first user identifier. In other words, the association can be established simply by the first user and the second user exchanging establishment requests, thus enriching the methods for establishing associations. Furthermore, neither the first user nor the second user needs to confirm the second establishment request, thereby reducing user operations, improving the efficiency of establishing associations, and minimizing information loss due to users passively receiving establishment requests.

[0068] Furthermore, when establishing a relationship based on the first and second establishment requests, the time interval between receiving the first and second establishment requests is also taken into account. This minimizes the impact of the first user changing their mind and not wanting to establish a relationship due to a long time interval between the first and second establishment requests. As a result, the way the relationship is established can better meet the user's ideas and needs, thus improving the user experience.

[0069] Furthermore, for user identifiers that establish a relationship by sending mutual establishment requests, an interaction identifier will be displayed when the user identifier is shown. The interaction identifier allows users to intuitively understand how the relationship was established with the user identifier. Attached Figure Description

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

[0071] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application;

[0072] Figure 2 This is a flowchart of a method for establishing an association provided in an embodiment of this application;

[0073] Figure 3 This is a flowchart of a method for establishing an association provided in an embodiment of this application;

[0074] Figure 4 This is a flowchart of a method for establishing an association provided in an embodiment of this application;

[0075] Figure 5 This is a schematic diagram of a relationship establishment request interface provided in an embodiment of this application;

[0076] Figure 6 This is a schematic diagram of a graphic code scanning interface provided in an embodiment of this application;

[0077] Figure 7 This is a schematic diagram of a user identifier recommendation interface provided in an embodiment of this application;

[0078] Figure 8 This is a schematic diagram of an information display interface provided in an embodiment of this application;

[0079] Figure 9 This is a schematic diagram of a user identifier display interface provided in an embodiment of this application;

[0080] Figure 10 This is a schematic diagram of another user identifier display interface provided in an embodiment of this application;

[0081] Figure 11 This is a schematic diagram of a request display interface provided in an embodiment of this application;

[0082] Figure 12 This is a schematic diagram of a user identifier display interface provided in an embodiment of this application;

[0083] Figure 13 This is a schematic diagram of a conversation interface between a first user identifier and a second user identifier provided in an embodiment of this application;

[0084] Figure 14 This is a schematic diagram of a notification display interface provided in an embodiment of this application;

[0085] Figure 15 This is a schematic diagram of the structure of an association establishment device provided in an embodiment of this application;

[0086] Figure 16 This is a schematic diagram of another association establishment device provided in an embodiment of this application;

[0087] Figure 17 This is a schematic diagram of the structure of an association establishment device provided in an embodiment of this application;

[0088] Figure 18 This is a schematic diagram of another association establishment device provided in an embodiment of this application;

[0089] Figure 19 This is a structural block diagram of a terminal provided in an embodiment of this application;

[0090] Figure 20 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0091] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0092] It is understood that the terms "first," "second," etc., used in this application may be used to describe various concepts herein, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of this application, a first user identifier may be referred to as a second user identifier, and similarly, a second user identifier may be referred to as a first user identifier.

[0093] As used in this application, the terms "at least one", "multiple", "each", and "any" are used in the following ways: at least one includes one, two, or more; multiple includes two or more; each refers to each of the corresponding multiple; and any refers to any one of the multiple. For example, multiple user identifiers include three user identifiers, each refers to each of the three user identifiers, and any refers to any one of the three user identifiers, which can be the first, the second, or the third.

[0094] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application. See also... Figure 1The implementation environment includes: a first terminal 101, a second terminal 102, and an application server 103.

[0095] The first terminal 101 and the second terminal 102 can be devices such as mobile phones, computers, and tablets. The application server 103 can be a single server, a server cluster consisting of several servers, or a cloud computing service center.

[0096] The first terminal 101 and the second terminal 102 can install the same application client. They log in to the application client based on the user identifier and establish a communication connection with the application server 103 through the application client, thereby interacting with the application server 103.

[0097] In one possible implementation, the first terminal 101 sends a first establishment request to the application server by logging into a first application client with a first user identifier. The first establishment request indicates that the first user identifier requests to establish an association with a second user identifier. The second terminal 102 sends a second establishment request to the application server by logging into a second application client with a second user identifier. The second establishment request indicates that the second user identifier requests to establish an association with the first user identifier. After receiving the first establishment request and the second establishment request, the application server 103 establishes the association between the first user identifier and the second user identifier and returns a relationship establishment notification to the first terminal 101 and the second terminal 102.

[0098] Figure 2 This application provides a method for establishing association relationships, and the execution subject of this application embodiment is... Figure 1 The first terminal 101 shown is referred to in the following text. Figure 2 The method includes:

[0099] 201. The first terminal displays a relationship establishment request interface by logging into the first application client with the first user identifier. This relationship establishment request interface includes the second user identifier.

[0100] The terminal has an application client installed, which can be logged into based on the user's identifier. This application client can be a client that enables interaction between different users, such as a social networking client, an instant messaging client, or a message-sharing client with chat functionality.

[0101] A user identifier is a unique identifier registered by a user in the application client. This identifier is used to uniquely identify the user and represents that user's identity. It can be a user account, user nickname, etc. Any two terminals with the same application client installed can interact by logging in based on their respective user identifiers.

[0102] This application embodiment uses a first terminal and a second terminal as examples. For ease of distinction, the application client installed on the first terminal is referred to as the first application client, and the application client installed on the second terminal is referred to as the second application client. Furthermore, the user of the first terminal is referred to as the first user, and the user of the second terminal is referred to as the second user.

[0103] The relationship establishment request interface is used to request the establishment of an association with another user identifier. If the relationship establishment request interface displayed by logging into the first application client of the first user identifier includes the second user identifier, then the relationship establishment request interface is used to request the establishment of an association with the second user identifier.

[0104] 202. In response to the relationship establishment confirmation operation detected in the relationship establishment request interface, the first terminal sends a first establishment request to the application server. The first establishment request indicates that the first user identifier requests to establish an association relationship with the second user identifier.

[0105] The application server is used to receive the first establishment request, receive the second establishment request, the second establishment request instructing the second user identifier to establish an association with the first user identifier, and in response to the first establishment request and the second establishment request, establish the association between the first user identifier and the second user identifier, and return a relationship establishment notification.

[0106] The relationship establishment notification is used to indicate that the association between the first user identifier and the second user identifier has been established.

[0107] 203. The first terminal receives the relationship establishment notification sent by the application server and displays the relationship establishment notification.

[0108] The association establishment method provided in this application embodiment establishes an association between a first user identifier and a second user identifier after the application server receives a first establishment request and a second establishment request. The first establishment request instructs the first user identifier to request an association with the second user identifier, and the second establishment request instructs the second user identifier to request an association with the first user identifier. In other words, the association can be established simply by the first user and the second user exchanging establishment requests, thus enriching the methods for establishing associations. Furthermore, neither the first user nor the second user needs to confirm the second establishment request, thereby reducing user operations, improving the efficiency of establishing associations, and minimizing information loss due to users passively receiving establishment requests.

[0109] Optionally, the recipient of the relationship establishment notification sent by the application server displays the relationship establishment notification, including:

[0110] When the relationship establishment notification is received, it will be displayed on the current screen.

[0111] When the display duration of the relationship establishment notification reaches a first preset duration, the display of the relationship establishment notification stops.

[0112] Optionally, the recipient of the relationship establishment notification sent by the application server displays the relationship establishment notification, including:

[0113] Upon receiving the relationship establishment notification, the second user ID and the relationship establishment notification are displayed in the user ID display interface. The user ID display interface is used to display user IDs that have established a relationship with the first user ID.

[0114] Optionally, the recipient of the relationship establishment notification sent by the application server displays the relationship establishment notification, including:

[0115] Upon receiving the relationship establishment notification, the relationship establishment notification is displayed on the session interface between the first user ID and the second user ID.

[0116] Optionally, the recipient of the relationship establishment notification sent by the application server displays the relationship establishment notification, including:

[0117] Upon receiving the relationship establishment notification, the relationship establishment notification is displayed on the notification display interface, which is used to display the notification received by the first user identifier.

[0118] Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the time of establishment of the association, or the method of establishing the association.

[0119] Optionally, the method further includes:

[0120] Upon receiving the relationship establishment notification, a correspondence is created between the second user identifier and the interaction identifier. The interaction identifier instructs the first user identifier and the second user identifier to establish an association by sending establishment requests to each other.

[0121] When the second user identifier is displayed, the interaction identifier is displayed according to the correspondence.

[0122] Optionally, when displaying the second user identifier, displaying the interaction identifier according to the correspondence includes:

[0123] The user identifier display interface displays the second user identifier and the interaction identifier accordingly. This user identifier display interface is used to display user identifiers that have established a relationship with the first user identifier; or...

[0124] The second user ID and the interaction ID are displayed in the session interface between the first user ID and the second user ID.

[0125] Optionally, displaying the interaction identifier based on the correspondence includes:

[0126] Obtain the display parameters of the interactive icon, which indicate the display style of the interactive icon;

[0127] The interactive icon is displayed based on the display parameters.

[0128] Optionally, after creating the correspondence between the second user identifier and the interaction identifier, the method further includes:

[0129] If no session message from the second user identifier is received within the second preset time period prior to the current time, the correspondence is terminated.

[0130] Optionally, after sending a first establishment request to the application server in response to the confirmation operation of the second user identifier, the method further includes:

[0131] The user is redirected from the relationship establishment request interface to a user identifier display interface, which shows user identifiers that have been associated with the first user identifier; or...

[0132] The user is redirected from the relationship establishment request interface to the establishment request display interface, which displays the establishment request received by the first user identifier; or,

[0133] The user is redirected from the relationship establishment request interface to a user ID recommendation interface, which displays at least one user ID recommended to the first user ID; or,

[0134] The user will be redirected from the relationship establishment request interface to the information display interface of the second user identifier.

[0135] Optionally, before displaying the relationship establishment request interface on the first application client that logs in with the first user identifier, the method further includes:

[0136] Scan the graphic code containing the second user identifier through the graphic code scanning interface, and then be redirected to the relationship establishment request interface; or,

[0137] Display a user ID recommendation interface, and in response to a confirmation operation of the second user ID in the user ID recommendation interface, redirect from the user ID recommendation interface to the relationship establishment request interface; or,

[0138] The information display interface of the second user identifier is displayed, and in response to the relationship establishment request operation detected in the information display interface, the relationship establishment request interface is displayed.

[0139] Optionally, the method further includes:

[0140] Receive the second establishment request, display the second establishment request, and set the status of the second establishment request to pending.

[0141] In response to the received relationship establishment notification, the status of the second establishment request is updated to processed.

[0142] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0143] It should be noted that the above embodiments are also applicable to Figure 1 The second terminal 102 shown.

[0144] Figure 3 This is a flowchart of a method for establishing an association provided in an embodiment of this application. The execution subject of this embodiment is... Figure 1 The application server 103 shown in this embodiment illustrates the process of establishing association relationships. See [link to relevant documentation]. Figure 3 The method includes:

[0145] 301. Receive the first establishment request.

[0146] The first establishment request is sent by the first application client that logs in with the first user identifier. The first establishment request includes the first user identifier and the second user identifier, indicating that the first user identifier requests to establish an association with the second user identifier.

[0147] 302. Receive the second establishment request.

[0148] The second establishment request is sent by the second application client that logs in with the second user identifier. The second establishment request includes the first user identifier and the second user identifier, indicating that the second user identifier requests to establish an association with the first user identifier.

[0149] 303. In response to the first establishment request and the second establishment request, establish the association between the first user identifier and the second user identifier.

[0150] Among them, the association relationship is the relationship between any two user identifiers, which can be any kind of relationship provided by the application client, such as friend relationship, follow relationship, interest relationship, etc.

[0151] 304. Send a relationship establishment notification to the first application client logged in with the first user ID and the second application client logged in with the second user ID.

[0152] After establishing the association between the first user identifier and the second user identifier, the server will notify the first user identifier and the second user identifier that the association has been established.

[0153] The association establishment method provided in this application embodiment establishes an association between a first user identifier and a second user identifier after the application server receives a first establishment request and a second establishment request. The first establishment request instructs the first user identifier to request an association with the second user identifier, and the second establishment request instructs the second user identifier to request an association with the first user identifier. In other words, the association can be established simply by the first user and the second user exchanging establishment requests, thus enriching the methods for establishing associations. Furthermore, neither the first user nor the second user needs to confirm the second establishment request, thereby reducing user operations, improving the efficiency of establishing associations, and minimizing information loss due to users passively receiving establishment requests.

[0154] Optionally, in response to the first establishment request and the second establishment request, establishing the association between the first user identifier and the second user identifier includes:

[0155] If the time interval between receiving the first establishment request and the second establishment request does not exceed the third preset duration, the association relationship is established.

[0156] Optionally, the method further includes:

[0157] If the time of receiving the first establishment request is before the time of receiving the second establishment request, and the time interval between the time of receiving the first establishment request and the second establishment request exceeds the third preset duration, the second establishment request is sent to the first application client.

[0158] If the second application client receives a confirmation notification for the first establishment request, or if the first application client receives a confirmation notification for the second establishment request, then the association is established.

[0159] Optionally, after receiving the first establishment request, the method further includes:

[0160] The first establishment request is sent to the second application client;

[0161] If the second application client receives a confirmation notification regarding the first establishment request, then the association is established.

[0162] Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the first relationship identifier, the establishment time of the association, or the method of establishing the association.

[0163] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0164] Figure 4 This is a flowchart illustrating a method for establishing an association relationship provided in an embodiment of this application. The interactive subject in this embodiment is... Figure 1 The first terminal 101, the second terminal 102, and the application server 103 shown in this embodiment illustrate the process of establishing the association relationship. See [link to relevant documentation]. Figure 4 The method includes:

[0165] 401. The first terminal displays a relationship establishment request interface by logging into the first application client with the first user identifier. The relationship establishment request interface includes the second user identifier.

[0166] The relationship establishment request interface is used to request the establishment of an association with other user identifiers. This interface includes user identifiers, which can be any user identifier other than the first user identifier. The relationship establishment request interface is used to request the establishment of an association with the user identifiers included in the interface. For example, in this embodiment, if the relationship establishment request interface includes a second user identifier, then the interface is used to request the establishment of an association with the second user identifier.

[0167] In addition to the second user identifier, the relationship establishment request interface may also include other options or buttons. Optionally, the relationship establishment request interface may also include a confirmation button, which the user can use to confirm whether to request to establish an association with the second user identifier.

[0168] For example, such as Figure 5 As shown, the relationship establishment request interface 500 includes "Xiaoming" 501 and a send button 502. "Xiaoming" is a second user identifier. Users can confirm the identity of the second user identifier based on the second user identifier. After confirming the identity of the second user identifier, if they want to establish an association with "Xiaoming", they can trigger the send button 502.

[0169] Optionally, the relationship establishment request interface may also include a relationship type option, which allows users to determine which type of association to establish with other users.

[0170] For example, such as Figure 5As shown, the relationship establishment request interface 500 also includes a relationship type option 503. After triggering the relationship type option 503, at least one type of association can be displayed. The user can select an association from these at least one type of association, such as... Figure 5 As shown, the user selected the "friend" relationship, indicating that the user wants to establish a friend relationship with "Xiaoming".

[0171] Optionally, the relationship establishment request interface may also include a verification information input box 504, in which the user can enter verification information so that when the second user receives the establishment request, he / she can determine whether to agree to the establishment request based on the verification information.

[0172] In addition, other interfaces can be displayed before the relationship establishment request interface is displayed, and the relationship establishment request interface can be accessed through these other interfaces. This application embodiment describes the method of displaying the relationship establishment request interface:

[0173] 1. Scan the graphic code containing the second user identifier through the graphic code scanning interface, and jump from the graphic code scanning interface to the relationship establishment request interface.

[0174] The graphic code scanning interface is used for scanning graphic codes, and optionally, as follows: Figure 6 As shown, the graphic code scanning interface 600 may include a scanning frame 601, which is used to scan the captured graphic code to obtain the user identifier included in the graphic code, and jump to the relationship establishment request interface according to the user identifier.

[0175] Optionally, the graphic code scanning interface can be displayed through the "scan" function provided by the first terminal or through the "scan" function provided by the first application client.

[0176] 2. Display the user ID recommendation interface, and in response to the confirmation operation of the second user ID in the user ID recommendation interface, jump from the user ID recommendation interface to the relationship establishment request interface.

[0177] The user identifier recommendation interface is an interface that recommends other users to end users. The first application client or application server can obtain at least one user identifier and display the at least one user identifier through the user identifier recommendation interface. Users can select at least one user identifier from the at least one user identifier and thus establish an association relationship with the at least one user identifier.

[0178] Optionally, the application server obtaining at least one user identifier may include: the application server may obtain the location of the first terminal and the location of the terminal where other user identifiers are located, and determine at least one user identifier whose distance from the first terminal does not exceed a preset distance threshold based on the location of the first terminal and the location of the terminal where other user identifiers are located.

[0179] For example, the first user can search for "people nearby" in the first application client and obtain at least one user identifier from the application server, such as... Figure 7 As shown, at least one user identifier is displayed through the user identifier recommendation interface 700. Clicking on any of the at least one user identifier will redirect to the relationship establishment request interface, which includes the clicked user identifier.

[0180] Additionally, the application server can recommend nearby people or people the first user identifier may know. Optionally, obtaining at least one user identifier may include: obtaining a first associated user identifier that is associated with the first user identifier, obtaining a second associated user identifier that is associated with the first associated user identifier, and recommending them to the first user identifier. Alternatively, the application server can obtain multiple first associated user identifiers that are associated with the first user identifier, obtain second associated user identifiers that are associated with the multiple first associated user identifiers, and recommend them to the first user identifier. For example, if the association is a friend relationship, the application server can recommend mutual friends of multiple friends of the first user identifier to the first user identifier.

[0181] 3. Display the information display interface of the second user identifier, and in response to the relationship establishment request operation detected in the information display interface, display the relationship establishment request interface.

[0182] The second user identifier information display interface is used to display the information of the second user identifier, such as... Figure 8 As shown, the information display interface 800 includes: the second user's avatar, interests, gender, age, etc. Users can use the information display interface to learn about the second user and determine whether to establish an association with that second user.

[0183] Optionally, the information display interface 800 may include an add button 801, and in response to a triggering operation of the add button, a relationship establishment request interface is displayed.

[0184] It should be noted that the above three methods of entering the relationship establishment request interface are merely illustrative examples of entering the relationship establishment request interface. Other methods can also be used to enter the relationship establishment request interface, and this application embodiment does not limit this.

[0185] 402. The first application client responds to the relationship establishment confirmation operation detected in the relationship establishment request interface by sending the first establishment request to the application server.

[0186] The relationship establishment confirmation operation can be a user-triggered operation to agree to establish a relationship. Optionally, the relationship establishment request interface 500 may include a send button 502. The relationship establishment confirmation operation is a triggering operation of the send button 502. The triggering operation can also be any operation such as a click operation, a double click operation, or a swipe operation. This application embodiment does not limit the triggering operation.

[0187] The first establishment request may include a first user identifier and a second user identifier, indicating that the first user identifier requests to establish an association with the second user identifier. Optionally, the first establishment request may also include verification information entered in the first application client. The second user can determine whether to agree to establish an association with the first user based on the verification information in the first establishment request.

[0188] It should be noted that step 402 provides an illustrative explanation of how to access the relationship establishment request interface. After accessing the interface, you can return to the previous screen using the back operation, or you can confirm the relationship establishment within the interface. After sending the first establishment request, you will proceed to the next screen. The following provides an illustrative example of the process of "sending the first establishment request to the application server and then proceeding to the next screen":

[0189] 1. The user will be redirected from the relationship establishment request interface to the user ID display interface.

[0190] This user identifier display interface is used to display user identifiers that have been associated with the first user identifier. For example, such as... Figure 9 As shown, the user identifier display interface 900 is used to display the friend list of the first user identifier.

[0191] Optionally, when displaying user identifiers that have been associated with the first user identifier, the user identifier display interface may also display the latest session messages for each user identifier, such as... Figure 10 In the user identifier display interface 1000 shown, the user identifier and the latest session message between the user identifier and the first user identifier can be displayed in the same area.

[0192] It should be noted that if the association between the first user identifier and the second user identifier has been successfully established after the first establishment request is sent, the second user identifier will be displayed in the user identifier display interface. If the association between the first user identifier and the second user identifier has not yet been established, the second user identifier will not be included in the user identifier display interface.

[0193] 2. The page that requests the establishment of the relationship will redirect to the page that displays the establishment request.

[0194] After receiving a request, the first application client can display the received request in the request display interface, identifying the first user. The first user can process the displayed request, such as agreeing to, rejecting, or blocking it. However, the first user may not open the request display interface, thus preventing them from seeing and processing the received request.

[0195] In this embodiment, after sending the first establishment request to the application server, the user can jump from the relationship establishment request interface to the establishment request display interface, thereby displaying the establishment request received by the first user to the first user. This increases the probability of the user processing the establishment request and minimizes the impact of the user missing the establishment request.

[0196] Additionally, when displaying the establishment request received by the first user identifier on the establishment request display interface, the status of the establishment request can also be displayed, such as... Figure 11 As shown, in the request creation display interface 1100, request creation 1101 is "Xiaomin requests to add you as a friend," and a corresponding "Add" option 1102 is displayed. This "Add" option 1102 indicates that request creation 1101 is in a pending state. If the first user triggers the "Add" option 1102, request creation 1101 will be updated from a pending state to a processed state, and a friend relationship will be established between the first user and "Xiaomin." In the request creation display interface 1100, request creation 1103 is "Xiaolan requests to add you as a friend," and the word "Added" is displayed, indicating that request creation 1103 is in a processed state.

[0197] 3. The user will be redirected from the relationship establishment request page to the user identification recommendation page.

[0198] The user identifier recommendation interface is used to display at least one user identifier recommended to the first user identifier. After sending the first establishment request, the user can jump from the relationship establishment request interface to the user identifier recommendation interface, so that the user can select any user identifier from the user identifier recommendation interface and send an establishment request to establish an association relationship with that user identifier.

[0199] Optionally, the first application client displays a user identifier recommendation interface, which includes a second user identifier. In response to a confirmation operation of the second user identifier in the user identifier recommendation interface, the client is redirected from the user identifier recommendation interface to the relationship establishment request interface. In response to a relationship establishment confirmation operation detected in the relationship establishment request interface, the client sends a first establishment request to the application server. Then, the client is redirected from the relationship establishment request interface to the user identifier recommendation interface. In response to a confirmation operation of a third user identifier in the user identifier recommendation interface, the client is redirected from the user identifier recommendation interface to the relationship establishment request interface. In response to a relationship establishment confirmation operation detected in the relationship establishment request interface, the client sends a third establishment request to the application server. The third establishment request indicates that the first user identifier requests to establish an association relationship with the third user identifier.

[0200] 4. The user is redirected from the relationship establishment request interface to the information display interface of the second user identifier.

[0201] Optionally, in response to the relationship establishment request operation detected in the information display interface, the first application client jumps from the information display interface to the relationship establishment request interface, and then in response to the relationship establishment confirmation operation detected in the relationship establishment request interface, sends a first establishment request to the application server and then jumps back to the information display interface of the second user identifier.

[0202] It should be noted that the above four ways of jumping from the relationship establishment request interface to other interfaces are only illustrative examples of the display method of the first application client after sending the first establishment request. This application embodiment does not limit the interface displayed by the first application client when sending the first establishment request. Optionally, the first application client may also display the relationship establishment request interface.

[0203] 403. The application server receives the first establishment request and sends the first establishment request to the second application client.

[0204] It should be noted that the embodiments of this application are only illustrated by the example that the first establishment request is received earlier than the second establishment request. Therefore, after the application server receives the first establishment request, it can send the first establishment request to the second application client. The first establishment request includes a first user identifier and a second user identifier. The application server can send the first establishment request to the second application client based on the second user identifier. The second application client is the client that logged in with the second user identifier.

[0205] Optionally, after receiving the first establishment request, the application server may record the time of receiving the first establishment request; or, the first establishment request may carry the time when the first application client sent the first establishment request, and the application server may obtain the time carried in the first establishment request after receiving it.

[0206] Optionally, the application server may store the first establishment request after receiving it.

[0207] 404. The second terminal receives the first establishment request through the second application client that logs in with the second user identifier, displays the first establishment request, and the status of the first establishment request is pending.

[0208] Since the first establishment request is a request to establish an association between the first user identifier and the second user identifier, the first establishment request needs to be processed by the second user identifier. If the second user identifier has not yet processed it, the status of the first establishment request is pending; if the second user identifier has already processed it, the status of the first establishment request is processed.

[0209] Additionally, after receiving the first establishment request, the second application client needs to display the first establishment request so that the second user can process it. Optionally, the second application client receiving and displaying the first establishment request may include: after receiving the first establishment request, displaying the first establishment request on a notification display interface, which is used to display a notification identified by the second user.

[0210] Optionally, the second application client receiving and displaying the first establishment request may include: after receiving the first establishment request, displaying the first establishment request in an establishment request display interface, which is used to display the establishment request received by the second user identifier.

[0211] It should be noted that the notification display interface and the request creation display interface may be displayed after the interface entry is triggered, or they may be displayed automatically after a new notification or request is received. This application embodiment does not limit this.

[0212] Optionally, the second application client receiving and displaying the first establishment request may include: after receiving the first establishment request, displaying the first establishment request on the current interface; and stopping the display of the first establishment request when the display duration reaches a first preset duration. This avoids information loss due to the user not having opened the notification display interface or the establishment request display interface. The first preset duration can be any duration, such as 1 second, 3 seconds, 5 seconds, etc.

[0213] It should be noted that if the second user confirms the first establishment request, the application server can directly establish the association between the first user identifier and the second user identifier. If the second user does not process the first establishment request, steps 405 to 410 can be executed.

[0214] 405. The second application client displays a relationship establishment request interface, which includes the first user identifier.

[0215] Step 405 is similar to step 401, and can be referred to step 401. It will not be described in detail here.

[0216] 406. In response to the relationship establishment confirmation operation detected in the relationship establishment request interface, the second terminal sends a second establishment request to the application server.

[0217] Step 406 is similar to step 402, and can be referred to step 402. It will not be described in detail here.

[0218] 407. The application server receives the second establishment request and, in response to the first establishment request and the second establishment request, establishes the association between the first user identifier and the second user identifier.

[0219] If the application server receives a second establishment request after receiving the first establishment request, it means that the first user wants to establish an association with the second user, and the second user also wants to establish an association with the first user. In this case, in order to reduce the operations of the first user and the second user, the first user does not need to confirm the second establishment request, nor does the second user need to confirm the first establishment request. The application server can directly establish the association between the first user's identifier and the second user's identifier.

[0220] Optionally, the application server establishing the association between the first user identifier and the second user identifier may include: the application server establishing a relationship chain pair between the first user identifier and the second user identifier. This relationship chain pair indicates the association between the first user identifier and the second user identifier; for example, if the relationship chain pair is a friend relationship chain pair, then the relationship chain pair indicates that the first user identifier and the second user identifier are friends.

[0221] Optionally, after the application server establishes the association between the first user identifier and the second user identifier, it can mark the association to indicate that the association was established by sending establishment requests to each other based on the first user identifier and the second user identifier.

[0222] Optionally, the application server can also determine whether to directly establish the association based on the reception time of the first establishment request and the second establishment request. In one possible implementation, establishing the association between the first user identifier and the second user identifier in response to the first establishment request and the second establishment request may include: establishing the association if the time interval between the reception times of the first establishment request and the second establishment request does not exceed a third preset duration. The third preset duration can be any duration, such as one month, six months, one year, two years, etc.

[0223] Furthermore, if the time interval between receiving the first establishment request and the second establishment request exceeds a third preset duration, the application server cannot directly establish a connection and can send the second establishment request to the first application client to obtain the user's consent. In one possible implementation, if the time of receiving the first establishment request is before the time of receiving the second establishment request, and the time interval between receiving the first and second establishment requests exceeds the third preset duration, the second establishment request can be sent to the first application client; subsequently, if a confirmation notification of the first establishment request is received from the second application client, or if a confirmation notification of the second establishment request is received from the first application client, the connection is established.

[0224] For example, if the time of receiving the first establishment request differs from the time of receiving the second establishment request by 3 days, the user is unlikely to change their mind. In this case, the association between the first user ID and the second user ID can be established directly. If the time of receiving the first establishment request differs from the time of receiving the second establishment request by 2 years, the first user's mind may change, and they may not want to establish an association with the second user. In this case, the second establishment request needs to be sent to the first application client to obtain the first user's consent.

[0225] 408. The application server sends a relationship establishment notification to the first application client and the second application client.

[0226] After establishing the association, the application server can send a relationship establishment notification to both the first and second application clients, informing them that the association has been successfully established. Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the time the association was established, or the method by which the association was established.

[0227] Optionally, after the application server sends a relationship establishment notification to the first application client and the second application client, it may also send other information. Optionally, the application server sends an interaction identifier to the first application client and the second application client, which indicates that the first user identifier and the second user identifier establish an association relationship by sending establishment requests to each other.

[0228] After the association is established, the first user and the second user can send conversation messages to each other. However, after the association is established, the first user and the second user may not know what to say first, resulting in a lack of timely interaction. Optionally, after the application server sends a relationship establishment notification to the first application client and the second application client, it can also send a greeting message to both application clients so that the first user and the second user can send conversation messages as soon as possible. The greeting message received by the first application client is different from the greeting message received by the second application client. For example, the greeting message received by the first application client is "Hello, I am Xiaoming," where Xiaoming is the second user's identifier, while the greeting message received by the second application client is "Hello, I am Xiaozi," where Xiaozi is the first user's identifier.

[0229] 409. The first application client receives the relationship establishment notification sent by the application server and displays the relationship establishment notification.

[0230] Upon receiving the relationship establishment notification, the first application client can display the notification to inform the user that the association has been established.

[0231] Optionally, the first application client can display the relationship establishment notification through a certain interface. In one possible implementation, receiving and displaying the relationship establishment notification sent by the application server includes: after receiving the relationship establishment notification, displaying the second user identifier and the relationship establishment notification in a user identifier display interface, wherein the user identifier display interface is used to display user identifiers that have established a relationship with the first user identifier.

[0232] For example, such as Figure 12 As shown, the user identifier display interface 1200 displays "Xiaoming" 1201 and "You have sent friend requests to each other and become friends with Xiaoming" 1202. Among them, "Xiaoming" is the second user identifier, and "You have sent friend requests to each other and become friends with Xiaoming" is the relationship establishment notification.

[0233] In one possible implementation, receiving and displaying the relationship establishment notification sent by the application server may include: after receiving the relationship establishment notification, displaying the relationship establishment notification on the session interface between the first user ID and the second user ID.

[0234] Optionally, since the relationship establishment notification includes a second user identifier, after receiving the relationship establishment notification, the first application client can generate a greeting message based on the second user identifier and greeting message template carried in the relationship establishment notification, and display the greeting message in the session interface.

[0235] For example, such as Figure 13 As shown, in the conversation interface 1300 between the first user ID and the second user ID, “Xiaoming” 1301 and “You have sent friend requests to each other and become friends with Xiaoming” 1302 are displayed. “Xiaoming” is the second user ID, and “You have sent friend requests to each other and become friends with Xiaoming” is a relationship establishment notification.

[0236] In one possible implementation, receiving and displaying the relationship establishment notification sent by the application server includes: after receiving the relationship establishment notification, displaying the relationship establishment notification on the notification display interface.

[0237] The notification display interface is used to display notifications received by the first user identifier. Optionally, the notification display interface can also be used to display notifications received by other clients installed on the first terminal; this embodiment of the application does not limit this. Figure 14 As shown, the notification display interface 1400 displays "You have sent friend requests to each other and become friends with Xiaoming" 1401. The notification display interface can be displayed through a pull-down operation or by triggering the interface entry.

[0238] Optionally, when the first application client displays the relationship establishment notification, it can also display it directly on the current interface. In one possible implementation, receiving the relationship establishment notification sent by the application server and displaying the relationship establishment notification includes: displaying the relationship establishment notification on the current interface when the relationship establishment notification is received; and stopping the display of the relationship establishment notification when the display duration of the relationship establishment notification reaches a first preset duration. The current interface can be any interface displayed on the terminal.

[0239] Furthermore, the first user identifier and the second user identifier establish a relationship by sending establishment requests to each other. Optionally, when the first application client displays the second user identifier, it can display a corresponding interaction identifier, which instructs the first user identifier and the second user identifier to establish a relationship by sending establishment requests to each other. In one possible implementation, the method further includes: after receiving the relationship establishment notification, creating a correspondence between the second user identifier and the interaction identifier, whereby the interaction identifier instructs the first user identifier and the second user identifier to establish a relationship by sending establishment requests to each other; and when displaying the second user identifier, displaying the interaction identifier according to the correspondence.

[0240] The interaction identifier can be sent from the application server to the first application client or obtained by the first application client. In one possible implementation, after receiving the relationship establishment notification, the first application client can create a correspondence between the second user identifier and the interaction identifier by: determining the method of establishing the association after receiving the relationship establishment notification, obtaining the interaction identifier according to the method of establishing the association, and creating a correspondence between the second user identifier and the interaction identifier; or, the relationship establishment notification includes the interaction identifier, and the first application client obtains the interaction identifier from the relationship establishment notification and creates a correspondence between the second user identifier and the interaction identifier.

[0241] Optionally, if the relationship establishment notification includes an interaction identifier, the application server can determine the interaction identifier corresponding to the identifier based on the identifier of the association relationship.

[0242] like Figure 12 As shown, the user identifier display interface 1200 displays "Xiaoming" 1201 and "△" 1203, where "△" is an interaction identifier. The user identifier display interface 1200 is used to display user identifiers that have established a relationship with the first user identifier; or, in the conversation interface 1300 between the first user identifier and the second user identifier, "Xiaoming" 1301 and "△" 1303 are displayed. The interaction identifier can be of any shape, and this embodiment does not limit the shape of the interaction identifier.

[0243] Optionally, the relationship establishment notification may include the establishment time of the association. In one possible implementation, the first application client receives the relationship establishment notification sent by the application server and displays the relationship establishment notification. This may include: obtaining the association establishment time carried in the relationship establishment notification and displaying the establishment time at the top of the session interface; obtaining the first user identifier, the second user identifier, the method of establishing the association, and the notification message template carried in the relationship establishment notification; generating a notification message; and displaying the notification message below the greeting message.

[0244] Additionally, when the first client displays the interactive icon, it can obtain the corresponding display parameters and display the interactive icon according to the display parameters. Optionally, displaying the interactive icon according to the correspondence may include: obtaining the display parameters of the interactive icon, the display parameters indicating the display style of the interactive icon; and displaying the interactive icon according to the display parameters.

[0245] Optionally, the first client may continuously display the interaction identifier corresponding to the second user identifier, or it may cancel the display of the interaction identifier after certain conditions are met. Optionally, after creating the correspondence between the second user identifier and the interaction identifier, the method further includes: if no session message sent by the second user identifier is received within a second preset time period before the current time, then the correspondence is terminated.

[0246] For example, the time when the association is established can be used as the start time. If no session message is received from the second user identifier within a second preset time period starting from the start time, the interaction identifier will be removed from display. If a session message is received from the second user identifier, the interaction identifier will continue to be displayed. Alternatively, if the time interval since the last session message sent to the second user identifier, or the time interval since the last session message received from the second user identifier, reaches the second preset time period, the interaction identifier will be removed from display.

[0247] 410. The second application client receives the relationship establishment notification sent by the application server and displays the relationship establishment notification.

[0248] Step 410 is similar to step 409, and can be referred to step 409. It will not be described in detail here.

[0249] It should be noted that after the second client receives the first relationship establishment request, it displays the first relationship establishment request in the relationship establishment request notification interface, and the status of the first relationship establishment request is pending. After receiving the relationship establishment notification sent by the application server, the second client can respond to the received relationship establishment notification by updating the status of the second relationship establishment request to the processed status.

[0250] The association establishment method provided in this application embodiment establishes an association between a first user identifier and a second user identifier after the application server receives a first establishment request and a second establishment request. The first establishment request instructs the first user identifier to request an association with the second user identifier, and the second establishment request instructs the second user identifier to request an association with the first user identifier. In other words, the association can be established simply by the first user and the second user sending establishment requests to each other, enriching the methods for establishing associations. Furthermore, it eliminates the need for the first user to confirm the second establishment request, and the second user to confirm the first establishment request, thereby reducing the number of operations required from both users, improving the efficiency of establishing associations, and reducing information loss due to users passively receiving establishment requests.

[0251] Furthermore, when establishing a relationship based on the first and second establishment requests, the time interval between receiving the first and second establishment requests is also taken into account. This minimizes the impact of the first user changing their mind and not wanting to establish a relationship due to a long time interval between the first and second establishment requests. As a result, the way the relationship is established can better meet the user's ideas and needs, thus improving the user experience.

[0252] Furthermore, for user identifiers that establish a relationship by sending mutual establishment requests, an interaction identifier will be displayed when the user identifier is shown. The interaction identifier allows users to intuitively understand how the relationship was established with the user identifier.

[0253] Figure 15 This is a schematic diagram of the structure of an association establishment device provided in an embodiment of this application. See also... Figure 15 The device includes a display module 1501 and a transmission module 1502.

[0254] Display module 1501 is used to display a relationship establishment request interface through a first application client with a first user ID, the relationship establishment request interface including a second user ID;

[0255] Sending module 1502 is used to send a first establishment request to the application server in response to the relationship establishment confirmation operation detected in the relationship establishment request interface. The first establishment request indicates that the first user identifier requests to establish an association relationship with the second user identifier.

[0256] The display module 1501 is used to receive the relationship establishment notification sent by the application server and display the relationship establishment notification.

[0257] The application server is configured to receive the first establishment request, receive the second establishment request, the second establishment request instructing the second user identifier to establish an association with the first user identifier, and in response to the first establishment request and the second establishment request, establish the association between the first user identifier and the second user identifier, and return a notification of the establishment of the relationship.

[0258] like Figure 16 As shown, optionally, the display module 1501 is also used to display the relationship establishment notification on the current interface when the relationship establishment notification is received;

[0259] The display module 1501 is also configured to stop displaying the relationship establishment notification in response to the display duration of the relationship establishment notification reaching a first preset duration.

[0260] Optionally, the display module 1501 is further configured to, after receiving the relationship establishment notification, display the second user identifier and the relationship establishment notification in the user identifier display interface, which is used to display user identifiers that have established an association with the first user identifier.

[0261] Optionally, the display module 1501 is further configured to display the relationship establishment notification on the session interface between the first user ID and the second user ID after receiving the relationship establishment notification.

[0262] Optionally, the display module 1501 is used to display the relationship establishment notification on a notification display interface after receiving the relationship establishment notification. The notification display interface is used to display the notification received by the first user identifier.

[0263] Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the time of establishment of the association, or the method of establishing the association.

[0264] Optionally, the device further includes:

[0265] The creation module 1503 is used to create a correspondence between the second user identifier and the interaction identifier after receiving the relationship establishment notification. The interaction identifier indicates that the first user identifier and the second user identifier establish an association relationship by sending establishment requests to each other.

[0266] The display module 1501 is also used to display the interaction identifier according to the correspondence when displaying the second user identifier.

[0267] Optionally, the display module 1501 is further configured to display the second user identifier and the interaction identifier in the user identifier display interface, wherein the user identifier display interface is used to display user identifiers that have been associated with the first user identifier; or,

[0268] The display module 1501 is also used to display the second user ID and the interaction ID in the session interface between the first user ID and the second user ID.

[0269] Optionally, the display module 1501 includes:

[0270] The acquisition unit 1511 is used to acquire the display parameters of the interactive icon, which indicate the display style of the interactive icon;

[0271] Display unit 1521 is used to display the interactive identifier according to the display parameters.

[0272] Optionally, the device further includes:

[0273] The cancellation module 1504 is used to cancel the correspondence if no session message sent by the second user identifier is received within a second preset time period before the current time.

[0274] Optionally, the display module 1501 is further configured to jump from the relationship establishment request interface to a user identifier display interface, which displays user identifiers that have been associated with the first user identifier; or,

[0275] The display module 1501 is also used to jump from the relationship establishment request interface to the establishment request display interface, which is used to display the establishment request received by the first user identifier; or,

[0276] The display module 1501 is further configured to redirect from the relationship establishment request interface to a user identifier recommendation interface, which displays at least one user identifier recommended to the first user identifier; or,

[0277] The display module 1501 is also used to jump from the relationship establishment request interface to the information display interface of the second user identifier.

[0278] Optionally, the device further includes:

[0279] The display module 1501 is also used to scan a graphic code containing the second user identifier through a graphic code scanning interface, and then jump from the graphic code scanning interface to the relationship establishment request interface; or,

[0280] The display module 1501 is also used to display a user identifier recommendation interface, and in response to a confirmation operation of the second user identifier in the user identifier recommendation interface, to jump from the user identifier recommendation interface to the relationship establishment request interface; or,

[0281] The display module 1501 is also used to display the information display interface of the second user identifier, and to display the relationship establishment request interface in response to the relationship establishment request operation detected in the information display interface.

[0282] Optionally, the device further includes:

[0283] The display module 1501 is also used to receive the second establishment request, display the second establishment request, and the status of the second establishment request is a pending state;

[0284] The update module 1505 is also configured to update the status of the second establishment request to a processed status in response to the received relationship establishment notification.

[0285] It should be noted that the association establishment device provided in the above embodiments is only illustrated by the division of the above functional modules when establishing associations. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the terminal can be divided into different functional modules to complete all or part of the functions described above. In addition, the association establishment device and the association establishment method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0286] Figure 17 This is a schematic diagram of the structure of an association establishment device provided in an embodiment of this application. See also... Figure 17 The device includes: a request receiving module 1701, an establishment module 1702, and a notification sending module 1703.

[0287] The request receiving module 1701 is used to receive a first establishment request, which indicates that the first user identifier requests to establish an association relationship with the second user identifier;

[0288] The request receiving module 1701 is also configured to receive a second establishment request, the second establishment request indicating that the second user identifier request establishes an association relationship with the first user identifier;

[0289] Establishment module 1702 is used to establish the association between the first user identifier and the second user identifier in response to the first establishment request and the second establishment request;

[0290] The notification sending module 1703 is used to send a relationship establishment notification to the first application client logged in with the first user ID and the second application client logged in with the second user ID.

[0291] like Figure 18As shown, optionally, the establishment module 1702 is further configured to establish the association relationship if the time interval between the receipt time of the first establishment request and the second establishment request does not exceed a third preset duration.

[0292] Optionally, the device further includes:

[0293] The request sending module 1704 is used to send the second establishment request to the first application client if the reception time of the first establishment request is earlier than the reception time of the second establishment request, and the time interval between the reception times of the first establishment request and the second establishment request exceeds the third preset duration.

[0294] The establishment module 1702 is further configured to establish the association if it receives a confirmation notification from the second application client regarding the first establishment request, or if it receives a confirmation notification from the first application client regarding the second establishment request.

[0295] Optionally, the device further includes:

[0296] The request sending module 1704 is used to send the first establishment request to the second application client;

[0297] The notification receiving module 1705 is used to establish the association if it receives a confirmation notification from the second application client regarding the first establishment request.

[0298] Optionally, the relationship establishment notification may include at least one of the following: the first user identifier, the second user identifier, the first relationship identifier, the establishment time of the association, or the method of establishing the association.

[0299] It should be noted that the association establishment device provided in the above embodiments is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the application server can be divided into different functional modules to complete all or part of the functions described above. In addition, the association establishment device and the association establishment method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0300] Figure 19This is a structural block diagram of a terminal provided in an embodiment of this application. The terminal 1900 is used to perform the steps executed by the terminal or smart device in the above embodiments, and can be a portable mobile terminal, such as a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. The terminal 1900 may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other names.

[0301] Typically, terminal 1900 includes a processor 1901 and a memory 1902.

[0302] Processor 1901 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1901 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1901 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1901 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 1901 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0303] The memory 1902 may include one or more computer-readable storage media, which may be non-transitory. The memory 1902 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1902 is used to store at least one instruction, which is executed by the processor 1901 to implement the association establishment method provided in the method embodiments of this application.

[0304] In some embodiments, the terminal 1900 may also optionally include a peripheral device interface 1903 and at least one peripheral device. The processor 1901, memory 1902, and peripheral device interface 1903 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1903 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: a radio frequency circuit 1904, a touch display screen 1905, a camera assembly 1906, an audio circuit 1907, a positioning assembly 1908, and a power supply 1909.

[0305] Peripheral device interface 1903 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 1901 and memory 1902. In some embodiments, processor 1901, memory 1902 and peripheral device interface 1903 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 1901, memory 1902 and peripheral device interface 1903 can be implemented on separate chips or circuit boards, and this application embodiment does not limit this.

[0306] The radio frequency (RF) circuit 1904 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 1904 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 1904 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 1904 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 1904 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: the World Wide Web, metropolitan area networks, intranets, various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 1904 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0307] Display screen 1905 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 1905 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 1901 for processing. In this case, display screen 1905 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 1905, which serves as the front panel of terminal 1900; in other embodiments, there may be at least two display screens 1905, respectively disposed on different surfaces of terminal 1900 or in a folded design; in still other embodiments, display screen 1905 may be a flexible display screen, disposed on a curved or folded surface of terminal 1900. Furthermore, display screen 1905 may also be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 1905 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0308] The camera assembly 1906 is used to acquire images or videos. Optionally, the camera assembly 1906 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal, and the rear-facing camera is located on the back of the terminal. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 1906 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm-light flash and a cool-light flash, which can be used for light compensation at different color temperatures.

[0309] The audio circuit 1907 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 1901 for processing, or to the radio frequency circuit 1904 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 1900. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 1901 or the radio frequency circuit 1904 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 1907 may also include a headphone jack.

[0310] The positioning component 1908 is used to locate the current geographic location of the terminal 1900 in order to enable navigation or LBS (Location Based Service). The positioning component 1908 can be a positioning component based on the US GPS (Global Positioning System), China's BeiDou system, Russia's Grenas system, or the European Union's Galileo system.

[0311] The power supply 1909 is used to power the various components in the terminal 1900. The power supply 1909 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When the power supply 1909 includes a rechargeable battery, the rechargeable battery can support wired or wireless charging. The rechargeable battery can also be used to support fast charging technology.

[0312] In some embodiments, the terminal 1900 further includes one or more sensors 1910. The one or more sensors 1910 include, but are not limited to: an accelerometer 1911, a gyroscope 1912, a pressure sensor 1913, a fingerprint sensor 1914, an optical sensor 1915, and a proximity sensor 1916.

[0313] Accelerometer 1911 can detect the magnitude of acceleration along the three axes of a coordinate system established by terminal 1900. For example, accelerometer 1911 can be used to detect the components of gravitational acceleration along the three axes. Processor 1901 can control touchscreen 1905 to display the user interface in landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 1911. Accelerometer 1911 can also be used for games or for acquiring user motion data.

[0314] The gyroscope sensor 1912 can detect the orientation and rotation angle of the terminal 1900. The gyroscope sensor 1912, in conjunction with the accelerometer sensor 1911, can collect 3D motion data from the user on the terminal 1900. Based on the data collected by the gyroscope sensor 1912, the processor 1901 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, game control, and inertial navigation.

[0315] The pressure sensor 1913 can be disposed on the side bezel of the terminal 1900 and / or on the lower layer of the touch display screen 1905. When the pressure sensor 1913 is disposed on the side bezel of the terminal 1900, it can detect the user's grip signal on the terminal 1900, and the processor 1901 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 1913. When the pressure sensor 1913 is disposed on the lower layer of the touch display screen 1905, the processor 1901 can control the operable controls on the UI interface based on the user's pressure operation on the touch display screen 1905. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0316] The fingerprint sensor 1914 is used to collect the user's fingerprint. The processor 1901 identifies the user's identity based on the fingerprint collected by the fingerprint sensor 1914, or the fingerprint sensor 1914 identifies the user's identity based on the collected fingerprint. When the user's identity is identified as trusted, the processor 1901 authorizes the user to perform relevant sensitive operations, including unlocking the screen, viewing encrypted information, downloading software, making payments, and changing settings. The fingerprint sensor 1914 can be located on the front, back, or side of the terminal 1900. When the terminal 1900 has physical buttons or a manufacturer's logo, the fingerprint sensor 1914 can be integrated with the physical buttons or manufacturer's logo.

[0317] An optical sensor 1915 is used to collect ambient light intensity. In one embodiment, the processor 1901 can control the display brightness of the touch screen 1905 based on the ambient light intensity collected by the optical sensor 1915. Specifically, when the ambient light intensity is high, the display brightness of the touch screen 1905 is increased; when the ambient light intensity is low, the display brightness of the touch screen 1905 is decreased. In another embodiment, the processor 1901 can also dynamically adjust the shooting parameters of the camera assembly 1906 based on the ambient light intensity collected by the optical sensor 1915.

[0318] The proximity sensor 1916, also known as a distance sensor, is typically located on the front panel of the terminal 1900. The proximity sensor 1916 is used to detect the distance between the user and the front of the terminal 1900. In one embodiment, when the proximity sensor 1916 detects that the distance between the user and the front of the terminal 1900 is gradually decreasing, the processor 1901 controls the touchscreen display 1905 to switch from a screen-on state to a screen-off state; when the proximity sensor 1916 detects that the distance between the user and the front of the terminal 1900 is gradually increasing, the processor 1901 controls the touchscreen display 1905 to switch from a screen-off state to a screen-on state.

[0319] Those skilled in the art will understand that Figure 19 The structure shown does not constitute a limitation on terminal 1900 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0320] Figure 20This is a schematic diagram of a server structure provided in an embodiment of this application. The server 2000 can vary significantly due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 2001 and one or more memories 2002. The memories 2002 store at least one instruction, which is loaded and executed by the processor 2001 to implement the methods provided in the various method embodiments described above. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated upon here.

[0321] Server 2000 can be used to execute the steps performed by the application server in the above-mentioned association establishment method.

[0322] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one instruction, which is loaded and executed by the processor to perform the operations performed in the association relationship establishment method of the above embodiments.

[0323] This application also provides a computer-readable storage medium storing at least one instruction, which is loaded and executed by a processor to perform the operations performed in the association relationship establishment method of the above embodiments.

[0324] This application also provides a computer program that stores at least one instruction, which is loaded and executed by a processor to perform the operations performed in the association relationship establishment method of the above embodiments.

[0325] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0326] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for establishing association relationships, characterized in that, The method includes: By logging into the first application client with the first user identifier, a relationship establishment request interface is displayed, which includes the second user identifier; In response to the relationship establishment confirmation operation detected in the relationship establishment request interface, a first establishment request is sent to the application server. The first establishment request indicates that the first user identifier requests to establish an association relationship with the second user identifier. Receive the relationship establishment notification sent by the application server and display the relationship establishment notification; The second terminal is used to display a relationship establishment request interface through a second application client that has logged in with the second user identifier. The relationship establishment request interface includes the first user identifier. In response to the relationship establishment confirmation operation detected in the relationship establishment request interface, the terminal sends a second establishment request to the application server. The application server is configured to receive the first establishment request, receive the second establishment request, wherein the second establishment request indicates that the second user identifier requests to establish an association relationship with the first user identifier, and in response to the first establishment request and the second establishment request, establish the association relationship between the first user identifier and the second user identifier, and return the relationship establishment notification; The application server is further configured to send the first establishment request to the second application client. The first establishment request includes verification information entered in the relationship establishment request interface displayed by the first application client. The verification information is used by the second user to determine whether to agree to establish an association relationship with the first user. The second terminal is further configured to receive the first establishment request through the second application client and display the first establishment request.

2. The method according to claim 1, characterized in that, The process of receiving and displaying the relationship establishment notification sent by the application server includes: Upon receiving the relationship establishment notification, the relationship establishment notification is displayed on the current interface; When the display duration of the relationship establishment notification reaches a first preset duration, the display of the relationship establishment notification stops.

3. The method according to claim 1, characterized in that, The process of receiving and displaying the relationship establishment notification sent by the application server includes: Upon receiving the relationship establishment notification, the relationship establishment notification is displayed on the session interface between the first user ID and the second user ID.

4. The method according to claim 1, characterized in that, The process of receiving and displaying the relationship establishment notification sent by the application server includes: Upon receiving the relationship establishment notification, the relationship establishment notification is displayed on the notification display interface, which is used to display the notification received by the first user identifier.

5. The method according to claim 1, characterized in that, The method further includes: Upon receiving the relationship establishment notification, a correspondence between the second user identifier and the interaction identifier is created, wherein the interaction identifier indicates that the first user identifier and the second user identifier establish an association relationship by sending establishment requests to each other; When the second user identifier is displayed, the interaction identifier is displayed according to the correspondence.

6. The method according to claim 5, characterized in that, The step of displaying the interaction identifier according to the correspondence when displaying the second user identifier includes: The second user identifier and the interaction identifier are displayed correspondingly in the user identifier display interface, which is used to display user identifiers that have established a relationship with the first user identifier; or... In the session interface between the first user ID and the second user ID, the second user ID and the interaction ID are displayed.

7. The method according to claim 5, characterized in that, The step of displaying the interactive identifier according to the correspondence includes: Obtain the display parameters of the interactive icon, wherein the display parameters indicate the display style of the interactive icon; The interactive identifier is displayed according to the display parameters.

8. The method according to claim 5, characterized in that, After creating the correspondence between the second user identifier and the interaction identifier, the method further includes: If no session message sent by the second user identifier is received within the second preset time period before the current time, the correspondence is terminated.

9. The method according to claim 1, characterized in that, After sending a first establishment request to the application server in response to the confirmation operation of the second user identifier, the method further includes: The user is redirected from the relationship establishment request interface to a user identifier display interface, which displays user identifiers that have been associated with the first user identifier; or... The user is redirected from the relationship establishment request interface to the establishment request display interface, which displays the establishment request received by the first user identifier; or... The user is redirected from the relationship establishment request interface to a user identifier recommendation interface, which displays at least one user identifier recommended to the first user identifier; or, The user is redirected from the relationship establishment request interface to the information display interface of the second user identifier.

10. The method according to claim 1, characterized in that, Before displaying the relationship establishment request interface on the first application client that logs in with the first user identifier, the method further includes: Scan the graphic code containing the second user identifier using the graphic code scanning interface, and then be redirected to the relationship establishment request interface; or... Display a user ID recommendation interface, and in response to a confirmation operation on the second user ID in the user ID recommendation interface, redirect from the user ID recommendation interface to the relationship establishment request interface; or... Display the information display interface of the second user identifier, and in response to the relationship establishment request operation detected in the information display interface, display the relationship establishment request interface.

11. The method according to claim 1, characterized in that, The method further includes: Receive the second establishment request, display the second establishment request, and set the status of the second establishment request to pending. In response to the received relationship establishment notification, the status of the second establishment request is updated to processed.

12. The method according to claim 1, characterized in that, The process of receiving and displaying the relationship establishment notification sent by the application server includes: Upon receiving the relationship establishment notification, the second user identifier and the relationship establishment notification are displayed in the user identifier display interface. The user identifier display interface is used to display user identifiers that have established an association with the first user identifier.

13. The method according to claim 1, characterized in that, The relationship establishment notification includes at least one of the following: the first user identifier, the second user identifier, the establishment time of the association, or the method of establishing the association.

14. A method for establishing association relationships, characterized in that, The method includes: Receive a first establishment request, the first establishment request indicating that a first user identifier requests to establish an association relationship with a second user identifier; Receive a second establishment request, the second establishment request indicating that the second user identifier requests to establish an association relationship with the first user identifier; In response to the first establishment request and the second establishment request, an association relationship is established between the first user identifier and the second user identifier; Send a relationship establishment notification to the first application client logged in with the first user identifier and the second application client logged in with the second user identifier; After receiving the first establishment request, the method further includes: sending the first establishment request to the second application client; the first establishment request includes verification information, which is used by the second user to determine whether to agree to establish an association with the first user; the second terminal is used to receive the first establishment request through the second application client and display the first establishment request; The second terminal is also used to display a relationship establishment request interface through the second application client. The relationship establishment request interface includes the first user identifier. In response to the relationship establishment confirmation operation detected in the relationship establishment request interface, the terminal sends the second establishment request to the application server.

15. The method according to claim 14, characterized in that, The step of establishing the association between the first user identifier and the second user identifier in response to the first establishment request and the second establishment request includes: If the time interval between receiving the first establishment request and the second establishment request does not exceed the third preset duration, the association relationship is established.

16. The method according to claim 15, characterized in that, The method further includes: If the reception time of the first establishment request is earlier than the reception time of the second establishment request, and the time interval between the reception times of the first establishment request and the second establishment request exceeds the third preset duration, the second establishment request is sent to the first application client. If a confirmation notification from the second application client regarding the first establishment request is received, or if a confirmation notification from the first application client regarding the second establishment request is received, then the association relationship is established.

17. The method according to claim 14, characterized in that, After sending the first establishment request to the second application client, the method further includes: If the second application client receives a confirmation notification for the first establishment request, then the association relationship is established.

18. The method according to claim 14, characterized in that, The relationship establishment notification includes at least one of the following: the first user identifier, the second user identifier, the establishment time of the association, or the method of establishing the association.

19. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one instruction, which is loaded and executed by the processor to perform the operations performed in the association establishment method as described in any one of claims 1-18.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction, which is loaded and executed by a processor to perform the operations performed in the association establishment method as described in any one of claims 1-18.

Images