User relationship processing method and apparatus

Abstract

Embodiments of the present specification provide a user relationship processing method and device, wherein a user relationship processing method comprises: obtaining user feature data submitted by a first user for configuring a user relationship for a second user; querying whether a reverse relationship label configured by the second user for the first user exists in a user relationship network; if it exists, generating a forward relationship label corresponding to the reverse relationship label and pushing it to the first user; and in the case of detecting a label confirmation instruction, updating the user feature data and the forward relationship label to the user relationship network.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a user relationship processing method and apparatus. Background Technology

[0002] With the development of internet technology and the popularization of mobile terminals, more and more services are extending to online scenarios. The application scope and application scenarios of online services are becoming more and more extensive. Interactions between users are no longer limited to face-to-face environments, but are gradually taking place in online environments. In this process, user relationships between users are becoming more and more important. Based on user relationships, it is possible to better identify each other and thus better carry out interactive activities. Summary of the Invention

[0003] This specification provides one or more embodiments of a user relationship processing method, comprising: obtaining user feature data submitted by a first user for configuring user relationships with a second user; querying a user relationship network to see if a reverse relationship tag configured by the second user for the first user exists; if it exists, generating a forward relationship tag corresponding to the reverse relationship tag and pushing it to the first user; and updating the user feature data and the forward relationship tag to the user relationship network upon detecting a tag confirmation instruction.

[0004] This specification provides one or more embodiments of a user relationship-based recommendation processing method, comprising: obtaining a search request from an accessing user performing a user relationship search on a target service; if the search request type is an association request type, extracting first relationship data that has a direct association with the accessing user from a user relationship network; recommending the first relationship data and second relationship data that has an indirect association with the accessing user to the accessing user; the second relationship data is obtained after performing association prediction based on the user relationship network; wherein, the user relationship network is updated according to user feature data submitted by a first user for user relationship configuration for a second user and reverse relationship tags configured by the second user for the first user.

[0005] This specification provides one or more embodiments of a user relationship processing apparatus, comprising: a data acquisition module configured to acquire user feature data submitted by a first user for configuring user relationships with a second user; a tag query module configured to query a user relationship network for the existence of a reverse relationship tag configured by the second user for the first user; a tag push module configured to, if present, generate a forward relationship tag corresponding to the reverse relationship tag and push it to the first user; and a network update module configured to, upon detecting a tag confirmation instruction, update the user feature data and the forward relationship tag to the user relationship network.

[0006] This specification provides one or more embodiments of a user relationship-based recommendation processing apparatus, comprising: a request acquisition module configured to acquire a search request from an accessing user performing a user relationship search on a target service; a data extraction module configured to extract, if the search request is of the association request type, first relationship data that has a direct association with the accessing user from a user relationship network; and a data recommendation module configured to recommend the first relationship data and second relationship data that has an indirect association with the accessing user to the accessing user; the second relationship data is obtained after performing association prediction based on the user relationship network; wherein the user relationship network is updated according to user feature data submitted by a first user for user relationship configuration for a second user and reverse relationship tags configured by the second user for the first user.

[0007] This specification provides one or more embodiments of a user relationship processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire user feature data submitted by a first user for configuring user relationships with a second user; query a user relationship network to see if a reverse relationship tag configured by the second user for the first user exists; if it exists, generate a forward relationship tag corresponding to the reverse relationship tag and push it to the first user; and, upon detecting a tag confirmation instruction, update the user feature data and the forward relationship tag to the user relationship network.

[0008] This specification provides one or more embodiments of a user relationship-based recommendation processing device, comprising: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire a search request from an accessing user to perform a user relationship search on a target service; if the search request is of the association request type, extract first relationship data that has a direct association with the accessing user from a user relationship network; recommend the first relationship data and second relationship data that has an indirect association with the accessing user to the accessing user; the second relationship data is obtained after performing association prediction based on the user relationship network; wherein the user relationship network is updated according to user feature data submitted by a first user for user relationship configuration for a second user and reverse relationship tags configured by the second user for the first user.

[0009] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process: Obtaining user feature data submitted by a first user for configuring user relationships with a second user; querying the user relationship network to see if a reverse relationship tag configured by the second user for the first user exists; if it exists, generating a forward relationship tag corresponding to the reverse relationship tag and pushing it to the first user; and updating the user feature data and the forward relationship tag to the user relationship network upon detecting a tag confirmation instruction.

[0010] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process: Obtaining a search request from an accessing user to perform a user relationship search on a target service. If the search request type is an association request type, extracting first relationship data that has a direct association with the accessing user from a user relationship network. Recommending the first relationship data and second relationship data that has an indirect association with the accessing user to the accessing user; the second relationship data is obtained after performing association prediction based on the user relationship network; wherein, the user relationship network is updated according to user feature data submitted by a first user for user relationship configuration for a second user and reverse relationship tags configured by the second user for the first user. Attached Figure Description

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

[0012] Figure 1 A flowchart illustrating a user relationship processing method provided in one or more embodiments of this specification;

[0013] Figure 2 A schematic diagram of a user relationship network provided for one or more embodiments of this specification;

[0014] Figure 3 A flowchart illustrating a user relationship processing method applied to a service processing scenario, provided in one or more embodiments of this specification;

[0015] Figure 4 A flowchart illustrating a user relationship-based recommendation processing method provided for one or more embodiments of this specification;

[0016] Figure 5 A flowchart illustrating a user relationship-based recommendation processing method for service processing scenarios, provided in one or more embodiments of this specification.

[0017] Figure 6 A schematic diagram of a user relationship processing device provided for one or more embodiments of this specification;

[0018] Figure 7 A schematic diagram of a user relationship-based recommendation processing device provided for one or more embodiments of this specification;

[0019] Figure 8 A schematic diagram of the structure of a user relationship processing device provided for one or more embodiments of this specification;

[0020] Figure 9 This is a schematic diagram of a user relationship-based recommendation processing device provided for one or more embodiments of this specification. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0022] This specification provides an example of a user relationship processing method:

[0023] In practical applications, user relationships are often managed in online environments using groups. However, group management often has the drawback of limiting the number of members. Each group can only have a specific number of members, and there is also a limit to the number of groups each user can participate in. Each user can only participate in a specific number of groups.

[0024] To address this, the user relationship processing method provided in this embodiment generates forward relationship data corresponding to the reverse relationship data configured by the second user for the first user, based on the reverse relationship data queried from the user relationship network, and pushes it to the first user. It also updates the user feature data of the second user and the forward relationship data submitted by the first user to the user relationship network. Specifically, after obtaining the user feature data submitted by the first user for user relationship configuration for the second user, the method queries the reverse relationship tags configured by the second user for the first user, generates forward relationship tags corresponding to the queried reverse relationship tags, and pushes them to the first user. Upon detecting a tag confirmation command, the user feature data and forward relationship tags are updated to the user relationship network. This utilizes the generated forward relationship tags corresponding to the reverse relationship tags configured by the second user for the first user to assist the first user in configuring user relationships for the second user, improving the convenience and efficiency of user relationship configuration. Furthermore, updating the user relationship network enhances the comprehensiveness and flexibility of user relationship management within the network.

