Social relationship processing method and apparatus

Abstract

The embodiment of the present specification provides a social relationship processing method and device, wherein a social relationship processing method comprises: acquiring an access request of a user in a target service for social relationship access sent by a user terminal; in response to the access request, reading predicted social relationship data of the user and returning to the user terminal; generating a social relationship factor of the user and a social user corresponding to the relationship type of the predicted social relationship of the social user according to the selection instruction; and establishing a trusted social relationship between the user and the social user based on the social relationship factor.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a method and apparatus for processing social relationships. 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. Users' social activities are no longer limited to face-to-face communication. Users engage in diverse social behaviors through online services, thereby generating social relationships between different users. How to better manage the social relationships between different users has gradually become a research hotspot. Summary of the Invention

[0003] This specification provides one or more embodiments of a social relationship processing method, comprising: acquiring an access request sent by a user terminal indicating that a user is accessing social relationships on a target service; responding to the access request by reading the user's predicted social relationship data and returning it to the user terminal; generating a social relationship factor between the user and the social user based on the relationship type of the predicted social relationship between the user and the social user corresponding to the selection instruction; and establishing a trusted social relationship between the user and the social user based on the social relationship factor.

[0004] This specification provides one or more embodiments of a service processing method, comprising: generating an access request and sending it to a server based on an access instruction from a user to access social relationships in a target service; receiving predicted social relationship data of the user returned by the server; generating a selection instruction and submitting it to the server based on a social user selected by the user based on the predicted social relationship data; and performing service processing for the access service based on a trusted social relationship determined by social relationship factors between the user and the social user; wherein the social relationship factors are generated after the selection instruction is submitted, according to the relationship type of the predicted social relationship between the social user and the user.

[0005] This specification provides one or more embodiments of a social relationship processing apparatus, including: an access request acquisition module configured to acquire an access request sent by a user terminal indicating that a user is accessing social relationships on a target service; a relationship data reading module configured to, in response to the access request, read the user's predicted social relationship data and return it to the user terminal; a relationship factor generation module configured to generate a social relationship factor between the user and the social user corresponding to a selection instruction, based on the relationship type of the predicted social relationship between the user and the social user; and a social relationship establishment module configured to establish a trusted social relationship between the user and the social user based on the social relationship factor.

[0006] This specification provides one or more embodiments of a service processing apparatus, comprising: an access request sending module configured to generate an access request and send it to a server based on an access instruction from a user to access social relationships in a target service; a relationship data receiving module configured to receive predicted social relationship data of the user returned by the server; a selection instruction submission module configured to generate a selection instruction and submit it to the server based on a social user selected by the user based on the predicted social relationship data; and a service processing module configured to perform service processing for the access service based on a trusted social relationship determined by a social relationship factor between the user and the social user; wherein the social relationship factor is generated after the selection instruction is submitted, according to the relationship type of the predicted social relationship between the social user and the user.

[0007] This specification provides one or more embodiments of a social relationship processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire an access request sent by a user terminal indicating that a user is accessing social relationships on a target service; in response to the access request, read predicted social relationship data of the user and return it to the user terminal; generate a social relationship factor between the user and the social user based on the relationship type of the predicted social relationship between the user and the social user corresponding to the selection instruction; and establish a trusted social relationship between the user and the social user based on the social relationship factor.

[0008] This specification provides one or more embodiments of a service processing apparatus, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: generate an access request and send it to a server based on an access instruction from a user to access social relationships in a target service; receive predicted social relationship data of the user returned by the server; generate a selection instruction and submit it to the server based on a social user selected by the user based on the predicted social relationship data; and perform service processing for the access service based on a trusted social relationship determined by social relationship factors between the user and the social user; wherein the social relationship factors are generated after the selection instruction is submitted, based on the relationship type of the predicted social relationship between the social user and the 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: acquiring an access request sent by a user terminal indicating that a user is accessing social relationships on a target service; responding to the access request, reading the user's predicted social relationship data and returning it to the user terminal; generating a social relationship factor between the user and the social user corresponding to the selection instruction, based on the relationship type of the predicted social relationship between the user and the social user; and establishing a trusted social relationship between the user and the social user based on the social relationship factor.

[0010] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: Based on a user's access instruction to access social relationships in a target service, generate an access request and send it to a server. Receive predicted social relationship data of the user returned by the server. Based on the social users selected by the user based on the predicted social relationship data, generate a selection instruction and submit it to the server. Perform service processing for the access service based on the trusted social relationship determined by the social relationship factors between the user and the social users; the social relationship factors are generated after the selection instruction is submitted, based on the relationship type of the predicted social relationship between the social users and the 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 social relationship processing method provided in one or more embodiments of this specification;

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

[0014] Figure 3 A schematic diagram of a trusted social relationship network provided for one or more embodiments of this specification;

[0015] Figure 4 A timing diagram illustrating a social relationship processing method applied to a service processing scenario, provided in one or more embodiments of this specification.

[0016] Figure 5A flowchart illustrating a social relationship processing method applied in a trusted social scenario, provided for one or more embodiments of this specification;

[0017] Figure 6 A service processing method flowchart provided for one or more embodiments of this specification;

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

[0019] Figure 8 A schematic diagram of a service processing apparatus provided for one or more embodiments of this specification;

[0020] Figure 9 A schematic diagram of the structure of a social relationship processing device provided for one or more embodiments of this specification;

[0021] Figure 10 This is a schematic diagram of the structure of a service processing device provided for one or more embodiments of this specification. Detailed Implementation

[0022] 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.

[0023] This specification provides an example of a social relationship processing method:

[0024] In practical applications, social relationship sets are often generated based on the social relationship types obtained by tagging social users with social relationship types collected from the data. When users access social relationships in the target service, the social relationship set can be read and displayed to the user. However, the social relationship type tagging method is relatively cumbersome, resulting in low efficiency in generating social relationship sets.

[0025] To address this, the social relationship processing method provided in this embodiment establishes a trustworthy social relationship between the user and a social user selected based on predicted social relationship data during the user's access to social relationships on the target service. Specifically, during the user's access to social relationships on the target service, the user's predicted social relationship data is returned to the user, and a social relationship factor between the user and the social user corresponding to the submitted selection instruction is generated based on the predicted social relationship type. A trustworthy social relationship between the user and the social user is then established based on the social relationship factor. This achieves the transformation of the user's predicted social relationship with the social user into a trustworthy social relationship, improving the effectiveness and reliability of the trustworthy social relationship. Furthermore, by performing the transformation from predicted social relationship to trustworthy social relationship during the access to social relationships on the target service, the efficiency and convenience of social relationship transformation are improved.

[0026] Reference Figure 1 The social relationship processing method provided in this embodiment specifically includes steps S102 to S108.

[0027] Step S102: Obtain the access request sent by the user terminal for the user to access social relationships in the target service.

[0028] The target service described in this embodiment refers to a service in which a user has a need to access social relationships during the process of accessing the target service. For example, if the target service is a money transfer service, user u1 needs to identify the transfer user during the process of accessing the money transfer service, which means there is a need to query or search for social users. Or, if the target service is an auxiliary payment service, user u1 needs to identify the auxiliary user during the process of accessing the auxiliary payment service, which means there is a need to query or search for social users. In addition, the target service also includes other types of services. Other services with access needs for social relationships are also within the scope of protection of this solution, which will not be listed here.

[0029] In practical applications, users may have access needs for social relationship access when accessing a target service. For example, in a money transfer service, user u1 may determine that they want to transfer money to social user s1 and can search or query social user s1. This search or query for social users constitutes social relationship access. Optionally, social relationship access includes accessing social user data that has a social relationship with the user and / or accessing social relationship data between the user and social users. The user includes users who have access needs for social relationship access, and the user terminal refers to the terminal device to which the user belongs. The social users include users who have a social relationship with the user. The social user data includes a set of social users or a list of social users, and the social relationship data includes a set of social relationships or a list of social relationships.

[0030] In this embodiment, social relationships refer to relationships involving social behavior or data interaction, such as kinship, friendship, colleague relationships, resource trading relationships, or friendship relationships through instant messaging applications.

[0031] In practice, when a user accesses a target service, they submit an access command to access social relationships, generating an access request. The server then receives the access request sent by the user's terminal.

[0032] Step S104: Read the user's predicted social relationship data and return it to the user's terminal.

[0033] The above-mentioned step of obtaining the user's access request for social relationship access in the target service involves reading the user's predicted social relationship data and returning it to the user terminal. Specifically, this step reads the user's predicted social relationship data and returns it to the user terminal in response to the access request for social relationship access.

