Method and system for adding social circles

Abstract

The present application relates to the field of network communication technology, and discloses a method and system for adding social circles. By associating a second user ID with a circle ID and combining it with a system tag knowledge graph, it is possible to accurately analyze the interests and correlations of circle members, thereby improving the accuracy of recommendations; by calculating the correlation between a first user ID and each second user ID in the system tag knowledge graph, the circle friend list is sorted according to the degree of correlation, thereby improving the probability of successful recommendations; by providing a variety of request options, including circle entry requests, circle friend requests, and cross-circle requests, users are given enough choices of dating modes, ensuring that users make friends based on their own choices, and providing personalized and interactive user experience.

Description

Technical Field

[0001] The present application relates to the field of Internet communication technology, and in particular to a method and system for adding a social circle. Background Art

[0002] "Dating" refers to a popular social method among young people. It is more about working together than just being friends. It focuses on precise companionship in a vertical segment, including but not limited to meal dating, travel dating, coffee dating, sports dating, and drama dating. The popularity of the above new stranger social methods has brought new technical challenges to the Internet social programs' ability to comprehensively collect and accurately divide users' characteristics and to push users in a targeted manner to facilitate "dating".

[0003] In existing stranger dating software, when users match friends through interest circles or tags, there are problems such as inaccurate matching and low friend recommendation rate. Therefore, there is an urgent need for a solution that accurately and efficiently matches interest circles, circle members, and recommends circle friends for users based on personal interests and companionship needs, so that two strangers who become circle friends are connected based on real common interests and topics, and only on this basis can a closer "match" be achieved efficiently and accurately. Summary of the invention

[0004] In response to the defects in the prior art, the present application proposes a method and system for adding social circles. By associating the second user ID and the circle ID and combining it with the system label knowledge graph, it can accurately analyze the interests and correlations of circle members, thereby improving the accuracy of recommendations; by calculating the correlation between the first user ID and each second user ID in the system label knowledge graph, the circle friend list is sorted according to the degree of correlation, thereby increasing the probability of successful recommendation; by providing a variety of request options, including circle entry requests, circle friend requests, and cross-circle requests, users are given enough choices of dating modes, ensuring that users make friends based on their own choices, and providing personalized and interactive user experience.

[0005] To solve the above problems, the present application provides a method for adding a social circle, which includes:

[0006] S1. The first user terminal logged in by the first user ID obtains the first user ID and a selected circle identifier and sends it to the business server; wherein the circle identifier includes: a circle ID directly associated with a number of second user IDs;

[0007] S2. The business server matches the circle ID with the system tag knowledge graph in the database, generates an invitation to join the circle corresponding to the circle ID, and searches the system tag knowledge graph for several second user IDs associated with the circle ID;

[0008] S3. The business server calculates the relevance between the first user ID and each second user ID in the system tag knowledge graph, and arranges the second user IDs from high to low according to the relevance to generate a circle of friends list;

[0009] S4. The first user terminal receives the circle-joining invitation and circle-friend list sent by the business server, and performs one of the following actions according to the operation input by the first user terminal:

[0010] a. Send a circle entry request and / or circle member request to the business server;

[0011] b. Send circle friend requests and / or cross-circle requests to the business server.

[0012] In a possible embodiment, the method further includes S5, which specifically includes:

[0013] S501. If the business server receives a circle entry request, it sends the circle's home page content to the first user terminal according to the circle entry request;

[0014] S502. If the business server receives a circle friend request, it sends a circle friend request to the second client logged in by the corresponding second user ID according to the circle friend request;

[0015] S503. If the service server receives the cross-circle request, it sends multiple new circle identifiers to the first user terminal and returns to execute S1.

[0016] In a possible embodiment, the method further includes: when the service server generates the circle friend list, further screening the second user ID based on the following conditions:

[0017] The frequency of social interactions between the second user ID and the first user ID;

[0018] The activity level of the second user ID in the circle;

[0019] The degree of matching between the interest tag of the second user ID and the interest tag of the first user ID.

[0020] In a possible embodiment, if the second client logged in by the second user ID receives and agrees to the circle friend request, the friend relationship is added to the system tag knowledge graph through the business server to establish a direct association between the first user ID and the second user ID.

[0021] In a possible embodiment, the business server searches the system tag knowledge graph to determine whether the first user ID and the second user ID are associated with a third-party binding account;