[0025] Reference Figure 1 The user relationship processing method provided in this embodiment can be applied to a server, and specifically includes steps S102 to S108.

[0026] Step S102: Obtain user feature data submitted by the first user for configuring user relationships with the second user.

[0027] The user relationship configuration described in this embodiment includes configuring the user feature data of the second user and / or configuring the relationship tag of the second user; wherein, the user feature data includes the user's own feature data and / or the feature data carried by the user, and optionally, the user feature data includes at least one of the following: name, contact information, credential type, and credential identifier.

[0028] In this embodiment, user relationships include social or kinship relationships between users. Social relationships refer to relationships involving social behavior, such as friendships or colleague relationships. In addition, user relationships also include friend relationships through instant messaging applications or transaction relationships involving online transactions.

[0029] In specific implementation, to improve the convenience of user relationship configuration, a configuration entry can be provided, through which user relationship configuration is performed. In an optional implementation provided in this embodiment, the user feature data is obtained in the following way: according to the first user's trigger instruction for the configuration entry, a configuration template for user relationship configuration is displayed to the first user; the user feature data entered by the first user through the configuration template is collected.

[0030] The configuration entry point refers to the configuration entry point for configuring user relationships.

[0031] Specifically, based on the first user's trigger command for the configuration entry, a configuration page containing a configuration template for user relationship configuration is displayed to the first user; user feature data entered by the first user through the configuration template is collected.

[0032] To facilitate the first user's management of user relationships, after the first user configures the user relationship for the second user, the user relationship details of the second user can be displayed on the first user's terminal device when the trigger command of the first user for the second user on the initial page is detected.

[0033] Step S104: Query the user relationship network to see if there is a reverse relationship label configured by the second user for the first user.

[0034] In the above-mentioned step of obtaining user feature data submitted by the first user for configuring user relationships with the second user, this step involves querying whether there is a reverse relationship label configured by the second user for the first user. Specifically, this involves querying the user relationship network to see if there is a reverse relationship label configured by the second user for the first user.

[0035] The reverse relationship label mentioned in this embodiment refers to the label of the user relationship configured by the second user for the first user. Optionally, the reverse relationship label records the user relationship. For example, if the user relationship or association in the reverse relationship label is "wife," it means that the user relationship configured by the second user for the first user is "wife." The user relationship network refers to a network that represents the user relationship or association between every two users, such as... Figure 2 The user relationship network shown has three user nodes: the first user, the second user, and the third user. The first user configures the relationship label for the second user as "husband," and the second user configures the relationship label for the first user as "wife." The relationship labels configured by the users corresponding to other user nodes for other users are similar and will not be described in detail here.

[0036] Optionally, the user relationship network is used to recommend first relationship data that has a direct relationship with the user and second relationship data that has an indirect relationship with the user based on the user relationship search request.

[0037] In practice, to improve the convenience of querying reverse relationship tags, the user account of the second user can be determined based on the user characteristic data of the second user, and the user account of the second user can be used to query in the user relationship network whether there is a reverse relationship tag configured by the second user for the first user.

[0038] In an optional implementation of this embodiment, if the result of querying the user relationship network to see if a reverse relationship tag configured by a second user for a first user does not exist is found, the following operation is performed:

[0039] Obtain the relationship tags configured by the first user for the second user;

[0040] Update the user feature data and the relationship tags to the user relationship network.

[0041] Specifically, if no reverse relationship tag configured by the second user for the first user is found in the user relationship network, a reminder message for entering the relationship tag can be generated and sent to the first user. The first user's terminal device displays the reminder message and the relationship tag entry control, and obtains the relationship tag configured by the first user for the second user after the relationship tag entry control is triggered, and updates the relationship tag and the user feature data of the second user to the user relationship network.

[0042] The step of updating the user feature data and the relationship label to the user relationship network includes: determining a second user node in the user relationship network based on the user account queried based on the user feature data, and establishing a connection relationship between the first user node and the second user node in the user relationship network based on the positive relationship label; and associating the positive relationship label and the user feature data with the connection relationship.

[0043] Step S106: Generate the positive relationship label corresponding to the reverse relationship label and push it to the first user.

[0044] The above steps involve querying the user relationship network to see if a reverse relationship label configured by the second user for the first user exists. If it does not exist, the collected relationship label configured by the first user for the second user is obtained, and the user feature data and relationship label are updated to the user relationship network. If it exists, a positive relationship label corresponding to the reverse relationship label is generated and pushed to the first user.

[0045] The positive relationship label mentioned in this embodiment refers to a label representing a user relationship or association that is the opposite of the user relationship or association in the negative relationship label. For example, if the user relationship in the negative relationship label is "wife", then the user relationship in the positive relationship label is "husband".

[0046] In practice, when a reverse relationship label configured by the second user for the first user is found, in order to facilitate the first user's user relationship configuration, a positive relationship label corresponding to the reverse relationship label can be generated and pushed to the first user, so that the first user can configure the user relationship for the second user based on the positive relationship label.

[0047] For example, if the second user, who is found in the user relationship network, configures the reverse relationship label for the first user as "wife", the positive relationship label of the reverse relationship label is generated as "husband" and pushed to the first user.

[0048] In the process of generating the positive relationship label corresponding to the reverse relationship label and pushing it to the first user, in order to improve the user experience of the first user, a positive relationship label corresponding to the reverse relationship label can be generated, and an auxiliary configuration reminder can be generated and pushed to the first user based on the reverse relationship label and / or the positive relationship label husband. Continuing with the previous example, the reverse relationship label is wife, and the generated positive relationship label is husband. An auxiliary configuration reminder is generated based on the reverse relationship label and the positive relationship label husband: "The second user has set you as wife. Do you want to set the second user as husband?" The auxiliary configuration reminder is then pushed to the first user.

[0049] Step S108: Upon detecting a tag confirmation instruction, update the user feature data and the positive relationship tag to the user relationship network.

[0050] The above-mentioned generation of positive relationship labels corresponding to reverse relationship labels and pushes them to the first user. In this step, the user feature data and positive relationship labels are updated to the user relationship network. Specifically, when a label confirmation instruction is detected, the user feature data and positive relationship labels are updated to the user relationship network.

[0051] In a specific implementation, in one optional embodiment provided by this example, the following operations are performed during the process of updating user feature data and positive relationship tags to the user relationship network:

[0052] The second user node is determined in the user relationship network based on the user account queried based on the user feature data, and a connection relationship between the first user node and the second user node of the first user is established in the user relationship network based on the positive relationship label.