[0034] In this embodiment, predicted social relationships refer to social relationships obtained through prediction. Optionally, the relationship type of the predicted social relationship is obtained based on the interaction behavior data between the user and the social user and / or their respective feature data. The relationship type refers to the category of the predicted social relationship between the user and the social user. The interaction behavior data refers to the data generated by the interaction behavior between the user and the social user. Optionally, the interaction behavior data is obtained from one or more of the access services. The access services include target services and / or authorized services. The authorized services refer to services other than the target service. For example, the interaction behavior data is the interaction data generated by transferring money to a friend in a dining scenario, the interaction data generated by helping a family member pick up a package, or the interaction data generated by giving a gift to a partner on a holiday. The feature data includes identity feature data, such as the length of time from birth to the time of calculation.

[0035] Optionally, the predicted social relationship type includes relationship attributes and / or relationship features; the relationship attributes include a first relationship attribute or a second relationship attribute, such as the first relationship attribute being a predicted relationship attribute and the second relationship attribute being a reliable relationship attribute; the relationship features include key feature levels and / or key feature parameters, where each key feature level can correspond to one or more key feature parameters, such as a first level where the key feature parameter corresponding to the first level is a relative or friend, or a second level where the key feature parameter corresponding to the second level is a father or mother.

[0036] The predicted social relationship data described in this embodiment includes a set or list of predicted social relationships consisting of predicted social relationships between one or more users and social users. In one optional implementation of this embodiment, based on the relationship types in a user's predicted social relationship records, the predicted social relationships extracted from the corresponding user's predicted social relationship records are tagged by type, and the predicted social relationship data is constructed based on the tagging results. Specifically, the predicted social relationship data is constructed in the following manner:

[0037] Read the user's predicted relationship records from the predicted social relationship database, and extract the predicted social relationships from the predicted relationship records;

[0038] Based on the relationship types in the predicted relationship records, the corresponding predicted social relationships are tagged, and the predicted social relationship data is constructed based on the tagging results.

[0039] The predicted social relationship database refers to a database or a data table (i.e., a predicted social relationship table) that stores predicted social relationships between users and social users. The database can store multiple predicted relationship records between users and their corresponding social users. Each predicted relationship record includes the user's identifier, the social user's identifier, the relationship type of the predicted social relationship between the user and the social user, and / or the relationship status of the predicted social relationship between the user and the social user. For example, the predicted social relationship database shown in Table 1 below:

[0040] 100001 100002 predict Level 1 relatives invalid 100005 100006 predict Level 2 Mother efficient

[0041] Table 1

[0042] Referring to Table 1, the predicted relationship records of user u1 (100001) are read from the predicted social relationship database. The predicted social relationships "100001, 100002" are extracted from the predicted social relationship records. The predicted social relationships are tagged with the relationship types "predicted, first level, relatives" in the predicted relationship records. The predicted social relationship list "100001, 100002, predicted, first level, relatives" is constructed based on the tagging results.

[0043] The aforementioned predicted social relationship data of users is constructed based on the predicted relationship records of users read from the predicted social relationship database. In addition, the predicted social relationship data of users can also be constructed based on the predicted relationship records of users extracted from the predicted social relationship network. The predicted social relationship network may include the predicted relationship records of users with predicted social relationships and social users, that is, it includes the predicted relationship records of all users.

[0044] Specifically, the predicted social relationship network is constructed as follows: predictive relationship nodes are determined based on the user identifiers of the first user and the second user, and a bidirectional predictive connection between the first user and the second user is established based on the relationship feature parameters between the first user and the second user. The relationship status of the predicted social relationship between the first user and the second user is associated with the bidirectional predictive connection to obtain the predicted social relationship network.

[0045] The bidirectional predictive connection refers to the predicted bidirectional connection between the first user and the second user, which may not be real. The process of determining the predictive relationship node based on the user identifier of the first user and the user identifier of the second user can be implemented by determining the first predictive relationship node based on the user identifier of the first user and the second predictive relationship node based on the user identifier of the second user. The process of establishing the bidirectional predictive connection between the first user and the second user based on the relationship feature parameters of the first user and the second user can be implemented by establishing the first directed predictive connection between the first user and the second user based on the relationship feature parameters of the first user and the second user, and establishing the second directed predictive connection between the second user and the first user based on the relationship feature parameters of the second user and the first user, and using the first directed predictive connection and the second directed predictive connection as the bidirectional predictive connection.

[0046] like Figure 2The predicted social relationship network shown has three predicted relationship nodes: user u1, user u2, and user u3. These three nodes establish bidirectional predicted connections based on their respective relationship feature parameters. The relationship feature parameter between user u1 and user u2 is "husband," so a first directed predicted connection from user u1 to user u2 is established based on this parameter. The relationship feature parameter between user u2 and user u1 is "wife," so a second directed predicted connection from user u2 to user u1 is established based on this parameter. The process of establishing connections between other predicted relationship nodes is similar to the process of establishing a connection between user u1 and user u2, and will not be described in detail here.

[0047] Step S106: Generate a social relationship factor between the user and the social user based on the predicted social relationship type between the user and the social user corresponding to the selection instruction.

[0048] The above-mentioned reading of the user's predicted social relationship data is returned to the user terminal. Correspondingly, the user terminal receives the user's predicted social relationship data returned by the server, and generates a selection instruction based on the social user selected by the user based on the predicted social relationship data and submits it to the server. In this step, the social relationship factor between the user and the social user corresponding to the submitted selection instruction is generated according to the relationship type of the predicted social relationship between the user and the social user.

[0049] The social relationship factors mentioned in this embodiment refer to the social relationship factors required to establish a trustworthy social relationship between a user and a social user. Optionally, the social relationship factors include relationship attributes, relationship features, user identifier, social user identifier, relationship creation event and / or relationship modification time. The relationship features include key feature levels and / or key feature parameters. For example, the social relationship factors are "user identifier, social user identifier, trustworthy, first level, mother".

[0050] Optionally, the predicted social relationship type is obtained based on the interaction behavior data between the user and the social user and / or their respective feature data. In one optional implementation of this embodiment, social relationship prediction is performed in the following manner:

[0051] Based on the interaction behavior data and the feature data, calculate the predicted probability of the candidate relationship type;

[0052] The relationship type is determined from the candidate relationship types based on the probability calculation results.

[0053] The interactive behavior data refers to the interactive data generated by users interacting with social users on various access services. Optionally, the interactive behavior data is obtained from one or more of the access services, which include target services and / or authorized services. The authorized services refer to services other than the target service. For example, the interactive behavior data is the interactive data generated by a user transferring money to a friend in a dining scenario, the interactive data generated by a user helping a family member pick up a package, or the interactive data generated by a user giving a gift to their partner on a holiday. The feature data includes identity feature data, such as the length of time from birth to the time of calculation, and whether the user is male or female.

[0054] Specifically, based on interaction behavior data and feature data, the predicted probability of each relationship type in the candidate relationship types is calculated, and the relationship types whose predicted probabilities meet the probability conditions are selected from the candidate relationship types. Optionally, the probability conditions include the predicted probability being a preset probability threshold or the predicted probability ranking being at a preset position. The predicted probability ranking refers to the sorting order of the predicted probabilities. For example, the probability condition is that the predicted probability is >a%, or the probability condition is that the predicted probability ranking is first. It should be noted that if the probability condition is that the predicted probability is >a%, the predicted social relationship type between the user and the social user can be one or more. If the probability condition is that the predicted probability ranking is first, the predicted social relationship type between the user and the social user can be one.

[0055] In practical applications, to improve the effectiveness and accuracy of social relationship factors between users and social users, and to facilitate the establishment of trustworthy social relationships and improve the efficiency of establishing trustworthy social relationships, it is possible to further detect the user's confirmation instruction regarding the predicted social relationship type of the social user corresponding to the submitted selection instruction. Based on this, social relationship factors are generated. In one optional implementation of this embodiment, the following operations are performed during the process of generating social relationship factors between users and social users based on the predicted social relationship type of the user and the social user corresponding to the submitted selection instruction:

[0056] If a confirmation instruction submitted by the user for the confirmation reminder of the relationship type is detected, a reliable relationship attribute is determined based on the predicted relationship attribute in the relationship type;

[0057] The social relationship factor is generated based on the trusted relationship attribute and the relationship features in the relationship type.

[0058] The confirmation reminder refers to a reminder message that confirms the relationship type between the user and the social user. For example, if the relationship type between the user and the social user is "predicted, first level, mother", the confirmation reminder would be "Is the social user your mother?".

[0059] For example, the predicted social relationship type between user u1 and a social user is "predicted, first level, mother", and the confirmation prompt is "Is the social user your mother?". If a confirmation instruction submitted by user u1 in response to the confirmation prompt "Is the social user your mother?" is detected, it means that user u1 acknowledges the predicted social relationship type with the social user. Based on the predicted relationship attribute "predicted" in the relationship type, the trustworthy relationship attribute is determined to be "trustworthy". Based on the trustworthy relationship attribute "trustworthy" and the relationship feature "first level, mother" in the predicted social relationship type, the social relationship factor "user identifier, social user identifier, trustworthy, first level, mother" is constructed.