[0022] If the first user ID is associated with a third-party bound account, the business server obtains the third-party bound account of the first user ID and sends it to the second client; the second client receives the third-party bound account of the first user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface;

[0023] If the second user ID is associated with a third-party bound account, the business server obtains the third-party bound account of the second user ID and sends it to the first user end; the first user end receives the third-party bound account of the second user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface.

[0024] In a possible embodiment, the third-party binding account includes: a social media account, an email address, a phone number, or other external platform accounts that support friend relationships, and the business server calls the corresponding API interface to add according to different third-party platforms.

[0025] In a possible embodiment, in S3, the business server calculates the association between the first user ID and each second user ID in the system tag knowledge graph, including:

[0026] A calculation model based on tag weights is used to ensure that the second user ID that best matches the interests of the first user ID is prioritized in the circle friend list.

[0027] In a possible embodiment, the label weight calculation model includes setting weights for the following data respectively:

[0028] Similarity between the interest tags of the first user ID and the second user ID;

[0029] The number of circles that the first user ID and the second user ID are in at the same time;

[0030] The number of activities jointly participated by the first user ID and the second user ID;

[0031] The historical interaction frequency and time interval between the first user ID and the second user ID.

[0032] In a possible embodiment, the nodes of the system tag knowledge graph include: one or more of interest tags, user IDs, third-party bound accounts, circle IDs, and activity tags.

[0033] In a possible embodiment, in S4, the invitation to join the circle also includes real-time basic information of the circle, and the real-time basic information includes: the number of members, the number of active members, discussion topics, and active discussion topics.

[0034] On the other hand, the present application also provides a social circle system, the system comprising:

[0035] Acquisition module: used for the first user terminal logged in by the first user ID, acquiring the first user ID and a selected circle identifier and sending them to the business server; wherein the circle identifier includes: circle IDs directly associated with a plurality of second user IDs;

[0036] Search module: used to match the circle ID with the system tag knowledge graph in the database through the business server, generate a circle entry invitation corresponding to the circle ID, and search for several second user IDs associated with the circle ID in the system tag knowledge graph;

[0037] Generation module: used to calculate the correlation between the first user ID and each second user ID in the system tag knowledge graph through the business server, and arrange the second user IDs from high to low according to the correlation, and generate a circle friend list;

[0038] Sending module: used for the first user terminal to receive the circle-joining invitation and circle-friend list sent by the business server, and to perform one of the following actions according to the operation input by the first user terminal:

[0039] a. Send a circle entry request and / or circle member request to the business server;

[0040] b. Send circle friend requests and / or cross-circle requests to the business server.

[0041] Furthermore, an adding module is also included, and the adding module is specifically used for:

[0042] A first adding module is used to determine whether a circle entry request is received, and if the business server receives the circle entry request, send the main page content of the circle to the first user terminal according to the circle entry request;

[0043] A second adding module is used to determine whether the circle friend request is received, and if the business server receives the circle friend request, send the circle friend request to the second client logged in by the corresponding second user ID according to the circle friend request;

[0044] The third adding module is used to determine whether the cross-circle request is received. If the service server receives the cross-circle request, it sends a plurality of new circle identifiers to the first user terminal and sends them to the acquisition module.

[0045] Furthermore, the generating module is also used for the business server to further filter the second user ID based on the following conditions when generating the circle friend list:

[0046] The frequency of social interactions between the second user ID and the first user ID;

[0047] The activity level of the second user ID in the circle;

[0048] The degree of matching between the interest tag of the second user ID and the interest tag of the first user ID.

[0049] If the second client logged in by the second user ID receives and agrees to the circle friend request, the friend relationship is added to the system tag knowledge graph through the business server to establish a direct association between the first user ID and the second user ID.

[0050] Furthermore, the search module is further used to: search the system tag knowledge graph through the business server to determine whether the first user ID and the second user ID are associated with a third-party binding account;

[0051] Determine whether the first user ID is associated with a third-party binding account. If the first user ID is associated with a third-party binding account, the business server obtains the third-party binding account of the first user ID and sends it to the second client; the second client receives the third-party binding account of the first user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface;

[0052] Determine whether the second user ID is associated with a third-party binding account. If the second user ID is associated with a third-party binding account, the business server obtains the third-party binding account of the second user ID and sends it to the first user end; the first user end receives the third-party binding account of the second user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface.