[0053] The positive relationship label and the user feature data are associated with the connection relationship.

[0054] The user account includes the service account of the user in the configuration service for configuring user relationships. The configuration service includes an application running on the terminal device or a subroutine embedded in a third-party application.

[0055] Specifically, a second user node is determined in the user relationship network based on the user account, and a connection relationship is established between the first user node and the second user node based on the positive relationship label, and the positive relationship label and user feature data are associated with the connection relationship.

[0056] For example, based on the user account, a second user node of the second user is constructed in the user relationship network, and based on the positive relationship label "husband", a connection relationship is established from the first user node of the first user to the second user node in the user relationship network, and the positive relationship label "husband" and the user feature data of the second user are associated with the connection relationship.

[0057] Furthermore, the above-described process of updating user feature data and positive feature tags to the user relationship network can be replaced by determining the second user node in the user relationship network based on the second user's user identifier, establishing a connection relationship between the first user node and the second user node in the user relationship network based on the positive relationship tags, associating the positive relationship tags and the user feature data of the second user with the connection relationship, and forming a new implementation method with other processing steps provided in this embodiment.

[0058] In practical applications, the first user can edit, delete, or add user relationship data during the management process, thereby improving the flexibility of user relationship data management. The user relationship data refers to the first user's own user relationship data, which records users who are related to the first user and the relationship types of direct relationships. For example, the user relationship data records a second user who is related to the first user, and the relationship type of the relationship is kinship.

[0059] In one optional implementation of this embodiment, after determining the second user node based on the user account, establishing a connection between the first user node and the second user node, and associating the positive relationship label and user feature data with the connection relationship, and updating the user feature data and positive relationship label to the user relationship network upon detecting a label confirmation instruction, the following operation is further performed:

[0060] Detect the deletion command submitted by the first user in response to the second user;

[0061] The connection relationship is terminated in the user relationship network, and the second user node is deleted.

[0062] Furthermore, the process of detecting the deletion command submitted by the first user to the second user, terminating the connection in the user relationship network, and deleting the second user node can be replaced by rolling back the update of user feature data and positive relationship tags to the user relationship network, and forming a new implementation method with other processing steps provided in this embodiment; wherein, the rollback process includes: detecting the deletion command submitted by the first user to the second user; terminating the connection in the user relationship network, and deleting the second user node.

[0063] In the specific execution process, in order to improve the comprehensiveness of the user relationship network and thus improve the search efficiency of users when searching for user relationships in specific scenarios, the feature data of users in the user relationship network can be updated. In an optional implementation method provided in this embodiment, the user feature data in the user relationship network is updated in the following way: the service registration information of the second user in the target service is updated according to the user feature data.

[0064] And / or,

[0065] Based on the user characteristic data, the user characteristic data configured by the third user for the second user in the user relationship network is updated.

[0066] The service registration information refers to the registration information used to register for the target service, such as the contact information and identity credentials of the second user. The third user refers to the remaining users in the user relationship network besides the first and second users.

[0067] Specifically, based on the user characteristic data submitted by the first user to the second user in the user relationship network, the service registration information of the second user in the target service is updated or supplemented; and / or, based on the user characteristic data submitted by the first user to the second user in the user relationship network, the user characteristic data configured by the third user to the second user in the user relationship network is updated or supplemented.

[0068] In practical applications, target users often need to manually input user characteristic data, such as name and phone number, during the service registration process. Service registration based solely on this input data leads to low efficiency and presents registration barriers for certain users, such as elderly users who may have operational difficulties and be unable to input their user characteristic data, resulting in registration failure. To address this, and to improve the efficiency and success rate of service registration, facilitating service registration for all types of users, service registration can be performed based on user characteristic data retrieved from a user relationship network. In one optional implementation of this embodiment, service registration is performed on target users in the following manner:

[0069] Based on the service registration instruction submitted by the accessing user, read the user characteristic data of the accessing user from the user relationship network;

[0070] Service registration is performed on the accessing user based on the read user characteristic data.

[0071] The user who can access the service can be any user corresponding to any user node in the user relationship network.

[0072] In practical applications, users have a need for user relationship search, such as searching for a user with a kinship relationship. To improve the search efficiency and success rate of users in the user relationship search process, and to enhance the comprehensiveness of the search, we can recommend first relationship data that is directly related to the user, and second relationship data that is indirectly related to the user. In one optional implementation of this embodiment, relationship data is recommended to users in the following way:

[0073] Based on the search request submitted by the user to perform a user relationship search, the system recommends first relationship data that has a direct relationship with the user and second relationship data that has an indirect relationship with the user to the user.

[0074] Optionally, the first relationship data is extracted from the user relationship network, and the second relationship data is obtained after performing association prediction based on the user relationship network.

[0075] The user relationship search refers to the search for users who are related to the visiting user, such as searching for a user who is related to the visiting user. Optionally, the direct relationship includes the relationship corresponding to the relationship tag obtained by the visiting user in the user relationship configuration. The indirect relationship includes the relationship obtained by predicting the relationship based on the relationship tag obtained by other users in the user relationship network in the user relationship configuration.

[0076] The first relationship data refers to relationship data containing relationship tags that are directly related to the accessing user, and the second relationship data refers to relationship data containing relationship tags that are indirectly related to the accessing user, such as... Figure 2 As shown, the first relationship data of the second user is "First User: Wife", and the second relationship data of the second user is "Third User: Mother-in-law".

[0077] In one optional implementation of this embodiment, the correlation prediction includes:

[0078] Read from the user relationship network the first relationship label configured by the accessing user and the first direct user for each other, and the second relationship label configured by the first direct user and the second direct user for each other.

[0079] Based on the first relationship tag and the second relationship tag, predict the third relationship tag of the accessing user for the second direct user.

[0080] Here, both the first direct user and the second direct user refer to users who have a direct relationship with the accessing user.

[0081] like Figure 2 As shown, the accessing user is the second user, the first direct user is the first user, and the second direct user is the third user. The first relationship label "wife, husband" configured by the second user and the first user for each other, and the second relationship label "mother, daughter" configured by the first user and the third user for each other are read. Based on the first relationship label "wife, husband" and the second relationship label "mother, daughter", the third relationship label of the second user for the third user is predicted to be "mother-in-law".

[0082] After the above-mentioned process of recommending first relationship data that is directly related to the user and second relationship data that is indirectly related to the user based on the search request submitted by the user, in an optional implementation of this embodiment, the following operation is also performed:

[0083] Determine the selected user chosen by the accessing user from the first relation data and the second relation data;

[0084] Based on the selected user, the corresponding operation process is executed.

[0085] For example, the user accesses the first relationship data and the second relationship data to select a user, and then processes the transfer to the selected user in the transfer service based on the selected user.