[0060] Furthermore, the execution operation in the process of generating a social relationship factor between a user and a social user based on the predicted social relationship type between the user and the social user corresponding to the selection instruction can be replaced by determining a second relationship type between the user and the social user based on the instruction information and relationship type submitted by the user in response to the confirmation reminder for the relationship type, and using the second relationship type as the social relationship factor.

[0061] The process of determining the second relationship type between the user and the social user based on the instruction information and relationship type submitted by the user in response to the confirmation reminder for the relationship type, and using the second relationship type as the social relationship factor, can be implemented as follows: If the instruction information is a confirmation instruction, a reliable relationship attribute is determined based on the predicted relationship attribute in the relationship type corresponding to the confirmation reminder; the reliable relationship attribute and the relationship feature in the relationship type are used as the social relationship factor; if the instruction information is an objection instruction, a reliable relationship type is determined based on the relationship feature in the relationship type corresponding to the confirmation reminder in the set of predicted social relationship types between the user and the social user, and the second relationship type is used as the social relationship factor.

[0062] Specifically, the second relationship type is determined from the set of predicted social relationship types between the user and the social user based on the relationship features in the relationship type corresponding to the confirmation reminder. This can be achieved by filtering out candidate relationship types other than the relationship features from the set of predicted social relationship types between the user and the social user, and determining the second relationship type as a social relationship factor from the candidate relationship types based on the predicted probability of the candidate relationship types.

[0063] Step S108: Establish a trusted social relationship between the user and the social user based on the social relationship factor.

[0064] The above-mentioned social relationship factor between the user and the social user corresponding to the submitted selection instruction is generated based on the predicted social relationship type. In this step, a reliable social relationship between the user and the social user is established based on the social relationship factor. In this way, the reliable social relationship helps to improve the user's access efficiency in accessing the service. The reliable social relationship refers to the reliable social relationship between the user and the social user.

[0065] In one optional implementation of this embodiment, a trusted social relationship between the user and the social user is established based on the social relationship factor in the following manner:

[0066] Based on the social relationship factor, the relationship status of the trusted social relationship between the user and the social user is marked as a valid status;

[0067] Based on the social relationship factors and the effective status, a trusted relationship record between the user and the social user is created and the trusted social relationship database is updated.

[0068] Optionally, the relationship status includes a valid status and / or an invalid status; the trusted relationship record records the social relationship factors and / or relationship status between the user and the social user. Furthermore, the trusted relationship record may also record the user identifier, social user identifier, relationship creation time, and / or relationship modification time; the trusted social relationship database refers to a database that stores trusted social relationships between users and social users. The trusted social relationship database can store trusted relationship records between multiple users and their corresponding social users; for example, the trusted social relationship database shown in Table 2 below:

[0069] 100001 100002 Trustworthy Level 1 relatives efficient 100007 100008 Trustworthy Level 2 Mother efficient

[0070] Table 2

[0071] Using the previous example, the social relationship factors between the user and the social user are "trustworthy, first level, mother". Based on the social relationship factors, the relationship status of the trustworthy social relationship between the user and the social user is marked as valid. Based on the social relationship factors "trustworthy, first level, mother" and the valid status of the trustworthy social relationship, the trustworthy relationship record between the user and the social user is created as "100007, 100008, trustworthy, second level, mother, valid".

[0072] Furthermore, to improve the effectiveness of establishing trustworthy social relationships, based on the aforementioned construction of a predicted social relationship network between users and social users, trustworthy social relationships between users and social users can also be established in the following way: Extract a predicted social relationship subnetwork associated with the user from the predicted social relationship network based on social relationship factors, and update the bidirectional predicted connections between users and social users in the predicted social relationship subnetwork using bidirectional trustworthy connections based on social relationship factors. Then, update the relationship state of the trustworthy social relationship between users and social users to obtain the trustworthy social relationship network; for example... Figure 3 The trustworthy social relationship network shown is based on the establishment of a two-way trustworthy connection between user u1 and user u2, a two-way trustworthy connection between user u1 and user u3, and a two-way trustworthy connection between user u2 and user u3.

[0073] After establishing trusted social relationships between users and social users based on social relationship factors, in order to improve the utilization rate of trusted social relationships, optionally, the user terminal performs service processing for accessing services based on the trusted social relationships; optionally, the service processing is implemented in the following manner:

[0074] Based on the relationship authorization agreement signed by the user, display trusted social relationship data containing the trusted social relationships;

[0075] Based on the social users selected from the trusted social relationship data, corresponding operation processes are performed on the access service.

[0076] The access service includes an authorization service and / or a target service, wherein the authorization service refers to other services besides the target service; the trusted social relationship data includes a user's trusted social relationship set or trusted relationship list, which contains one or more trusted social relationships; the relationship authorization agreement refers to an authorization agreement signed by the user authorizing the trusted social relationship data of one service to another service. Optionally, the relationship authorization agreement is signed at the access service. Alternatively, the relationship authorization agreement may also be signed at the provider of the trusted social relationship data.

[0077] For example, based on the relationship authorization agreement signed by the user, the trusted social relationship data "trusted social relationship between user u1 and social user s1, trusted social relationship between user u1 and social user s2" is displayed. User u1 selects social user s1 from the trusted social relationship data and performs a transfer to social user s1 in the transfer service based on the selected social user s1.

[0078] In one optional implementation of this embodiment, the trusted social relationship data described above is sorted according to the service type of each access service, and trusted social relationship data containing trusted social relationships is constructed according to the sorting results. Specifically, the trusted social relationship data containing the trusted social relationships is obtained in the following manner:

[0079] Read the user's trusted social relationship data across various access services;

[0080] The trusted social relationship data read is sorted according to the service type of each access service, and the trusted social relationship data containing the trusted social relationships is constructed according to the sorting results.

[0081] Specifically, the confidence level of the read trusted social relationship data is calculated based on the service type of each access service, and the read trusted social relationship data is sorted according to the confidence level. The sorting result is then used as trusted social relationship data containing trusted social relationships.

[0082] It should be noted that, based on the above-mentioned reading of the user's trusted social relationship data in each access service, the read trusted social relationship data can also be deduplicated; it should be noted that the deduplication process can be performed before or after the sorting process, and there is no specific order restriction here.

[0083] Furthermore, if the source service of the trusted social relationships in the user's trusted social relationship data belongs to the same service as the currently accessed service, that is, if the trusted social relationships in the trusted social relationship data displayed to the user during the access service are established on the access service, in order to improve the utilization rate of trusted social relationship data and enhance the user experience, it is not necessary for the user to sign a relationship authorization agreement. In an optional implementation of this embodiment, the following operation is also performed:

[0084] Determine the target social user selected by the user from trusted social relationship data containing the trusted social relationships;

[0085] Based on the target social user, corresponding operation processing is performed when accessing the service.

[0086] Based on the above-mentioned social relationship factors, the relationship status of the trusted social relationship between users and social users is marked as valid. Based on the social relationship factors and valid status, trusted relationship records between users and social users are created and the trusted social relationship database is updated. In order to improve the user's perception and facilitate the user's management of their trusted social relationship data, the user can be provided with the ability to edit trusted social relationship data. That is, the user can add, delete and / or update trusted social relationships in their trusted social relationship data. Specifically, the user can execute the corresponding editing instructions based on the editing instructions submitted for trusted social relationship data. The editing instructions include add instructions, delete instructions and / or update instructions.

[0087] Regarding the deletion of social users in trusted social relationship data, this embodiment provides an optional implementation method where, after establishing trusted social relationships between users based on social relationship factors, the social user can be deleted from the trusted social relationship data according to the user's deletion instruction, and the relationship status in the trusted social relationship database can be updated to invalid. This is specifically achieved in the following way:

[0088] Detect the user's deletion instruction on the social user in the trusted social relationship data;

[0089] Based on the deletion instruction, the social user is deleted from the trusted social relationship data, and the relationship status in the trusted social relationship database is updated to invalid.

[0090] In practical applications, a user may have predicted social relationships with both a first social user and a second social user simultaneously. To address this, and to improve the comprehensiveness of the user's predicted relationship records and facilitate the establishment of reliable social relationships, the social relationship between the first and second social users can be predicted based on the predicted relationship types between the user and both the first and second social users. Specifically, based on the predicted relationship types between the user and both the first and second social users, the target relationship type of the predicted social relationship between the first and second social users can be determined, and a social relationship record between the first and second social users can be created based on the target relationship type. In one optional implementation of this embodiment, the social relationship between the first and second social users is predicted in the following way:

[0091] Based on the first relationship type of the predicted social relationship between the user and the first social user, and the second relationship type of the predicted social relationship between the user and the second social user, a third relationship type of the predicted social relationship between the first social user and the second social user is determined.

[0092] A social relationship record between the first social user and the second social user is created based on the third relationship type; thereafter, the predicted social relationship database can be updated based on the created social relationship record.

[0093] For example, the predicted social relationship type between user u1 and the first social user s1 is "predicted, second level, wife", and the predicted social relationship type between user u1 and the second social user s2 is "predicted, second level, mother". Based on the predicted social relationship type between user u1 and the first social user s1 "predicted, second level, wife" and the predicted social relationship type between user u1 and the second social user s2 "predicted, second level, mother", the predicted social relationship type between the first social user s1 and the second social user s2 is determined to be "predicted, second level, mother-in-law". Based on the predicted social relationship type between the first social user s1 and the second social user s2 "predicted, second level, mother-in-law", a predicted relationship record between the first social user s1 and the second social user s2 is created.

[0094] In practical applications, to facilitate the management of predicted relationship records in the predicted social relationship database, update these records promptly, and ensure the effectiveness of predicted social relationships, the relationship status of predicted social relationships between users and social users in the predicted social relationship database can be updated based on the interaction frequency between users and social users calculated from interaction behavior data within a preset period. In one optional implementation of this embodiment, the relationship status of predicted social relationships between users and social users is updated in the following way: the interaction frequency between users and social users is calculated based on the interaction behavior data between users and social users within a preset period.

[0095] If the interaction frequency is less than the preset interaction frequency, the relationship status of the predicted social relationship between the user and the social user in the predicted social relationship database will be updated to an invalid state.

[0096] If the frequency of the interaction is greater than or equal to the predicted frequency of the interaction, no action needs to be taken.

[0097] The prediction period refers to a pre-set specific time period or time interval, such as x months; the interaction behavior data refers to the interaction data generated by users and social users interacting with each other on various access services; and the interaction frequency refers to the frequency of interaction between users and social users.

[0098] Specifically, the process of calculating the interaction frequency between users and social users based on their interaction behavior data within a preset period can be achieved by inputting the interaction behavior data between users and social users within a preset period into a frequency calculation algorithm to obtain the interaction frequency between users and social users.

[0099] In summary, the social relationship processing method provided in this embodiment, based on the user's access request for accessing social relationships in the target service sent by the user terminal, returns the read predicted social relationship data of the user to the user terminal, and generates a social relationship factor between the user and the social user corresponding to the submitted selection instruction based on the relationship type of the predicted social relationship between the user and the social user. Based on the social relationship factor, a credible social relationship between the user and the social user is established. In this way, the predicted social relationship between the user and the social user is transformed into a credible social relationship, thereby improving the effectiveness and reliability of the credible social relationship. Furthermore, by performing the transformation from predicted social relationship to credible social relationship during the process of accessing social relationships in the target service, the efficiency and convenience of social relationship transformation are improved.

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

[0101] Step S404: Read the user's predicted social relationship data and return it to the user's terminal.

[0102] Step S408: Based on the predicted social relationship type between the user and the social user corresponding to the submitted selection instruction, generate a confirmation reminder and return it to the user's terminal.

[0103] Step S412: Determine the credible relation attributes based on the predicted relation attributes in the relation type, and generate social relation factors based on the credible relation attributes and the relation features in the relation type.

[0104] Step S414: Establish a trustworthy social relationship between the user and the social user based on the social relationship factor.

[0105] The implementation process of the social relationship processing method for service processing scenarios provided above can be executed by the server. The implementation process of the service processing method for service processing scenarios provided in the following method embodiments can be executed by the user terminal. The two cooperate with each other during execution. Therefore, please refer to the corresponding content of the following method embodiments to read the above implementation process.

[0106] The following description uses the application of a social relationship processing method provided in this embodiment in a trusted social scenario as an example to further illustrate the social relationship processing method provided in this embodiment. (See also...) Figure 5 The method for handling social relationships in trusted social scenarios includes the following steps.

[0107] Step S502: Obtain the access request sent by the user terminal for the user to access social relationships in the target service.

[0108] Step S504: In response to the access request, read the user's predicted social relationship data and return it to the user's terminal.

[0109] Step S506: If a confirmation instruction submitted by a user for the relationship type of the predicted social relationship with the social user corresponding to the selection instruction is detected, a reliable relationship attribute is determined based on the predicted relationship attribute in the relationship type.

[0110] Step S508: Generate social relationship factors based on the relationship characteristics in the trusted relationship attributes and relationship types.

[0111] Step S510: Based on the social relationship factor, mark the relationship status of the trusted social relationship between the user and the social user as an effective status.

[0112] Step S512: Based on the social relationship factors and valid status, create a trusted relationship record between the user and the social user and update the trusted social relationship database.

[0113] This specification provides an example of a service processing method:

[0114] The service processing method provided in this embodiment performs service processing based on the trusted social relationship determined by the social relationship factors between the user and social users. Specifically, according to the user's access instruction to access social relationships in the target service, the method obtains the user's predicted social relationship data, and generates a selection instruction for the social users selected by the user based on the predicted social relationship data, which is then submitted to the server. Based on the trusted social relationship determined by the social relationship factors between the user and social users, the method performs service processing for access services. In this way, the predicted social relationship between the user and social users is transformed into a trusted social relationship, improving the effectiveness and reliability of the trusted social relationship. Furthermore, by performing service processing for access services through trusted social relationships, the efficiency and convenience of service processing are improved.

[0115] Reference Figure 6 The social relationship processing method provided in this embodiment specifically includes steps S602 to S608.

[0116] It should be noted that the implementation process of the service processing method provided in this embodiment can be executed by the user terminal, and the implementation process of the social relationship processing method provided in the above method embodiment can be executed by the server. The two cooperate with each other during the execution process. Therefore, to read the implementation process of the social relationship processing method provided in the above method embodiment, please refer to the corresponding content of this method embodiment. Similarly, to read the implementation process of the service processing method provided in this embodiment, please refer to the corresponding content of the above method embodiment.

[0117] Step S602: Based on the user's access instruction to access social relationships in the target service, generate an access request and send it to the server.

[0118] The target service described in this embodiment refers to a service in which a user has a need to access social relationships during the process of accessing the target service. For example, if the target service is a money transfer service, user u1 needs to identify the transfer user during the process of accessing the money transfer service, which means there is a need to query or search for social users. Or, if the target service is an auxiliary payment service, user u1 needs to identify the auxiliary user during the process of accessing the auxiliary payment service, which means there is a need to query or search for social users. In addition, the target service also includes other types of services. Other services with access needs for social relationships are also within the scope of protection of this solution, which will not be listed here.

[0119] In practical applications, users may have a need to access social relationships while accessing a target service. For example, in a money transfer service, user u1 may want to transfer money to social user s1 and can search for or query social user s1. This search or query for social users constitutes access to social relationships. Optionally, access to social relationships includes accessing social user data that has a social relationship with the user and / or accessing social relationship data between the user and social users. The user includes users who have a need to access social relationships; the social user includes users who have a social relationship with the user; the social user data includes a set of social users or a list of social users; and the social relationship data includes a set of social relationships or a list of social relationships.

[0120] In this embodiment, social relationships refer to relationships involving social behavior or data interaction, such as kinship, friendship, colleague relationships, resource trading relationships, or friendship relationships through instant messaging applications.

[0121] In practice, when a user accesses a target service, they submit an access command to access social relationships, generate an access request, and send it to the server. In turn, the server receives the access request sent by the user's terminal to access social relationships in the target service.

[0122] Step S604: Receive the predicted social relationship data of the user returned by the server.

[0123] The above-mentioned access request generated based on the user's access instruction to access social relationships in the target service is sent to the server. Correspondingly, the server obtains the user's access request to access social relationships in the target service sent by the user terminal, and reads the user's predicted social relationship data and returns it to the user terminal. In this step, the predicted social relationship data of the user returned by the server is received.

[0124] In this embodiment, predicted social relationships refer to social relationships obtained through prediction. Optionally, the relationship type of the predicted social relationship is obtained based on the interaction behavior data between the user and the social user and / or their respective feature data. The relationship type refers to the category of the predicted social relationship between the user and the social user. The interaction behavior data refers to the data generated by the interaction behavior between the user and the social user. Optionally, the interaction behavior data is obtained from one or more of the access services. The access services include target services and / or authorized services. The authorized services refer to services other than the target service. For example, the interaction behavior data is the interaction data generated by transferring money to a friend in a dining scenario, the interaction data generated by helping a family member pick up a package, or the interaction data generated by giving a gift to a partner on a holiday. The feature data includes identity feature data, such as the length of time from birth to the time of calculation.