[0053] Furthermore, the third-party binding account includes: a social media account, an email address, a phone number, or other external platform accounts that support friend relationships, and the business server calls the corresponding API interface to add according to different third-party platforms.

[0054] Furthermore, in the generation module, the business server calculates the association between the first user ID and each of the second user IDs in the system tag knowledge graph, including:

[0055] A calculation model based on tag weights is used to ensure that the second user ID that best matches the interests of the first user ID is prioritized in the circle of friends list.

[0056] Furthermore, the label weight calculation model includes setting weights for the following data respectively:

[0057] Similarity between the interest tags of the first user ID and the second user ID;

[0058] The number of circles in which the first user ID and the second user ID are simultaneously located;

[0059] The number of activities jointly participated by the first user ID and the second user ID;

[0060] The historical interaction frequency and time interval between the first user ID and the second user ID.

[0061] Furthermore, in the search module and the generation module, the nodes of the system tag knowledge graph include: one or more of interest tags, user IDs, third-party bound accounts, circle IDs, and activity tags;

[0062] In the sending module, the invitation to join the circle also includes the real-time basic information of the circle, and the real-time basic information includes: the number of members, the number of active members, discussion topics, and active discussion topics.

[0063] Compared with the prior art, this application has the following advantages and beneficial effects:

[0064] (1) The social circle adding method and system provided by the present application can accurately analyze the interests and relevance of circle members by associating the second user ID with the circle ID and combining the system tag knowledge graph, thereby improving the accuracy of recommendations;

[0065] (2) By calculating the correlation between the first user ID and each second user ID in the system tag knowledge graph, the friend list is sorted according to the correlation, thereby increasing the probability of successful recommendation;

[0066] (3) By providing a variety of request options, including requests to join a circle, requests to make friends in a circle, and requests to cross circles, we provide users with sufficient choices for making friends, ensuring that users make friends based on their own choices and providing a personalized and interactive user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0068] Figure 1A flowchart of a method for adding a social circle provided in this application;

[0069] Figure 2 is a flow chart of the specific steps of step S5;

[0070] Figure 3 A structural diagram of a social circle system provided for this application. DETAILED DESCRIPTION

[0071] In the following, various embodiments of the present disclosure will be described more fully. The present disclosure may have various embodiments, and adjustments and changes may be made therein. However, it should be understood that there is no intention to limit the various embodiments of the present disclosure to the specific embodiments disclosed herein, but rather the present disclosure should be understood to cover all adjustments, equivalents and / or alternatives that fall within the spirit and scope of the various embodiments of the present disclosure.

[0072] Hereinafter, the terms "include" or "may include" that may be used in various embodiments of the present disclosure indicate the presence of disclosed functions, operations, or elements, and do not limit the addition of one or more functions, operations, or elements. In addition, as used in various embodiments of the present disclosure, the terms "include", "have", and their cognates are intended only to indicate specific features, numbers, steps, operations, elements, components, or a combination of the foregoing, and should not be understood as first excluding the presence of one or more other features, numbers, steps, operations, elements, components, or a combination of the foregoing or the possibility of adding one or more features, numbers, steps, operations, elements, components, or a combination of the foregoing.

[0073] In various embodiments of the present disclosure, the expression "or" or "at least one of A or / and B" includes any combination or all combinations of the words listed at the same time. For example, the expression "A or B" or "at least one of A or / and B" may include A, may include B, or may include both A and B.

[0074] The expressions (such as "first", "second", etc.) used in the various embodiments of the present disclosure may modify the various constituent elements in the various embodiments, but may not limit the corresponding constituent elements. For example, the above expressions do not limit the order and / or importance of the elements. The above expressions are only used for the purpose of distinguishing one element from other elements. For example, the first user device and the second user device indicate different user devices, although both are user devices. For example, without departing from the scope of the various embodiments of the present disclosure, the first element may be referred to as the second element, and similarly, the second element may also be referred to as the first element.

[0075] It should be noted that if it is described that one component element is “connected” to another component element, the first component element may be directly connected to the second component element, and a third component element may be “connected” between the first component element and the second component element. Conversely, when one component element is “directly connected” to another component element, it can be understood that there is no third component element between the first component element and the second component element.

[0076] The term “user” used in various embodiments of the present disclosure may indicate a person using an electronic device or a device (eg, an artificial intelligence electronic device) using the electronic device.