[0086] In addition, relationship data can also be recommended to visiting users in the following way: Obtain the user's search request for user relationships in the target service; if the search request type is an association request type, extract first relationship data that has a direct association with the user from the user relationship network; recommend the first relationship data and second relationship data that has an indirect association with the user to the user; the second relationship data is obtained after association prediction based on the user relationship network; optionally, the user relationship network is updated according to user feature data submitted by the first user for user relationship configuration for the second user and the reverse relationship tags configured by the second user for the first user. If the search request type is a preset request type, extract the first relationship data from the user relationship network and recommend the first relationship data to the user.

[0087] The preset request type includes a normal request type. In the case of a normal request type, first relationship data with a direct correlation can be recommended to the accessing user.

[0088] The following description uses the application of a user relationship processing method provided in this embodiment in a service processing scenario as an example to further illustrate the user relationship processing method provided in this embodiment. (See also...) Figure 3 The user relationship processing method applied to service processing scenarios includes the following steps.

[0089] Step S302: Obtain user feature data submitted by the first user for configuring user relationships with the second user.

[0090] Step S304: Query the user relationship network to see if there is a reverse relationship label configured by the second user for the first user;

[0091] If it exists, proceed with step S306 below;

[0092] If it does not exist, obtain the relationship label configured by the first user for the second user, and update the user feature data and the collected relationship label to the user relationship network.

[0093] Step S306: Generate the positive relationship label corresponding to the reverse relationship label and push it to the first user.

[0094] Step S308: Upon detecting a tag confirmation instruction, determine the second user node in the user relationship network based on the user account queried based on user feature data, and establish a connection relationship between the first user node and the second user node in the user relationship network based on the positive relationship tag.

[0095] Step S310: Associate the positive relationship label and user feature data with the connection relationship.

[0096] Step S312: Based on the search request submitted by the user to search for user relationships, recommend first relationship data that has a direct relationship with the user and second relationship data that has an indirect relationship with the user.

[0097] Step S314: Determine the selected user chosen by the accessing user from the first relation data and the second relation data, and perform the corresponding operation processing based on the selected user.

[0098] This specification provides an example of a recommendation processing method based on user relationships:

[0099] The user relationship-based recommendation processing method provided in this embodiment, when the user's search request for user relationships in the target service is a relationship request type, extracts first relationship data that has a direct relationship with the user from the user relationship network, and recommends the first relationship data and second relationship data that has an indirect relationship with the user to the user. In this way, by recommending relationship data from both the first and second relationship data, the comprehensiveness of the recommendation processing is improved. At the same time, by providing comprehensive recommendations during the user's user relationship search, the search efficiency and search success rate are improved.

[0100] Reference Figure 4 The recommendation processing method based on user relationships provided in this embodiment can be applied to a server, and specifically includes steps S402 to S406.

[0101] Step S402: Obtain the search request from the accessing user to perform a user relationship search on the target service.

[0102] The target service described in this embodiment refers to a service in which a user has a search need to perform a user relationship search during the process of accessing the target service. For example, if the target service is a money transfer service, the user needs to identify the money transfer user during the process of accessing the money transfer service, and thus has a need to search for the money transfer user. Or, if the target service is an auxiliary payment service, the user needs to identify the auxiliary payment user during the process of accessing the auxiliary payment service, and thus has a need to search for the auxiliary payment user. In addition, the target service also includes other types of services, and other services with user relationship search needs are also within the scope of protection of this solution, which will not be listed here.

[0103] The user relationship search refers to the search for users who are related to the visiting user, such as searching for a user who is related to the visiting user.

[0104] In practice, users can submit a search request to search for user relationships by triggering the search control of the target service. In this step, the search request of the user to search for user relationships in the target service is obtained.

[0105] Step S404: Extract first relationship data that has a direct association with the accessing user from the user relationship network.

[0106] The above-mentioned step of obtaining search requests from users performing user relationship searches on the target service involves extracting first relationship data directly related to the users from the user relationship network. Specifically, if the search request type is a relationship request type, then first relationship data directly related to the users is extracted from the user relationship network.

[0107] In this embodiment, the first relational data refers to relational data containing relational tags that are directly related to the accessing user; such as... Figure 2 As shown, the first relationship data of the second user is "First User: Wife". The direct relationship includes the relationship corresponding to the relationship tag obtained by the user in configuring user relationships.

[0108] The user relationship network refers to a network that represents the user relationship or association between any two users, such as... Figure 2 The user relationship network shown has three user nodes: the first user, the second user, and the third user. The first user configures the relationship label for the second user as "husband," and the second user configures the relationship label for the first user as "wife." The relationship labels configured by the users corresponding to other user nodes for other users are similar and will not be described in detail here.

[0109] Optionally, the user relationship network is used to recommend first relationship data that has a direct relationship with the user and second relationship data that has an indirect relationship with the user based on the user relationship search request.

[0110] In a specific implementation, in one optional embodiment, if the search request type is a preset request type, the first relationship data is extracted from the user relationship network, and the first relationship data is recommended to the accessing user. The preset request type includes a normal request type; in the case of a normal request type, first relationship data with a direct association can be recommended to the accessing user.

[0111] Step S406: Recommend the first relationship data and the second relationship data that has an indirect association with the accessing user to the accessing user.

[0112] The first relationship data that is directly related to the accessing user is extracted from the user relationship network as described above. In this step, the first relationship data that is directly related to the accessing user and the second relationship data that is indirectly related to the accessing user are recommended to the accessing user.

[0113] The indirect association described in this embodiment includes associations predicted based on relationship tags obtained from user relationship configurations of other users in the user relationship network. The second relationship data refers to relationship data containing relationship tags that have indirect associations with the accessing user, such as... Figure 2 As shown, the second relationship data of the second user is "third user: mother-in-law". Optionally, the second relationship data is obtained after predicting the association relationship based on the user relationship network; optionally, the user relationship network is updated according to the user feature data submitted by the first user for the user relationship configuration of the second user and the reverse relationship label configured by the second user for the first user.

[0114] In a specific implementation, one optional embodiment of this example includes the following:

[0115] Read from the user relationship network the first relationship label configured by the accessing user and the first direct user for each other, and the second relationship label configured by the first direct user and the second direct user for each other.

[0116] Based on the first relationship tag and the second relationship tag, predict the third relationship tag of the accessing user for the second direct user.

[0117] Here, both the first direct user and the second direct user refer to users who have a direct relationship with the accessing user.

[0118] like Figure 2 As shown, the accessing user is the second user, the first direct user is the first user, and the second direct user is the third user. The first relationship label "wife, husband" configured by the second user and the first user for each other, and the second relationship label "mother, daughter" configured by the first user and the third user for each other are read. Based on the first relationship label "wife, husband" and the second relationship label "mother, daughter", the third relationship label of the second user for the third user is predicted to be "mother-in-law".