[0125] Optionally, the predicted social relationship type includes relationship attributes and / or relationship features; the relationship attributes include a first relationship attribute or a second relationship attribute, such as the first relationship attribute being a predicted relationship attribute and the second relationship attribute being a reliable relationship attribute; the relationship features include key feature levels and / or key feature parameters, where each key feature level can correspond to one or more key feature parameters, such as a first level where the key feature parameter corresponding to the first level is a relative or friend, or a second level where the key feature parameter corresponding to the second level is a father or mother.

[0126] Optionally, the predicted social relationship type is obtained based on the interaction behavior data between the user and the social user and / or their respective feature data. In one optional implementation of this embodiment, the server performs social relationship prediction in the following manner:

[0127] Based on the interaction behavior data and the feature data, calculate the predicted probability of the candidate relationship type;

[0128] The relationship type is determined from the candidate relationship types based on the probability calculation results.

[0129] The interactive behavior data refers to the interactive data generated by users interacting with social users on various access services. Optionally, the interactive behavior data is obtained from one or more of the access services, which include target services and / or authorized services. The authorized services refer to services other than the target service. For example, the interactive behavior data is the interactive data generated by a user transferring money to a friend in a dining scenario, the interactive data generated by a user helping a family member pick up a package, or the interactive data generated by a user giving a gift to their partner on a holiday. The feature data includes identity feature data, such as the length of time from birth to the time of calculation, and whether the user is male or female.

[0130] Specifically, based on interaction behavior data and feature data, the predicted probability of each relationship type in the candidate relationship types is calculated, and relationship types whose predicted probabilities meet the probability conditions are selected from the candidate relationship types. Optionally, the probability conditions include the predicted probability being a preset probability threshold or the predicted probability ranking being at a preset position. The predicted probability ranking refers to the sorting order of the predicted probabilities. For example, the probability condition is that the predicted probability is >a%, or the probability condition is that the predicted probability ranking is first. It should be noted that if the probability condition is that the predicted probability is >a%, the predicted social relationship type between the user and the social user may be one or more. If the probability condition is that the predicted probability ranking is first, the predicted social relationship type between the user and the social user may be one.

[0131] The predicted social relationship data described in this embodiment includes a set or list of predicted social relationships consisting of predicted social relationships between one or more users and social users. Optionally, based on the relationship types in a user's predicted social relationship records, the predicted social relationships extracted from the corresponding user's predicted social relationship records are tagged by type, and the predicted social relationship data is constructed based on the tagging results. Specifically, the predicted social relationship data can be constructed in the following manner:

[0132] Read the user's predicted relationship records from the predicted social relationship database, and extract the predicted social relationships from the predicted relationship records;

[0133] Based on the relationship types in the predicted relationship records, the corresponding predicted social relationships are tagged, and the predicted social relationship data is constructed based on the tagging results.

[0134] The predicted social relationship database refers to a database or a data table (i.e., a predicted social relationship table) that stores predicted social relationships between users and social users. The database can store multiple predicted relationship records between users and their corresponding social users. Each user's predicted relationship record includes the user's identifier, the social user's identifier, and / or the relationship type of the predicted social relationship between the user and the social user. For example, the predicted social relationship database shown in Table 1 below:

[0135] 100001 100002 predict Level 1 relatives invalid 100005 100006 predict Level 2 Mother efficient

[0136] Table 1

[0137] Referring to Table 1, the predicted relationship records of user u1 (100001) are read from the predicted social relationship database. The predicted social relationships "100001, 100002" are extracted from the predicted social relationship records. The predicted social relationships are tagged with the relationship types "predicted, first level, relatives" in the predicted relationship records. The predicted social relationship list "100001, 100002, predicted, first level, relatives" is constructed based on the tagging results.

[0138] The aforementioned predicted social relationship data of users is constructed based on the predicted relationship records of users read from the predicted social relationship database. In addition, the predicted social relationship data of users can also be constructed based on the predicted relationship records of users extracted from the predicted social relationship network. The predicted social relationship network may include the predicted relationship records of users with predicted social relationships and social users, that is, it includes the predicted relationship records of all users.

[0139] Specifically, the predicted social relationship network can be constructed as follows: predictive relationship nodes are determined based on the user identifiers of the first user and the second user, and a bidirectional predictive connection between the first user and the second user is established based on the relationship feature parameters between the first user and the second user. The relationship status of the predicted social relationship between the first user and the second user is associated with the bidirectional predictive connection to obtain the predicted social relationship network.

[0140] The bidirectional predictive connection refers to the predicted bidirectional connection between the first user and the second user, which may not be real. The process of determining the predictive relationship node based on the user identifier of the first user and the user identifier of the second user can be implemented by determining the first predictive relationship node based on the user identifier of the first user and the second predictive relationship node based on the user identifier of the second user. The process of establishing the bidirectional predictive connection between the first user and the second user based on the relationship feature parameters of the first user and the second user can be implemented by establishing the first directed predictive connection between the first user and the second user based on the relationship feature parameters of the first user and the second user, and establishing the second directed predictive connection between the second user and the first user based on the relationship feature parameters of the second user and the first user, and using the first directed predictive connection and the second directed predictive connection as the bidirectional predictive connection.

[0141] like Figure 2 The predicted social relationship network shown has three predicted relationship nodes: user u1, user u2, and user u3. These three nodes establish bidirectional predicted connections based on their respective relationship feature parameters. The relationship feature parameter between user u1 and user u2 is "husband," so a first directed predicted connection from user u1 to user u2 is established based on this parameter. The relationship feature parameter between user u2 and user u1 is "wife," so a second directed predicted connection from user u2 to user u1 is established based on this parameter. The process of establishing connections between other predicted relationship nodes is similar to the process of establishing a connection between user u1 and user u2, and will not be described in detail here.

[0142] Step S606: Based on the social users selected by the user based on the predicted social relationship data, generate a selection instruction and submit it to the server.

[0143] In the above-mentioned step of receiving the user's predicted social relationship data returned by the server, a selection instruction is generated and submitted to the server based on the social users selected by the user based on the predicted social relationship data.

[0144] The selection instruction described in this embodiment refers to the instruction generated after selecting a social user from the predicted social relationship data. Optionally, the selection instruction carries the user identifier of the social user.

[0145] In practice, the system receives and displays the predicted social relationship data of the user returned by the server, and generates a selection instruction based on the social users selected by the user in the predicted social relationship data, which is then submitted to the server.

[0146] Step S608: Based on the trusted social relationship determined by the social relationship factor between the user and the social user, perform service processing for access services.

[0147] The above-mentioned step generates a selection instruction and submits it to the server based on the social users selected by the user based on the predicted social relationship data. In this step, the service processing of access service is carried out based on the trusted social relationship determined by the social relationship factor between the user and the social user. Correspondingly, the server generates the social relationship factor between the user and the social user based on the relationship type of the predicted social relationship between the user and the social user corresponding to the submitted selection instruction, and establishes a trusted social relationship between the user and the social user based on the social relationship factor.

[0148] The social relationship factor described in this embodiment refers to the social relationship factors required to establish a trustworthy social relationship between a user and a social user. Optionally, the social relationship factor includes relationship attributes, relationship features, user identifier, social user identifier, relationship creation time and / or relationship modification time. The relationship features include key feature levels and / or key feature parameters, such as the social relationship factor being "user identifier, social user identifier, trustworthy, first level, mother". Optionally, the social relationship factor is generated based on the relationship type of the predicted social relationship between the social user and the user after the selection instruction is submitted.

[0149] In practical applications, to improve the effectiveness and accuracy of social relationship factors between users and social users, and to facilitate the establishment of trustworthy social relationships and improve the efficiency of establishing trustworthy social relationships, it is possible to further detect the user's confirmation instruction regarding the predicted social relationship type corresponding to the submitted selection instruction from the social user. Based on this, social relationship factors are generated. In one optional implementation of this embodiment, the social relationship factors between users and social users are generated in the following manner:

[0150] If a confirmation instruction submitted by a user for a confirmation reminder regarding a relationship type is detected, the trusted relationship attribute is determined based on the predicted relationship attribute in the relationship type;

[0151] Social relationship factors are generated based on the relationship characteristics in the trusted relationship attributes and relationship types.

[0152] The confirmation reminder refers to a reminder message that confirms the relationship type between the user and the social user. For example, if the relationship type between the user and the social user is "predicted, first level, mother", the confirmation reminder would be "Is the social user your mother?".

[0153] For example, the predicted social relationship type between user u1 and a social user is "predicted, first level, mother", and the confirmation prompt is "Is the social user your mother?". If a confirmation instruction submitted by user u1 in response to the confirmation prompt "Is the social user your mother?" is detected, it means that user u1 acknowledges the predicted social relationship type with the social user. Based on the predicted relationship attribute "predicted" in the relationship type, the trustworthy relationship attribute is determined to be "trustworthy". Based on the trustworthy relationship attribute "trustworthy" and the relationship feature "first level, mother" in the predicted social relationship type, the social relationship factor "user identifier, social user identifier, trustworthy, first level, mother" is constructed.