[0077] The terms used in the various embodiments of the present disclosure are only used for the purpose of describing specific embodiments and are not intended to limit the various embodiments of the present disclosure. As used herein, the singular form is intended to also include the plural form, unless the context clearly indicates otherwise. Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as the meanings commonly understood by ordinary technicians in the field to which the various embodiments of the present disclosure belong. The terms (such as the terms defined in the generally used dictionary) will be interpreted as having the same meaning as the contextual meaning in the relevant technical field and will not be interpreted as having an idealized meaning or an overly formal meaning, unless clearly defined in the various embodiments of the present disclosure. Example

[0078] Embodiment 1 provides an instant messaging method, such as Figure 1 As shown, the method includes:

[0079] S1. The first user terminal logged in by the first user ID obtains the first user ID and a selected circle identifier and sends it to the business server; wherein the circle identifier includes: a circle ID directly associated with a number of second user IDs;

[0080] S2. The business server matches the circle ID with the system tag knowledge graph in the database, generates an invitation to join the circle corresponding to the circle ID, and searches the system tag knowledge graph for several second user IDs associated with the circle ID;

[0081] S3. The business server calculates the relevance between the first user ID and each second user ID in the system tag knowledge graph, and arranges the second user IDs from high to low according to the relevance to generate a circle of friends list;

[0082] S4. The first user terminal receives the circle-joining invitation and circle-friend list sent by the business server, and performs one of the following actions according to the operation input by the first user terminal:

[0083] a. Send a circle entry request and / or circle member request to the business server;

[0084] b. Send circle friend requests and / or cross-circle requests to the business server.

[0085] Beneficial effects: By associating the second user ID and the circle ID and combining it with the system tag knowledge graph, the interests and correlations of circle members can be accurately analyzed, thereby improving the accuracy of recommendations; by calculating the correlation between the first user ID and each second user ID in the system tag knowledge graph, the circle friend list is sorted according to the degree of correlation, thereby increasing the probability of successful recommendation; by providing a variety of request options, including circle entry requests, circle friend requests, and cross-circle requests, users are given enough choices of dating modes to ensure that users make friends based on their own choices, providing personalized and interactive user experience.

[0086] Embodiment 2:

[0087] Embodiment 2 is further based on embodiment 1, and the method further includes S5, S5 is as follows Figure 2 As shown, S5 specifically includes:

[0088] S501. If the business server receives a circle entry request, it sends the circle's home page content to the first user terminal according to the circle entry request;

[0089] S502. If the business server receives a circle friend request, it sends a circle friend request to the second client logged in by the corresponding second user ID according to the circle friend request;

[0090] S503. If the service server receives the cross-circle request, it sends multiple new circle identifiers to the first user terminal and returns to execute S1.

[0091] The rest of Example 2 is the same as Example 1, so it will not be repeated here.

[0092] Embodiment 3:

[0093] Embodiment 3 is further optimized and implemented on the basis of Embodiment 2. When the business server generates the circle friend list, the second user ID is further screened based on the following conditions:

[0094] The frequency of social interactions between the second user ID and the first user ID;

[0095] The activity level of the second user ID in the circle;

[0096] The degree of matching between the interest tag of the second user ID and the interest tag of the first user ID.

[0097] The rest of Example 3 is the same as Example 2, so it will not be repeated here.

[0098] Embodiment 4:

[0099] Example 4 is further optimized and implemented based on Example 2. If the second client logged in by the second user ID receives and agrees to the circle friend request, the friend relationship is added to the system tag knowledge graph through the business server to establish a direct association between the first user ID and the second user ID.

[0100] Further, the business server searches the system tag knowledge graph to determine whether the first user ID and the second user ID are associated with a third-party binding account;

[0101] If the first user ID is associated with a third-party bound account, the business server obtains the third-party bound account of the first user ID and sends it to the second client; the second client receives the third-party bound account of the first user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface;

[0102] If the second user ID is associated with a third-party bound account, the business server obtains the third-party bound account of the second user ID and sends it to the first user end; the first user end receives the third-party bound account of the second user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface.

[0103] Beneficial effects: By adding friend relationships as edges connecting nodes to the system label knowledge graph to associate the nodes as user IDs at both ends of the edge, it is convenient to establish a clear social network graph for users, which is conducive to improving the potential for subsequent data mining.