[0119] After recommending the first relationship data and the second relationship data that are indirectly related to the visiting user to the visiting user, in an optional implementation of this embodiment, the following operation is also performed:

[0120] Determine the selected user chosen by the accessing user from the first relation data and the second relation data;

[0121] Based on the selected user, the corresponding operation is performed on the target service.

[0122] For example, the user accesses the first relationship data and the second relationship data to select a user, and then processes the transfer to the selected user in the transfer service based on the selected user.

[0123] In an optional implementation method provided in this embodiment, the user relationship network is updated in the following way:

[0124] Based on the user feature data submitted by the first user for configuring user relationships with the second user, query the reverse relationship tags configured by the second user for the first user in the user relationship network;

[0125] Generate the positive relationship tags corresponding to the queried reverse relationship tags and push them to the first user;

[0126] Upon detecting a tag confirmation instruction, the user feature data and the positive relationship tag are updated to the user relationship network.

[0127] Specifically, the system can obtain user feature data submitted by the first user for configuring user relationships with the second user; query the user relationship network to see if there is a reverse relationship label configured by the second user for the first user; if so, generate a positive relationship label corresponding to the reverse relationship label and push it to the first user; and update the user feature data and positive relationship label to the user relationship network when a label confirmation instruction is detected.

[0128] First, the user characteristic data submitted by the first user for configuring user relationships with the second user is obtained; wherein the user relationship configuration includes the first user configuring the user characteristic data of the second user and / or configuring the relationship tags of the second user; the user characteristic data includes the user's own characteristic data and / or the characteristic data carried by the user, and optionally, the user characteristic data includes at least one of the following: name, contact information, credential type, credential identifier.

[0129] In this embodiment, user relationships include social or kinship relationships between users. Social relationships refer to relationships involving social behavior, such as friendships or colleague relationships. In addition, user relationships also include friend relationships through instant messaging applications or transaction relationships involving online transactions.

[0130] In specific implementation, to improve the convenience of user relationship configuration, a configuration entry can be provided, through which user relationship configuration is performed. In an optional implementation provided in this embodiment, the user feature data is obtained in the following way: according to the first user's trigger instruction for the configuration entry, a configuration template for user relationship configuration is displayed to the first user; the user feature data entered by the first user through the configuration template is collected.

[0131] The configuration entry point refers to the entry point for configuring user relationships.

[0132] Specifically, based on the first user's trigger command for the configuration entry, a configuration page containing a configuration template for user relationship configuration is displayed to the first user; user feature data entered by the first user through the configuration template is collected.

[0133] To facilitate the first user's management of user relationships, after the first user configures the user relationship for the second user, the user relationship details of the second user can be displayed on the first user's terminal device when the trigger command of the first user for the second user on the initial page is detected.

[0134] The above involves querying the user relationship network to see if the second user has configured a reverse relationship label for the first user.

[0135] The process involves obtaining user feature data submitted by the first user for configuring user relationships with the second user. After that, it is necessary to query whether there is a reverse relationship label configured by the second user for the first user. Specifically, the process involves querying the user relationship network to see if there is a reverse relationship label configured by the second user for the first user.

[0136] The reverse relationship label refers to the label of the user relationship configured by the second user for the first user. Optionally, the reverse relationship label records the user relationship. For example, if the user relationship or association in the reverse relationship label is "wife", it means that the user relationship configured by the second user for the first user is "wife".

[0137] In practice, to improve the convenience of querying reverse relationship tags, the user account of the second user can be determined based on the user characteristic data of the second user, and the user account of the second user can be used to query in the user relationship network whether there is a reverse relationship tag configured by the second user for the first user.

[0138] In an optional implementation of this embodiment, if the result of querying the user relationship network to see if a reverse relationship tag configured by a second user for a first user does not exist is found, the following operation is performed:

[0139] Obtain the relationship tags configured by the first user for the second user;

[0140] Update the user feature data and the relationship tags to the user relationship network.

[0141] Specifically, if no reverse relationship tag configured by the second user for the first user is found in the user relationship network, a reminder message for entering the relationship tag can be generated and sent to the first user. The first user's terminal device displays the reminder message and the relationship tag entry control, and obtains the relationship tag configured by the first user for the second user after the relationship tag entry control is triggered, and updates the relationship tag and the user feature data of the second user to the user relationship network.

[0142] The step of updating the user feature data and the relationship label to the user relationship network includes: determining a second user node based on the user account queried based on the user feature data, and establishing a connection relationship from the first user node to the second user node based on the relationship label; and associating the relationship label and the user feature data with the connection relationship.

[0143] The above process involves querying the user relationship network to see if a reverse relationship label configured by the second user for the first user exists. If it does not exist, the process retrieves the relationship label configured by the first user for the second user and updates the user feature data and relationship label to the user relationship network. If it exists, the process generates a positive relationship label corresponding to the reverse relationship label and pushes it to the first user.

[0144] The positive relationship tag refers to a tag that represents the opposite user relationship or association relationship to the negative relationship tag. For example, if the user relationship in the negative relationship tag is "wife", then the user relationship in the positive relationship tag is "husband".

[0145] In practice, when a reverse relationship label configured by the second user for the first user is found, in order to facilitate the first user's user relationship configuration, a positive relationship label corresponding to the reverse relationship label can be generated and pushed to the first user, so that the first user can configure the user relationship for the second user based on the positive relationship label.

[0146] For example, if the second user, who is found in the user relationship network, configures the reverse relationship label for the first user as "wife", the positive relationship label of the reverse relationship label is generated as "husband" and pushed to the first user.

[0147] In the process of generating the positive relationship label corresponding to the reverse relationship label and pushing it to the first user, in order to improve the user experience of the first user, a positive relationship label corresponding to the reverse relationship label can be generated, and an auxiliary configuration reminder can be generated and pushed to the first user based on the reverse relationship label and / or the positive relationship label husband. Continuing with the previous example, the reverse relationship label is wife, and the generated positive relationship label is husband. An auxiliary configuration reminder is generated based on the reverse relationship label and the positive relationship label husband: "The second user has set you as wife. Do you want to set the second user as husband?" The auxiliary configuration reminder is then pushed to the first user.

[0148] The above process generates a positive relationship label corresponding to the reverse relationship label and pushes it to the first user. After that, the user feature data and positive relationship label are updated to the user relationship network. Specifically, when a label confirmation instruction is detected, the user feature data and positive relationship label are updated to the user relationship network.

[0149] In a specific implementation, in one optional embodiment provided by this example, the following operations are performed during the process of updating user feature data and positive relationship tags to the user relationship network:

[0150] The second user node is determined in the user relationship network based on the user account queried based on the user feature data, and a connection relationship between the first user node and the second user node of the first user is established in the user relationship network based on the positive relationship label.

[0151] The positive relationship label and the user feature data are associated with the connection relationship.