[0154] Furthermore, the execution operation in the process of generating a social relationship factor between a user and a social user based on the predicted social relationship type between the user and the social user corresponding to the selection instruction can be replaced by determining a second relationship type between the user and the social user based on the instruction information and relationship type submitted by the user in response to the confirmation reminder for the relationship type, and using the second relationship type as the social relationship factor.

[0155] The process of determining the second relationship type between the user and the social user based on the instruction information and relationship type submitted by the user for the confirmation reminder of the relationship type, and using the second relationship type as the social relationship factor, can be implemented in the following way: If the instruction information is a confirmation instruction, a second relationship attribute is determined based on the first relationship attribute in the relationship type corresponding to the confirmation reminder; the second relationship attribute and the relationship features in the relationship type are used as the social relationship factor; if the instruction information is an objection instruction, a second relationship type is determined based on the relationship features in the relationship type corresponding to the confirmation reminder in the set of predicted social relationship types between the user and the social user, and the second relationship type is used as the social relationship factor.

[0156] Specifically, the second relationship type is determined from the set of predicted social relationship types between the user and the social user based on the relationship features in the relationship type corresponding to the confirmation reminder. This can be achieved by filtering out candidate relationship types other than the relationship features from the set of predicted social relationship types between the user and the social user, and determining the second relationship type as a social relationship factor from the candidate relationship types based on the predicted probability of the candidate relationship types.

[0157] The server generates a social relationship factor between the user and the social user based on the predicted social relationship type between the user and the social user corresponding to the submitted selection instruction. After that, the server establishes a reliable social relationship between the user and the social user based on the social relationship factor. In this way, the reliable social relationship helps to improve the user's access efficiency in accessing the service. The reliable social relationship refers to a reliable social relationship between the user and the social user.

[0158] In one optional implementation of this embodiment, the server establishes trusted social relationships between users and social users based on social relationship factors in the following manner:

[0159] Based on the social relationship factor, the relationship status of the trusted social relationship between the user and the social user is marked as a valid status;

[0160] Based on the social relationship factors and the effective status, a trusted relationship record between the user and the social user is created and the trusted social relationship database is updated.

[0161] Optionally, the relationship status includes a valid status and / or an invalid status; the trusted relationship record records the social relationship factors and / or relationship status between the user and the social user. Furthermore, the trusted relationship record may also record the user identifier, social user identifier, relationship creation time, and / or relationship modification time; the trusted social relationship database refers to a database that stores trusted social relationships between users and social users. The trusted social relationship database can store trusted relationship records between multiple users and their corresponding social users; for example, the trusted social relationship database shown in Table 2 below:

[0162] 100001 100002 Trustworthy Level 1 relatives efficient 100007 100008 Trustworthy Level 2 Mother efficient

[0163] Table 2

[0164] Using the previous example, the social relationship factors between the user and the social user are "trustworthy, first level, mother". Based on the social relationship factors, the relationship status of the trustworthy social relationship between the user and the social user is marked as valid. Based on the social relationship factors "trustworthy, first level, mother" and the valid status of the trustworthy social relationship, the trustworthy relationship record between the user and the social user is created as "100007, 100008, trustworthy, second level, mother, valid".

[0165] Furthermore, to improve the effectiveness of establishing trusted social relationships, based on the aforementioned server-constructed predicted social relationship network between users and social users, the server can also establish trusted social relationships between users and social users in the following way: Extracting a sub-network of predicted social relationships associated with users from the predicted social relationship network based on social relationship factors, and updating the bidirectional predicted connections between users and social users in the predicted social relationship sub-network using bidirectional trusted connections based on social relationship factors, and updating the relationship state of the trusted social relationships between users and social users to obtain the trusted social relationship network; for example... Figure 3 The trustworthy social relationship network shown is based on the establishment of a two-way trustworthy connection between user u1 and user u2, a two-way trustworthy connection between user u1 and user u3, and a two-way trustworthy connection between user u2 and user u3.

[0166] In one optional implementation of this embodiment, the service processing is implemented in the following manner:

[0167] Based on the relationship authorization agreement signed by the user, display trusted social relationship data containing the trusted social relationships;

[0168] Based on the social users selected from the trusted social relationship data, corresponding operation processes are performed on the access service.

[0169] The access service includes an authorization service and / or a target service, wherein the authorization service refers to other services besides the target service; the trusted social relationship data includes a user's trusted social relationship set or trusted relationship list, which contains one or more trusted social relationships; the relationship authorization agreement refers to an authorization agreement signed by the user authorizing the trusted social relationship data of one service to another service. Optionally, the relationship authorization agreement is signed at the access service. Alternatively, the relationship authorization agreement may also be signed at the provider of the trusted social relationship data.

[0170] For example, based on the relationship authorization agreement signed by the user, the trusted social relationship data "trusted social relationship between user u1 and social user s1, trusted social relationship between user u1 and social user s2" is displayed. User u1 selects social user s1 from the trusted social relationship data and performs a transfer to social user s1 in the transfer service based on the selected social user s1.

[0171] The aforementioned trusted social relationship data is processed by sorting the trusted social relationship data read from each access service according to the service type of each access service, and constructing trusted social relationship data containing trusted social relationships according to the sorting results. Specifically, the server obtains the trusted social relationship data containing the trusted social relationships in the following way:

[0172] Read the user's trusted social relationship data across various access services;

[0173] The trusted social relationship data read is sorted according to the service type of each access service, and the trusted social relationship data containing the trusted social relationships is constructed according to the sorting results.

[0174] Specifically, the confidence level of the read trusted social relationship data is calculated based on the service type of each access service, and the read trusted social relationship data is sorted according to the confidence level. The sorting result is then used as trusted social relationship data containing trusted social relationships.

[0175] It should be noted that, based on the above-mentioned reading of the user's trusted social relationship data in each access service, the read trusted social relationship data can also be deduplicated; it should be noted that the deduplication process can be performed before or after the sorting process, and the specific order is not limited here.

[0176] Furthermore, if the source service of the trusted social relationships in the user's trusted social relationship data belongs to the same service as the currently accessed service, that is, if the trusted social relationships in the trusted social relationship data displayed to the user during the access service are established on the access service, in order to improve the utilization rate of trusted social relationship data and enhance the user experience, it is not necessary for the user to sign a relationship authorization agreement. In another optional implementation method provided in this embodiment, the service processing is implemented in the following way:

[0177] Determine the target social user selected by the user from trusted social relationship data containing the trusted social relationships;

[0178] Based on the target social user, corresponding operation processing is performed when accessing the service.

[0179] Based on the aforementioned server's marking of the trustworthy social relationship status between users and social users as valid states based on social relationship factors, and the creation and updating of trustworthy relationship records between users and social users according to social relationship factors and valid states, in order to improve user awareness and facilitate user management of their trustworthy social relationship data, users can be provided with the ability to edit trustworthy social relationship data. That is, users can add, delete, and / or update trustworthy social relationships in their trustworthy social relationship data. Specifically, the server can execute the corresponding editing instructions submitted by the user for trustworthy social relationship data. The editing instructions include add instructions, delete instructions, and / or update instructions.

[0180] Regarding the deletion of social users in trusted social relationship data, after the server establishes trusted social relationships between users based on social relationship factors, it can delete the social user from the trusted social relationship data according to the user's deletion instruction and update the relationship status in the trusted social relationship database to invalid. Specifically, the server implements this in the following way:

[0181] Detect the user's deletion instruction on the social user in the trusted social relationship data;

[0182] Based on the deletion instruction, the social user is deleted from the trusted social relationship data, and the relationship status in the trusted social relationship database is updated to invalid.

[0183] In practical applications, a user may have predicted social relationships with both a first social user and a second social user simultaneously. To address this, and to improve the comprehensiveness of the user's predicted relationship records and facilitate the establishment of trustworthy social relationships, the server can predict the social relationship between the first and second social users based on the predicted relationship types between the user and both the first and second social users. Specifically, the server can determine the target relationship type for the predicted social relationship between the first and second social users based on the predicted relationship types between the user and both the first and second social users, and create a social relationship record for the first and second social users based on the target relationship type. The social relationship prediction between the first and second social users is performed in the following way:

[0184] Based on the first relationship type of the predicted social relationship between the user and the first social user, and the second relationship type of the predicted social relationship between the user and the second social user, a third relationship type of the predicted social relationship between the first social user and the second social user is determined;

[0185] A social relationship record between the first social user and the second social user is created based on the third relationship type; thereafter, the predicted social relationship database can be updated based on the created social relationship record.