[0104] Furthermore, the third-party bound accounts include: social media accounts, email addresses, phone numbers or other external platform accounts that support friend relationships, and the business server calls the corresponding API interface to add them according to different third-party platforms.

[0105] Beneficial effects: Simplify the operational process of cross-platform communication, increase the communication methods between users, and further enhance the social integration of both parties in instant messaging.

[0106] The rest of Example 4 is the same as Example 2, so it will not be repeated here.

[0107] Embodiment 5:

[0108] Embodiment 5 is further optimized and implemented on the basis of Embodiment 1. In S3, the business server calculates the association between the first user ID and each second user ID in the system tag knowledge graph, including:

[0109] A calculation model based on tag weights is used to ensure that the second user ID that best matches the interests of the first user ID is prioritized in the circle friend list.

[0110] Beneficial effects: The calculation model based on tag weights can accurately calculate the interest matching between users, ensure that the most matching circle friends are displayed and recommended first, enhance the intelligence and personalization of recommendations, and help improve the user's instant messaging and making friends experience.

[0111] Furthermore, the label weight calculation model includes setting weights for the following data:

[0112] Similarity between the interest tags of the first user ID and the second user ID;

[0113] The number of circles that the first user ID and the second user ID are in at the same time;

[0114] The number of activities jointly participated by the first user ID and the second user ID;

[0115] The historical interaction frequency and time interval between the first user ID and the second user ID.

[0116] Beneficial effect: By setting weights for multi-dimensional data, the accuracy of the recommendation algorithm is further improved, providing users with more suitable instant social communication partners.

[0117] The rest of Example 5 is the same as Example 1, so it will not be repeated here.

[0118] Embodiment 6:

[0119] Embodiment 6 is implemented on the basis of any one of embodiments 1-5, and the nodes of the system tag knowledge graph include: one or more of interest tags, user IDs, third-party bound accounts, circle IDs, and activity tags.

[0120] Beneficial effects: Enhancing the comprehensiveness and complexity of the system label knowledge graph helps to more accurately identify and match user interests.

[0121] Furthermore, in S4, the invitation to join the circle also includes real-time basic information of the circle, and the real-time basic information includes: the number of members, the number of active members, discussion topics, and active discussion topics.

[0122] Beneficial effects: Adding real-time basic information to the invitation to join a circle allows users to have a basic and intuitive understanding of the circle situation when they decide to join the circle, improves the transparency and amount of information in circle matching, and enhances users' desire to select information and explore.

[0123] The rest of Example 6 is the same as any one of Examples 1-5, so it will not be repeated here.

[0124] Embodiment 7:

[0125] Embodiment 7 provides a social circle adding system, the system comprising:

[0126] Acquisition module: used for the first user terminal logged in by the first user ID, acquiring the first user ID and a selected circle identifier and sending them to the business server; wherein the circle identifier includes: circle IDs directly associated with a plurality of second user IDs;

[0127] Search module: used to match the circle ID with the system tag knowledge graph in the database through the business server, generate a circle entry invitation corresponding to the circle ID, and search for several second user IDs associated with the circle ID in the system tag knowledge graph;

[0128] Generation module: used to calculate the correlation between the first user ID and each second user ID in the system tag knowledge graph through the business server, and arrange the second user IDs from high to low according to the correlation, and generate a circle friend list;

[0129] Sending module: used for the first user terminal to receive the circle-joining invitation and circle-friend list sent by the business server, and to perform one of the following actions according to the operation input by the first user terminal:

[0130] a. Send a circle entry request and / or circle member request to the business server;

[0131] b. Send circle friend requests and / or cross-circle requests to the business server.

[0132] Furthermore, an adding module is also included, and the adding module is specifically used for:

[0133] A first adding module is used to determine whether a circle entry request is received, and if the business server receives the circle entry request, send the main page content of the circle to the first user terminal according to the circle entry request;

[0134] A second adding module is used to determine whether the circle friend request is received, and if the business server receives the circle friend request, send the circle friend request to the second client logged in by the corresponding second user ID according to the circle friend request;

[0135] The third adding module is used to determine whether the cross-circle request is received. If the service server receives the cross-circle request, it sends a plurality of new circle identifiers to the first user terminal and sends them to the acquisition module.