[0152] The user account includes the service account of the user in the configuration service for configuring user relationships. The configuration service includes an application running on the terminal device or a subroutine embedded in the application.

[0153] Specifically, a second user node is determined in the user relationship network based on the user account, and a connection relationship is established between the first user node and the second user node based on the positive relationship label, and the positive relationship label and user feature data are associated with the connection relationship.

[0154] For example, a second user node of the second user is constructed in the user relationship network based on the user account, and a connection relationship is established from the first user node of the first user to the second user node based on the positive relationship label "husband". The positive relationship label "husband" and the user feature data of the second user are associated with the connection relationship.

[0155] Furthermore, the above-described process of updating user feature data and positive feature tags to the user relationship network can be replaced by determining the second user node in the user relationship network based on the second user's user identifier, establishing a connection relationship between the first user node and the second user node in the user relationship network based on the positive relationship tags, associating the positive relationship tags and the user feature data of the second user with the connection relationship, and forming a new implementation method with other processing steps provided in this embodiment.

[0156] In practical applications, the first user can edit, delete, or add user relationship data during the management process, thereby improving the flexibility of user relationship data management. The user relationship data refers to the first user's own user relationship data, which records users who are related to the first user and the relationship types of direct relationships. For example, the user relationship data records a second user who is related to the first user, and the relationship type of the relationship is kinship.

[0157] In one optional implementation of this embodiment, after determining the second user node based on the user account, establishing a connection between the first user node and the second user node, and associating the positive relationship label and user feature data with the connection relationship, and updating the user feature data and positive relationship label to the user relationship network upon detecting a label confirmation instruction, the following operation is further performed:

[0158] Detect the deletion command submitted by the first user in response to the second user;

[0159] The connection relationship is terminated in the user relationship network, and the second user node is deleted.

[0160] Furthermore, the process of detecting the deletion command submitted by the first user to the second user, terminating the connection in the user relationship network, and deleting the second user node can be replaced by rolling back the update of user feature data and positive relationship tags to the user relationship network, and forming a new implementation method with other processing steps provided in this embodiment; wherein, the rollback process includes: detecting the deletion command submitted by the first user to the second user; terminating the connection in the user relationship network, and deleting the second user node.

[0161] In the specific execution process, in order to improve the comprehensiveness of the user relationship network and thus improve the search efficiency of users when searching for user relationships in specific scenarios, the feature data of users in the user relationship network can be updated. In an optional implementation method provided in this embodiment, the user feature data in the user relationship network is updated in the following way: the service registration information of the second user in the target service is updated according to the user feature data.

[0162] And / or,

[0163] Based on the user characteristic data, the user characteristic data configured by the third user for the second user in the user relationship network is updated.

[0164] The service registration information refers to the registration information used to register for the target service, such as the contact information and identity credentials of the second user. The third user refers to the remaining users in the user relationship network besides the first and second users.

[0165] Specifically, based on the user characteristic data submitted by the first user to the second user in the user relationship network, the service registration information of the second user in the target service is updated or supplemented; and / or, based on the user characteristic data submitted by the first user to the second user in the user relationship network, the user characteristic data configured by the third user to the second user in the user relationship network is updated or supplemented.

[0166] In practical applications, target users often need to manually input user characteristic data, such as name and phone number, during the service registration process. Service registration based solely on this input data leads to low efficiency and presents registration barriers for certain users, such as elderly users who may have operational difficulties and be unable to input their user characteristic data, resulting in registration failure. To address this, and to improve the efficiency and success rate of service registration, facilitating service registration for all types of users, service registration can be performed based on user characteristic data retrieved from a user relationship network. In one optional implementation of this embodiment, service registration is performed on target users in the following manner:

[0167] Based on the service registration instruction submitted by the accessing user, read the user characteristic data of the accessing user from the user relationship network;

[0168] Service registration is performed on the accessing user based on the read user characteristic data.

[0169] The user who can access the service can be any user corresponding to any user node in the user relationship network.

[0170] The following description uses the application of a user relationship-based recommendation processing method provided in this embodiment in a service processing scenario as an example to further illustrate the user relationship processing method provided in this embodiment. (See also...) Figure 5 The recommendation processing method based on user relationships, applied to service processing scenarios, specifically includes the following steps.

[0171] Step S502: Obtain the search request from the accessing user to perform a user relationship search on the target service.

[0172] Step S504: If the search request type is an association request type, extract the first relationship data that has a direct association with the accessing user from the user relationship network.

[0173] Step S506: Recommend first relationship data and second relationship data that have an indirect relationship with the accessing user to the accessing user.

[0174] Step S508: Determine the selected user among the accessing users in the first relational data and the second relational data.

[0175] Step S510: Perform the corresponding operation processing on the target service based on the selected user.

[0176] This specification provides an embodiment of a user relationship processing device as follows:

[0177] In the above embodiments, a user relationship processing method is provided, and correspondingly, a user relationship processing apparatus is also provided, which will be described below with reference to the accompanying drawings.

[0178] Reference Figure 6 The diagram shows a user relationship processing device provided in this embodiment.

[0179] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0180] This embodiment provides a user relationship processing device, including:

[0181] The data acquisition module 602 is configured to acquire user feature data submitted by the first user for configuring user relationships with the second user;

[0182] The tag query module 604 is configured to query in the user relationship network whether there is a reverse relationship tag configured by the second user for the first user;

[0183] The tag push module 606 is configured to generate a positive relationship tag corresponding to the reverse relationship tag and push it to the first user if the reverse relationship tag exists.

[0184] The network update module 608 is configured to update the user feature data and the positive relationship label to the user relationship network upon detecting a label confirmation instruction.

[0185] The following is an embodiment of a user relationship-based recommendation processing device provided in this specification:

[0186] In the above embodiments, a recommendation processing method based on user relationships is provided, and correspondingly, a recommendation processing device based on user relationships is also provided, which will be described below with reference to the accompanying drawings.

[0187] Reference Figure 7 The diagram illustrates a user relationship-based recommendation processing device provided in this embodiment.

[0188] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0189] This embodiment provides a recommendation processing device based on user relationships, including:

[0190] The request retrieval module 702 is configured to retrieve search requests from users performing user relationship searches on the target service;

[0191] The data extraction module 704 is configured to extract first relationship data that has a direct relationship with the accessing user from the user relationship network if the request type of the search request is an association request type;

[0192] The data recommendation module 706 is configured to recommend the first relationship data and the second relationship data that has an indirect relationship with the accessing user to the accessing user; the second relationship data is obtained after performing relationship prediction based on the user relationship network.

[0193] The user relationship network is updated based on the user feature data submitted by the first user for user relationship configuration of the second user and the reverse relationship tags configured by the second user for the first user.

[0194] This specification provides an example of a user relationship processing device as follows:

[0195] Corresponding to the user relationship processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a user relationship processing device, which is used to execute the user relationship processing method provided above. Figure 8 This is a schematic diagram of the structure of a user relationship processing device provided for one or more embodiments of this specification.

[0196] This embodiment provides a user relationship processing device, including:

[0197] like Figure 8 As shown, user relationship processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and memory 802, with memory 802 storing one or more application programs or data. Memory 802 can be temporary or persistent storage. The application programs stored in memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions from the user relationship processing device. Furthermore, processor 801 may be configured to communicate with memory 802, executing the series of computer-executable instructions in memory 802 on the user relationship processing device. The user relationship processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0198] In one specific embodiment, the user relationship processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the user relationship processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0199] Obtain user characteristic data submitted by the first user for configuring user relationships with the second user;

[0200] In the user relationship network, query whether the reverse relationship label configured by the second user for the first user exists;

[0201] If it exists, generate the positive relationship label corresponding to the reverse relationship label and push it to the first user;

[0202] Upon detecting a tag confirmation instruction, the user feature data and the positive relationship tag are updated to the user relationship network.

[0203] This specification provides an example of a user relationship-based recommendation processing device as follows:

[0204] Corresponding to the user relationship-based recommendation processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide a user relationship-based recommendation processing device, which is used to execute the user relationship-based recommendation processing method provided above. Figure 9 This is a schematic diagram of a user relationship-based recommendation processing device provided for one or more embodiments of this specification.

[0205] This embodiment provides a recommendation processing device based on user relationships, comprising:

[0206] like Figure 9As shown, the user-relationship-based recommendation processing device can vary significantly due to differences in configuration or performance. It may include one or more processors 901 and a memory 902, where one or more application programs or data may be stored. The memory 902 can be temporary or persistent storage. The application programs stored in the memory 902 may include one or more modules (not shown), each module including a series of computer-executable instructions from the user-relationship-based recommendation processing device. Furthermore, the processor 901 may be configured to communicate with the memory 902 and execute the series of computer-executable instructions in the memory 902 on the user-relationship-based recommendation processing device. The user-relationship-based recommendation processing device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, etc.

[0207] In one specific embodiment, the user-relationship-based recommendation processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the user-relationship-based recommendation processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0208] Retrieve search requests from users who are searching for user relationships within the target service;

[0209] If the search request is a related request type, extract the first relationship data that has a direct relationship with the accessing user from the user relationship network;

[0210] The system recommends the first relationship data and the second relationship data that has an indirect relationship with the user to the accessing user; the second relationship data is obtained after performing relationship prediction based on the user relationship network.

[0211] The user relationship network is updated based on the user feature data submitted by the first user for user relationship configuration of the second user and the reverse relationship tags configured by the second user for the first user.

[0212] This specification provides an example of a storage medium as follows:

[0213] Corresponding to the user relationship processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0214] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0215] Obtain user characteristic data submitted by the first user for configuring user relationships with the second user;

[0216] In the user relationship network, query whether the reverse relationship label configured by the second user for the first user exists;

[0217] If it exists, generate the positive relationship label corresponding to the reverse relationship label and push it to the first user;

[0218] Upon detecting a tag confirmation instruction, the user feature data and the positive relationship tag are updated to the user relationship network.

[0219] It should be noted that the embodiments of a storage medium described in this specification and the embodiments of a user relationship processing method described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0220] Another embodiment of the storage medium provided in this specification is as follows:

[0221] Corresponding to the user relationship-based recommendation processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide another storage medium.

[0222] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0223] Retrieve search requests from users who are searching for user relationships within the target service;

[0224] If the search request is a related request type, extract the first relationship data that has a direct relationship with the accessing user from the user relationship network;

[0225] The system recommends the first relationship data and the second relationship data that has an indirect relationship with the user to the accessing user; the second relationship data is obtained after performing relationship prediction based on the user relationship network.

[0226] The user relationship network is updated based on the user feature data submitted by the first user for user relationship configuration for the second user and the reverse relationship tags configured by the second user for the first user.

[0227] It should be noted that the embodiment of another storage medium in this specification and the embodiment of a recommendation processing method based on user relationships in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0228] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0229] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0230] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0231] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0232] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0233] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0234] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0235] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0236] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0237] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0238] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0239] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0240] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0241] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0242] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0243] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A user relationship processing method, comprising: Obtain user characteristic data submitted by the first user for configuring user relationships with the second user; In the user relationship network, query whether the reverse relationship label configured by the second user for the first user exists; The reverse relationship tags record user relationships; The user relationship network is a network that represents the user relationship between every two users; If it exists, generate the positive relationship label corresponding to the reverse relationship label and push it to the first user; Upon detecting a tag confirmation instruction, a second user node is determined in the user relationship network based on the user account queried based on the user feature data. A connection relationship is established between the first user node and the second user node of the first user in the user relationship network based on the positive relationship tag. The positive relationship tag and the user feature data are associated with the connection relationship.

2. The user relationship processing method according to claim 1 further includes: Based on the search request submitted by the user to perform a user relationship search, the system recommends first relationship data that has a direct relationship with the user and second relationship data that has an indirect relationship with the user to the user. The first relationship data is extracted from the user relationship network, and the second relationship data is obtained after predicting the association relationship based on the user relationship network.

3. The user relationship processing method according to claim 1 further includes: Based on the service registration instruction submitted by the accessing user, read the user characteristic data of the accessing user from the user relationship network; Service registration is performed on the accessing user based on the read user characteristic data.

4. The user relationship processing method according to claim 1, further comprising, after the steps of determining a second user node in the user relationship network based on the user account queried based on the user feature data when a tag confirmation instruction is detected, establishing a connection relationship between the first user node and the second user node of the first user in the user relationship network based on the positive relationship tag, and associating the positive relationship tag and the user feature data with the connection relationship, the method further comprises: Based on the user characteristic data, update the service registration information of the second user in the target service; And / or, Based on the user characteristic data, the user characteristic data configured by the third user for the second user in the user relationship network is updated.

5. The user relationship processing method according to claim 1, further comprising, after the steps of determining a second user node in the user relationship network based on the user account queried based on the user feature data when a tag confirmation instruction is detected, establishing a connection relationship between the first user node and the second user node of the first user in the user relationship network based on the positive relationship tag, and associating the positive relationship tag and the user feature data with the connection relationship, the method further comprises: Detect the deletion command submitted by the first user in response to the second user; The connection relationship is terminated in the user relationship network, and the second user node is deleted.

6. The user relationship processing method according to claim 1, if the execution result after the step of querying whether the reverse relationship label configured by the second user for the first user exists in the user relationship network is that it does not exist, the following operation is performed: Obtain the relationship tags configured by the first user for the second user; Update the user feature data and the relationship tags to the user relationship network.