[0186] For example, the predicted social relationship type between user u1 and the first social user s1 is "predicted, second level, wife", and the predicted social relationship type between user u1 and the second social user s2 is "predicted, second level, mother". Based on the predicted social relationship type between user u1 and the first social user s1 "predicted, second level, wife" and the predicted social relationship type between user u1 and the second social user s2 "predicted, second level, mother", the predicted social relationship type between the first social user s1 and the second social user s2 is determined to be "predicted, second level, mother-in-law". Based on the predicted social relationship type between the first social user s1 and the second social user s2 "predicted, second level, mother-in-law", a predicted relationship record between the first social user s1 and the second social user s2 is created.

[0187] In practical applications, to facilitate the management of predicted relationship records in the predicted social relationship database, and to ensure the effectiveness of predicted social relationships in these records, the relationship status of predicted social relationships between users and social users can be updated based on the interaction frequency calculated from user and social user interaction behavior data within a preset period. Specifically, the server updates the relationship status of predicted social relationships between users and social users in the following way:

[0188] The frequency of interaction between the user and the social user is calculated based on the interaction behavior data between the user and the social user within a preset period.

[0189] If the interaction frequency is less than the preset interaction frequency, the relationship status of the predicted social relationship between the user and the social user in the predicted social relationship database will be updated to an invalid state.

[0190] If the frequency of the interaction is greater than or equal to the predicted frequency of the interaction, no action is required.

[0191] The prediction period refers to a pre-set specific time period or time interval, such as x months; the interaction behavior data refers to the interaction data generated by users and social users interacting with each other on various access services; and the interaction frequency refers to the frequency of interaction between users and social users.

[0192] Specifically, the process by which the server calculates the frequency of interaction between users and social users based on the interaction behavior data between users and social users within a preset period can be achieved by inputting the interaction behavior data between users and social users within a preset period into a frequency calculation algorithm to obtain the frequency of interaction between users and social users.

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

[0194] Step S402: Based on the user's access instruction to access social relationships in the target service, generate an access request and send it to the server.

[0195] Step S406: Based on the social users selected by the user based on predicted social relationship data, generate a selection instruction and submit it to the server.

[0196] Step S410: Obtain the user's confirmation instruction for the confirmation reminder and send it to the server.

[0197] Step S416: If an access instruction submitted by a user to access social relationships is detected, the trusted social relationship data containing trusted social relationships is displayed based on the relationship authorization agreement signed by the user.

[0198] Step S418: Based on the social users selected from the trusted social relationship data, perform corresponding operation processing when accessing the service.

[0199] The following is an embodiment of a social relationship processing device provided in this specification:

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

[0201] Reference Figure 7 The diagram illustrates a social relationship processing device provided in this embodiment.

[0202] 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.

[0203] This embodiment provides a social relationship processing device, including:

[0204] The access request acquisition module 702 is configured to acquire access requests sent by the user terminal for users to access social relationships in the target service;

[0205] The relationship data reading module 704 is configured to read the user's predicted social relationship data and return it to the user terminal in response to the access request;

[0206] The relationship factor generation module 706 is configured to generate a social relationship factor between the user and the social user based on the relationship type of the predicted social relationship between the user and the social user corresponding to the selection instruction.

[0207] The social relationship establishment module 708 is configured to establish a trusted social relationship between the user and the social user based on the social relationship factors.

[0208] This specification provides an embodiment of a service processing device as follows:

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

[0210] Reference Figure 8 The diagram shows a service device provided in this embodiment.

[0211] 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.

[0212] This embodiment provides a service processing device, including:

[0213] The access request sending module 802 is configured to generate an access request and send it to the server based on the user's access instruction to access social relationships in the target service;

[0214] The relationship data receiving module 804 is configured to receive the predicted social relationship data of the user returned by the server;

[0215] The selection instruction submission module 806 is configured to generate a selection instruction and submit it to the server based on the social user selected by the user based on the predicted social relationship data.

[0216] The service processing module 808 is configured to perform service processing for access services based on the trusted social relationship determined by the social relationship factor between the user and the social user; the social relationship factor is generated according to the relationship type of the predicted social relationship between the social user and the user after the selection instruction is submitted.

[0217] This specification provides an embodiment of a social relationship processing device as follows:

[0218] Corresponding to the social relationship processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a social relationship processing device for executing the social relationship processing method provided above. Figure 9This is a schematic diagram of the structure of a social relationship processing device provided for one or more embodiments of this specification.

[0219] This embodiment provides a social relationship processing device, including:

[0220] like Figure 9 As shown, social relationship processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 901 and memory 902, with memory 902 storing one or more application programs or data. Memory 902 can be temporary or persistent storage. The application programs stored in memory 902 may include one or more modules (not shown), each module including a series of computer-executable instructions from the social relationship processing device. Furthermore, processor 901 may be configured to communicate with memory 902, executing the series of computer-executable instructions in memory 902 on the social relationship processing device. The social relationship 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.

[0221] In one specific embodiment, the social 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 social 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:

[0222] Get the access requests sent by the user terminal to access social relationships in the target service;

[0223] In response to the access request, the predicted social relationship data of the user is read and returned to the user terminal;

[0224] Based on the predicted social relationship type between the user and the social user corresponding to the selection instruction, a social relationship factor between the user and the social user is generated.

[0225] A trustworthy social relationship is established between the user and the social user based on the aforementioned social relationship factors.

[0226] This specification provides an example of a service processing device as follows:

[0227] Corresponding to the service processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a service processing device for executing the service processing method provided above. Figure 10 This is a schematic diagram of the structure of a service processing device provided for one or more embodiments of this specification.

[0228] This embodiment provides a service processing device, including:

[0229] like Figure 10 As shown, the service processing device can vary considerably due to differences in configuration or performance. It may include one or more processors 1001 and memory 1002, and the memory 1002 may store one or more application programs or data. The memory 1002 may be temporary or persistent storage. The application programs stored in the memory 1002 may include one or more modules (not shown), each module may include a series of computer-executable instructions from the service processing device. Furthermore, the processor 1001 may be configured to communicate with the memory 1002 and execute the series of computer-executable instructions in the memory 1002 on the service processing device. The service processing device may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input / output interfaces 1005, one or more keyboards 1006, etc.

[0230] In one specific embodiment, the service 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 use in the service 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:

[0231] Based on the user's access instruction to access social relationships in the target service, an access request is generated and sent to the server;

[0232] Receive the predicted social relationship data of the user returned by the server;

[0233] Based on the social users selected by the user based on the predicted social relationship data, a selection instruction is generated and submitted to the server;

[0234] The service processing for access services is performed based on the trusted social relationship determined by the social relationship factor between the user and the social user; the social relationship factor is generated according to the relationship type of the predicted social relationship between the social user and the user after the selection instruction is submitted.

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

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

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

[0238] Get the access requests sent by the user terminal to access social relationships in the target service;

[0239] In response to the access request, the predicted social relationship data of the user is read and returned to the user terminal;

[0240] Based on the predicted social relationship type between the user and the social user corresponding to the selection instruction, a social relationship factor between the user and the social user is generated.

[0241] A trustworthy social relationship is established between the user and the social user based on the aforementioned social relationship factors.

[0242] It should be noted that the embodiments of a storage medium described in this specification and the embodiments of a social 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.

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

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

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

[0246] Based on the user's access instruction to access social relationships in the target service, an access request is generated and sent to the server;

[0247] Receive the predicted social relationship data of the user returned by the server;

[0248] Based on the social users selected by the user based on the predicted social relationship data, a selection instruction is generated and submitted to the server;

[0249] The service processing for access services is performed based on the trusted social relationship determined by the social relationship factor between the user and the social user; the social relationship factor is generated according to the relationship type of the predicted social relationship between the social user and the user after the selection instruction is submitted.

[0250] It should be noted that the embodiments of a storage medium and the embodiments of a service processing method 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.

[0251] 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.

[0252] 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.

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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.

[0257] 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.

[0258] 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.

[0259] 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.

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

[0261] 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.

[0262] 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.

[0263] 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.

[0264] 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.

[0265] 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.

[0266] 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 method for handling social relationships, comprising: Get the access requests sent by the user terminal to access social relationships in the target service; In response to the access request, the predicted social relationship data of the user is read and returned to the user terminal; If a confirmation instruction is detected that the user has submitted a confirmation reminder for the relationship type of the predicted social relationship of the social user corresponding to the selection instruction, a reliable relationship attribute is determined based on the predicted relationship attribute in the relationship type, and a social relationship factor between the user and the social user is generated according to the reliable relationship attribute and the relationship feature in the relationship type. The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; Based on the social relationship factor, the relationship status of the trusted social relationship between the user and the social user is marked as valid. Based on the social relationship factor and the valid status, a trusted relationship record between the user and the social user is created and the trusted social relationship database is updated.