[0136] Furthermore, the generating module is also used for the business server to further filter the second user ID based on the following conditions when generating the circle friend list:

[0137] The frequency of social interactions between the second user ID and the first user ID;

[0138] The activity level of the second user ID in the circle;

[0139] The degree of matching between the interest tag of the second user ID and the interest tag of the first user ID.

[0140] If the second client logged in by the second user ID receives and agrees to the circle friend request, the friend relationship is added to the system tag knowledge graph through the business server to establish a direct association between the first user ID and the second user ID.

[0141] Furthermore, the search module is further used to: search the system tag knowledge graph through the business server to determine whether the first user ID and the second user ID are associated with a third-party binding account;

[0142] Determine whether the first user ID is associated with a third-party binding account. If the first user ID is associated with a third-party binding account, the business server obtains the third-party binding account of the first user ID and sends it to the second client; the second client receives the third-party binding account of the first user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface;

[0143] Determine whether the second user ID is associated with a third-party binding account. If the second user ID is associated with a third-party binding account, the business server obtains the third-party binding account of the second user ID and sends it to the first user end; the first user end receives the third-party binding account of the second user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface.

[0144] Furthermore, the third-party binding account includes: a social media account, an email address, a phone number, or other external platform accounts that support friend relationships, and the business server calls the corresponding API interface to add according to different third-party platforms.

[0145] Furthermore, in the generation module, the business server calculates the association between the first user ID and each of the second user IDs in the system tag knowledge graph, including:

[0146] A calculation model based on tag weights is used to ensure that the second user ID that best matches the interests of the first user ID is prioritized in the circle of friends list.

[0147] Furthermore, the label weight calculation model includes setting weights for the following data respectively:

[0148] Similarity between the interest tags of the first user ID and the second user ID;

[0149] The number of circles in which the first user ID and the second user ID are simultaneously located;

[0150] The number of activities jointly participated by the first user ID and the second user ID;

[0151] The historical interaction frequency and time interval between the first user ID and the second user ID.

[0152] Furthermore, in the search module and the generation module, the nodes of the system tag knowledge graph include: one or more of interest tags, user IDs, third-party bound accounts, circle IDs, and activity tags;

[0153] In the sending module, the invitation to join the circle also includes the real-time basic information of the circle, and the real-time basic information includes: the number of members, the number of active members, discussion topics, and active discussion topics.

[0154] Those skilled in the art will appreciate that the accompanying drawings are merely schematic diagrams of a preferred implementation scenario, and the modules or processes in the accompanying drawings are not necessarily required for implementing the present invention.

[0155] Those skilled in the art will appreciate that the modules in the device in the implementation scenario can be distributed in the device in the implementation scenario according to the implementation scenario description, or can be changed accordingly and located in one or more devices different from the implementation scenario. The modules in the above implementation scenario can be combined into one module, or can be further split into multiple sub-modules.

[0156] The above serial numbers of the present invention are only for description and do not represent the advantages or disadvantages of the implementation scenarios.

[0157] The above disclosure is only a few specific implementation scenarios of the present invention, but the present invention is not limited thereto, and any changes that can be conceived by those skilled in the art should fall within the protection scope of the present invention.

Claims

1. A method for adding a social circle, characterized in that: The method comprises: S1. The first user terminal logged in by the first user ID obtains the first user ID and a selected circle identifier and sends it to the business server; wherein the circle identifier includes: a circle ID directly associated with a number of second user IDs; S2. Matching the circle ID with the system tag knowledge graph in the database through the business server, generating a circle entry invitation corresponding to the circle ID, and searching the system tag knowledge graph for several second user IDs associated with the circle ID; S3. The business server calculates the relevance between the first user ID and each of the second user IDs in the system tag knowledge graph, and arranges the second user IDs from high to low according to the relevance to generate a circle friend list; S4. The first user terminal receives the circle-joining invitation and the circle-friend list sent by the service server, and performs one of the following actions according to the operation input by the first user terminal: a. Sending a circle entry request and / or circle friend request to the business server; b. Sending circle friend requests and / or cross-circle requests to the service server; S5. The S5 specifically includes: S501. If the business server receives a circle entry request, it sends the main page content of the circle to the first user terminal according to the circle entry request; S502. If the business server receives the circle friend request, it sends the circle friend request to the second client logged in by the corresponding second user ID according to the circle friend request; S503. If the business server receives the cross-circle request, it sends a plurality of new circle identifiers to the first user terminal, and returns to execute S1; The method further comprises: When the business server generates the circle friend list, the second user ID is further screened based on the following conditions: The frequency of social interactions between the second user ID and the first user ID; The activity level of the second user ID in the circle; the degree of matching between the interest tag of the second user ID and the interest tag of the first user ID; If the second client logged in by the second user ID receives and agrees to the circle friend request, the friend relationship is added to the system tag knowledge graph through the business server to establish a direct association between the first user ID and the second user ID.