7. The user relationship processing method according to claim 1, wherein the user feature data is obtained in the following manner: Based on the first user's trigger command for the configuration entry, display the configuration template of the user relationship configuration to the first user; Collect the user feature data entered by the first user through the configuration template.

8. The user relationship processing method according to claim 2, after the step of recommending first relationship data that has a direct relationship with the user and second relationship data that has an indirect relationship with the user to the user based on the search request submitted by the user for user relationship search, it further includes: Determine the selected user chosen by the accessing user from the first relation data and the second relation data; Based on the selected user, the corresponding operation process is executed.

9. The user relationship processing method according to claim 2, wherein the association relationship prediction includes: Read from the user relationship network the first relationship label configured by the accessing user and the first direct user for each other, and the second relationship label configured by the first direct user and the second direct user for each other. Based on the first relationship tag and the second relationship tag, predict the third relationship tag of the accessing user for the second direct user.

10. A recommendation processing method based on user relationships, comprising: Retrieve search requests from users who are searching for user relationships within the target service; If the search request is a related request type, extract the first relationship data that has a direct relationship with the accessing user from the user relationship network; Recommend the first relationship data and the second relationship data that has an indirect association with the accessing user to the accessing user; The second relationship data is obtained by prediction based on the first relationship tags configured by the accessing user and the first direct user to each other, and the second relationship tags configured by the first direct user and the second direct user to each other, which are read from the user relationship network. The second relationship data includes the third relationship tag of the accessing user to the second direct user. The user relationship network is updated based on user feature data submitted by the first user for user relationship configuration of the second user and the reverse relationship label configured by the second user for the first user; the reverse relationship label records the user relationship; the user relationship network is a network representing the user relationship between every two users.

11. The recommendation processing method based on user relationships according to claim 10, further comprising: Determine the selected user chosen by the accessing user from the first relation data and the second relation data; Based on the selected user, the corresponding operation is performed on the target service.

12. The recommendation processing method based on user relationships according to claim 10, further comprising: If the search request is of a preset request type, the first relationship data is extracted from the user relationship network and recommended to the accessing user.

13. The recommendation processing method based on user relationships according to claim 10, wherein the user relationship network is updated in the following manner: Based on the user feature data submitted by the first user for configuring user relationships with the second user, query the reverse relationship tags configured by the second user for the first user in the user relationship network; Generate the positive relationship tags corresponding to the queried reverse relationship tags and push them to the first user; Upon detecting a tag confirmation instruction, the user feature data and the positive relationship tag are updated to the user relationship network.

14. A user relationship processing apparatus, comprising: The data acquisition module is configured to acquire user feature data submitted by the first user for configuring user relationships with the second user; The tag query module is configured to query the user relationship network to see if there is a reverse relationship tag configured by the second user for the first user. The reverse relationship label records user relationships; the user relationship network is a network representing the user relationship between every two users. The tag push module is configured to generate a positive relationship tag corresponding to the reverse relationship tag and push it to the first user if the tag exists. The network update module is configured to, upon detecting a tag confirmation instruction, determine a second user node in the user relationship network based on the user account queried based on the user feature data, establish a connection relationship between the first user node and the second user node in the user relationship network based on the positive relationship tag, and associate the positive relationship tag and the user feature data with the connection relationship.

15. A recommendation processing apparatus based on user relationships, comprising: The request retrieval module is configured to retrieve search requests from users performing user relationship searches on the target service; The data extraction module is configured to extract first relationship data that has a direct relationship with the accessing user from the user relationship network if the search request is an association request type. The data recommendation module is configured to recommend the first relationship data and the second relationship data that has an indirect association with the accessing user to the accessing user; The second relationship data is obtained by prediction based on the first relationship tags configured by the accessing user and the first direct user to each other, and the second relationship tags configured by the first direct user and the second direct user to each other, which are read from the user relationship network. The second relationship data includes the third relationship tag of the accessing user to the second direct user. The user relationship network is updated based on user feature data submitted by the first user for user relationship configuration of the second user and the reverse relationship label configured by the second user for the first user; the reverse relationship label records the user relationship; the user relationship network is a network representing the user relationship between every two users.

16. A user relationship processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain user characteristic data submitted by the first user for configuring user relationships with the second user; In the user relationship network, query whether the reverse relationship label configured by the second user for the first user exists; The reverse relationship tags record user relationships; The user relationship network is a network that represents the user relationship between every two users; If it exists, generate the positive relationship label corresponding to the reverse relationship label and push it to the first user; Upon detecting a tag confirmation instruction, a second user node is determined in the user relationship network based on the user account queried based on the user feature data. A connection relationship is established between the first user node and the second user node of the first user in the user relationship network based on the positive relationship tag. The positive relationship tag and the user feature data are associated with the connection relationship.

17. A recommendation processing device based on user relationships, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Retrieve search requests from users who are searching for user relationships within the target service; If the search request is a related request type, extract the first relationship data that has a direct relationship with the accessing user from the user relationship network; Recommend the first relationship data and the second relationship data that has an indirect association with the accessing user to the accessing user; The second relationship data is obtained by prediction based on the first relationship tags configured by the accessing user and the first direct user to each other, and the second relationship tags configured by the first direct user and the second direct user to each other, which are read from the user relationship network. The second relationship data includes the third relationship tag of the accessing user to the second direct user. The user relationship network is updated based on user feature data submitted by the first user for user relationship configuration of the second user and the reverse relationship label configured by the second user for the first user; the reverse relationship label records the user relationship; the user relationship network is a network representing the user relationship between every two users.

18. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Obtain user characteristic data submitted by the first user for configuring user relationships with the second user; In the user relationship network, query whether the reverse relationship label configured by the second user for the first user exists; The reverse relationship tags record user relationships; The user relationship network is a network that represents the user relationship between every two users; If it exists, generate the positive relationship label corresponding to the reverse relationship label and push it to the first user; Upon detecting a tag confirmation instruction, a second user node is determined in the user relationship network based on the user account queried based on the user feature data. A connection relationship is established between the first user node and the second user node of the first user in the user relationship network based on the positive relationship tag. The positive relationship tag and the user feature data are associated with the connection relationship.

19. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Retrieve search requests from users who are searching for user relationships within the target service; If the search request is a related request type, extract the first relationship data that has a direct relationship with the accessing user from the user relationship network; Recommend the first relationship data and the second relationship data that has an indirect association with the accessing user to the accessing user; The second relationship data is obtained by prediction based on the first relationship tags configured by the accessing user and the first direct user to each other, and the second relationship tags configured by the first direct user and the second direct user to each other, which are read from the user relationship network. The second relationship data includes the third relationship tag of the accessing user to the second direct user. The user relationship network is updated based on user feature data submitted by the first user for user relationship configuration of the second user and the reverse relationship label configured by the second user for the first user; the reverse relationship label records the user relationship; the user relationship network is a network representing the user relationship between every two users.

Images