2. The social relationship processing method according to claim 1, wherein the user terminal performs service processing for accessing services based on the trusted social relationship; in, The service processing includes: Based on the relationship authorization agreement signed by the user, display trusted social relationship data containing the trusted social relationships; Based on the social users selected from the trusted social relationship data, corresponding operation processes are performed on the access service.

3. The social relationship processing method according to claim 1 further includes: Determine the target social user selected by the user from trusted social relationship data containing the trusted social relationships; Based on the target social user, corresponding operation processing is performed when accessing the service.

4. The social relationship processing method according to claim 1 further includes: Based on the first relationship type of the predicted social relationship between the user and the first social user, and the second relationship type of the predicted social relationship between the user and the second social user, the third relationship type of the predicted social relationship between the user and the third social user is determined. A social relationship record between the user and the third social user is created based on the third relationship type.

5. The social relationship processing method according to claim 1, after the step of creating a trusted relationship record between the user and the social user based on the social relationship factor and the effective state and updating the trusted social relationship database, further includes: Detect the user's deletion instruction on the social user in the trusted social relationship data; Based on the deletion instruction, the social user is deleted from the trusted social relationship data, and the relationship status in the trusted social relationship database is updated to invalid.

6. The social relationship processing method according to claim 1 further includes: The frequency of interaction between the user and the social user is calculated based on the interaction behavior data between the user and the social user within a preset period. If the interaction frequency is less than the preset interaction frequency, the relationship status of the predicted social relationship between the user and the social user in the predicted social relationship database will be updated to an invalid state.

7. The social relationship processing method according to claim 2, wherein the trusted social relationship data is obtained in the following manner: Read the user's trusted social relationship data across various access services; The trusted social relationship data read is sorted according to the service type of each access service, and the trusted social relationship data containing the trusted social relationships is constructed according to the sorting results.

8. The social relationship processing method according to claim 1, wherein the predicted social relationship data is obtained in the following manner: Read the user's predicted relationship records from the predicted social relationship database, and extract the predicted social relationships from the predicted relationship records; Based on the relationship types in the predicted relationship records, the corresponding predicted social relationships are tagged, and the predicted social relationship data is constructed based on the tagging results.

9. A service processing method, comprising: Based on the user's access instruction to access social relationships in the target service, an access request is generated and sent to the server; Receive the predicted social relationship data of the user returned by the server; Based on the social users selected by the user based on the predicted social relationship data, a selection instruction is generated and submitted to the server; Based on the trusted social relationship determined by the social relationship factors between the user and the social user, the service processing of access services is carried out. After detecting the confirmation instruction submitted by the user for the confirmation reminder of the relationship type of the predicted social relationship of the social user, the social relationship factor determines the credible relationship attribute based on the predicted relationship attribute in the relationship type, and generates a relationship based on the credible relationship attribute and the relationship feature in the relationship type; The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; The server marks the relationship status of the trusted social relationship as valid based on the social relationship factor, and creates a trusted relationship record between the user and the social user based on the social relationship factor and the valid status, and updates the trusted social relationship database.

10. The service processing method according to claim 9, wherein the service processing includes: Based on the relationship authorization agreement signed by the user on the access service, display trusted social relationship data containing the trusted social relationships; Based on the social users selected from the trusted social relationship data, corresponding operation processing is performed on the access service; And / or, The system determines the social user selected by the user from the trusted social relationship data containing the trusted social relationships, and performs corresponding operation processing on the access service based on the selected social user.

11. A social relationship processing device, comprising: The access request acquisition module is configured to acquire access requests sent by the user terminal for accessing social relationships in the target service. The relationship data reading module is configured to read the user's predicted social relationship data and return it to the user terminal in response to the access request; The relationship factor generation module is configured to, if it detects a confirmation instruction submitted by the user for a confirmation reminder of the relationship type of the predicted social relationship of the social user corresponding to the selection instruction, determine a reliable relationship attribute based on the predicted relationship attribute in the relationship type, and generate a social relationship factor between the user and the social user based on the reliable relationship attribute and the relationship feature in the relationship type; The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; The social relationship establishment module is configured to mark the relationship status of the trusted social relationship between the user and the social user as an effective state based on the social relationship factor, and to create a trusted relationship record between the user and the social user and update the trusted social relationship database according to the social relationship factor and the effective state.

12. A service processing apparatus, comprising: The access request sending module is configured to generate an access request and send it to the server based on the user's access instruction to access social relationships in the target service; The relationship data receiving module is configured to receive the predicted social relationship data of the user returned by the server; The selection instruction submission module is configured to generate a selection instruction and submit it to the server based on the social users selected by the user based on the predicted social relationship data. The service processing module is configured to perform service processing for access services based on the trusted social relationship determined by the social relationship factor between the user and the social user. After detecting the confirmation instruction submitted by the user for the confirmation reminder of the relationship type of the predicted social relationship of the social user, the social relationship factor determines the credible relationship attribute based on the predicted relationship attribute in the relationship type, and generates a relationship based on the credible relationship attribute and the relationship feature in the relationship type; The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; The server marks the relationship status of the trusted social relationship as valid based on the social relationship factor, and creates a trusted relationship record between the user and the social user based on the social relationship factor and the valid status, and updates the trusted social relationship database.

13. A social relationship processing device, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Get the access requests sent by the user terminal to access social relationships in the target service; In response to the access request, the predicted social relationship data of the user is read and returned to the user terminal; If a confirmation instruction is detected that the user has submitted a confirmation reminder for the relationship type of the predicted social relationship of the social user corresponding to the selection instruction, a reliable relationship attribute is determined based on the predicted relationship attribute in the relationship type, and a social relationship factor between the user and the social user is generated according to the reliable relationship attribute and the relationship feature in the relationship type. The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; Based on the social relationship factor, the relationship status of the trusted social relationship between the user and the social user is marked as valid. Based on the social relationship factor and the valid status, a trusted relationship record between the user and the social user is created and the trusted social relationship database is updated.

14. A service processing apparatus, comprising: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Based on the user's access instruction to access social relationships in the target service, an access request is generated and sent to the server; Receive the predicted social relationship data of the user returned by the server; Based on the social users selected by the user based on the predicted social relationship data, a selection instruction is generated and submitted to the server; Based on the trusted social relationship determined by the social relationship factors between the user and the social user, the service processing of access services is carried out. After detecting the confirmation instruction submitted by the user for the confirmation reminder of the relationship type of the predicted social relationship of the social user, the social relationship factor determines the credible relationship attribute based on the predicted relationship attribute in the relationship type, and generates a relationship based on the credible relationship attribute and the relationship feature in the relationship type; The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; The server marks the relationship status of the trusted social relationship as valid based on the social relationship factor, and creates a trusted relationship record between the user and the social user based on the social relationship factor and the valid status, and updates the trusted social relationship database.

15. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Get the access requests sent by the user terminal to access social relationships in the target service; In response to the access request, the predicted social relationship data of the user is read and returned to the user terminal; If a confirmation instruction is detected that the user has submitted a confirmation reminder for the relationship type of the predicted social relationship of the social user corresponding to the selection instruction, a reliable relationship attribute is determined based on the predicted relationship attribute in the relationship type, and a social relationship factor between the user and the social user is generated according to the reliable relationship attribute and the relationship feature in the relationship type. The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; Based on the social relationship factor, the relationship status of the trusted social relationship between the user and the social user is marked as valid. Based on the social relationship factor and the valid status, a trusted relationship record between the user and the social user is created and the trusted social relationship database is updated.

16. A storage medium for storing computer-executable instructions, which, when executed by a processor, perform the following process: Based on the user's access instruction to access social relationships in the target service, an access request is generated and sent to the server; Receive the predicted social relationship data of the user returned by the server; Based on the social users selected by the user based on the predicted social relationship data, a selection instruction is generated and submitted to the server; Based on the trusted social relationship determined by the social relationship factors between the user and the social user, the service processing of access services is carried out. After detecting the confirmation instruction submitted by the user for the confirmation reminder of the relationship type of the predicted social relationship of the social user, the social relationship factor determines the credible relationship attribute based on the predicted relationship attribute in the relationship type, and generates a relationship based on the credible relationship attribute and the relationship feature in the relationship type; The relationship type is obtained by predicting social relationships based on the interaction behavior data between the user and the social user. The social relationship prediction includes: calculating the predicted probability of candidate relationship types based on the interaction behavior data, and determining the relationship type among the candidate relationship types based on the predicted probability; The server marks the relationship status of the trusted social relationship as valid based on the social relationship factor, and creates a trusted relationship record between the user and the social user based on the social relationship factor and the valid status, and updates the trusted social relationship database.

Images