2. The method for adding a social circle according to claim 1, characterized in that: The business server searches the system tag knowledge graph to determine whether the first user ID and the second user ID are associated with a third-party binding account; If the first user ID is associated with a third-party binding account, the business server obtains the third-party binding account of the first user ID and sends it to the second client; the second client receives the third-party binding account of the first user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client friend adding interface; If the second user ID is associated with a third-party bound account, the business server obtains the third-party bound account of the second user ID and sends it to the first user terminal; The first user terminal receives the third-party bound account of the second user ID, copies it to the clipboard, and applies to the business server to call the third-party platform to add a friend API interface, and jumps to the third-party client to add a friend interface.

3. The method for adding a social circle according to claim 2, characterized in that: The third-party binding account includes: a social media account, an email address, a phone number, or other external platform accounts that support friend relationships. The business server calls the corresponding API interface to add according to different third-party platforms.

4. The method for adding a social circle according to claim 1, characterized in that: In S3, the business server calculates the association between the first user ID and each of the second user IDs in the system tag knowledge graph, including: A calculation model based on tag weights is used to ensure that the second user ID that best matches the interests of the first user ID is prioritized in the circle of friends list.

5. The method for adding a social circle according to claim 4, characterized in that: The label weight calculation model includes setting weights for the following data: Similarity between the interest tags of the first user ID and the second user ID; The number of circles in which the first user ID and the second user ID are simultaneously located; The number of activities jointly participated by the first user ID and the second user ID; The historical interaction frequency and time interval between the first user ID and the second user ID.

6. The method for adding a social circle according to claim 1, characterized in that: The nodes of the system tag knowledge graph include: one or more of interest tags, user IDs, third-party bound accounts, circle IDs, and activity tags; In S4, the invitation to join the circle also includes real-time basic information of the circle, and the real-time basic information includes: the number of members, the number of active members, discussion topics, and active discussion topics.

7. A social circle system, characterized in that: The system comprises: Acquisition module: used for the first user terminal logged in by the first user ID, acquiring the first user ID and a selected circle identifier and sending them to the service server; wherein the circle identifier includes: circle IDs directly associated with a plurality of second user IDs; Search module: used to match the circle ID with the system tag knowledge graph in the database through the business server, generate a circle entry invitation corresponding to the circle ID, and search for several second user IDs associated with the circle ID in the system tag knowledge graph; A generation module: used to calculate the relevance between the first user ID and each of the second user IDs in the system tag knowledge graph through the business server, and arrange the second user IDs from high to low according to the relevance to generate a circle friend list; The sending module is used for the first user terminal to receive the invitation to join the circle and the list of circle friends sent by the business server, and to perform one of the following actions according to the operation input by the first user terminal: a. Sending a circle entry request and / or circle friend request to the business server; b. Sending circle friend requests and / or cross-circle requests to the service server; It also includes an adding module, which is specifically used for: A first adding module is used to determine whether a circle entry request is received, and if the business server receives the circle entry request, send the main page content of the circle to the first user terminal according to the circle entry request; A second adding module is used to determine whether the circle friend request is received, and if the business server receives the circle friend request, send the circle friend request to the second client logged in by the corresponding second user ID according to the circle friend request; A third adding module is used to determine whether the cross-circle request is received, and if the service server receives the cross-circle request, send a plurality of new circle identifiers to the first user terminal and send them to the acquisition module; The generating module is further configured to filter the second user ID based on the following conditions when the business server generates the circle friend list: The frequency of social interactions between the second user ID and the first user ID; The activity level of the second user ID in the circle; the degree of matching between the interest tag of the second user ID and the interest tag of the first user ID; If the second client logged in by the second user ID receives and agrees to the circle friend request, the business server adds a friend relationship to the system tag knowledge graph to establish a direct association between the first user ID and the second user ID.

Images