Id merging method and apparatus, server, and computer readable storage medium

Abstract

The application provides an ID merging method and device, a server and a computer readable storage medium. The ID merging method comprises the following steps: obtaining a first user ID to be merged and an associated user ID of the first user ID; determining any one first user ID as a target first user ID, and determining whether there is a second user ID matched with the target first user ID according to the associated user ID of the target first user ID; and if there is a second user ID matched with the target first user ID, merging the target first user ID, the second user ID, the associated user ID of the target first user ID and the associated user ID of the second user ID. The ID merging method provided by the application solves the problem that integration cannot be performed across user IDs by merging the matched user IDs.

Description

Technical Field

[0001] This application relates to the field of computer big data technology, specifically to an ID merging method, apparatus, server, and computer-readable storage medium. Background Technology

[0002] Most current user association solutions in big data analytics systems divide all user IDs into two categories for association. One category is collectively called Device ID, which is usually the identifier of the device, such as the AndroidID of an Android system or the cookie_id of a web page. This can be obtained by calling the relevant system interface or using a random algorithm before a user registers / logs in. The other category is collectively called Login ID, which is usually a unique ID that identifies an actual user in the business system. This ID can be obtained by calling the business system interface after a user registers / logs in. Then, the system associates the Login ID and Device ID with the user.

[0003] However, in scenarios involving user association across multiple business lines, different business lines are independent, and existing system association algorithms do not support associating login IDs corresponding to multiple business lines. In other words, it cannot handle the association of login IDs for the same user across different business lines in a multi-business scenario. Summary of the Invention

[0004] This application provides an ID merging method that solves the problem of not being able to integrate across user IDs by merging matching user IDs.

[0005] Firstly, this application provides an ID merging method, the method comprising:

[0006] Obtain the first user ID to be merged and the associated user ID of the first user ID;

[0007] Identify any first user ID as the target first user ID, and determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID;

[0008] If a second user ID exists that matches the target first user ID, the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID are merged.

[0009] In some embodiments of this application, obtaining the first user ID to be merged and the associated user ID of the first user ID includes:

[0010] Retrieve each user ID, and each user ID corresponds to an associated user ID;

[0011] Based on preset filtering conditions and the associated user IDs corresponding to each user ID, each user ID is filtered to obtain the first user ID to be merged and the associated user IDs of the first user ID.

[0012] In some embodiments of this application, obtaining each user ID includes:

[0013] Obtain each initial user ID, and each initial user ID corresponds to an associated user ID;

[0014] Check whether the ID naming of each initial user ID conforms to the ID naming rules, and determine the initial user ID that conforms to the ID naming rules as the user ID.

[0015] In some embodiments of this application, the step of filtering each user ID according to preset filtering conditions and the associated user IDs corresponding to each user ID to obtain the first user ID to be merged and the associated user IDs of the first user ID includes:

[0016] Based on the ID type of the associated user ID corresponding to each user ID, determine the theoretical number of associated user IDs corresponding to each user ID;

[0017] Determine the actual number of associated user IDs corresponding to each user ID;

[0018] The user IDs whose actual number of associated user IDs matches the theoretical number are determined as the first user IDs, so as to obtain the first user IDs to be merged and the associated user IDs of the first user IDs.

[0019] In some embodiments of this application, determining whether there exists a second user ID matching the target first user ID based on the associated user ID of the target first user ID includes:

[0020] Determine the merging priority between the target first user ID and each second user ID;

[0021] Based on the merging priority of each second user ID with the target first user ID, a second user ID matching the first user ID is obtained.

[0022] In some embodiments of this application, determining the merging priority between the target first user ID and each of the second user IDs includes:

[0023] Obtain the first behavior data of the first user ID and obtain the second behavior data corresponding to each of the second user IDs;

[0024] Determine the first behavioral feature of the first behavioral data and determine the second behavioral feature of each of the second behavioral data;

[0025] The similarity between the first behavioral feature and each of the second behavioral features is determined to obtain multiple similarities, with one similarity corresponding to one first behavioral feature and one second behavioral feature.

[0026] Based on the multiple similarities, the merging priority between the target first user ID and each second user ID is determined.

[0027] In some embodiments of this application, after merging the first user ID, the second user ID, the associated user ID of the first user ID, and the associated user ID of the second user ID, the method further includes:

[0028] The merged user IDs are stored in a pre-defined ID storage system;

[0029] Determine the second user ID that does not match the first user ID;

[0030] Create a corresponding ID sequence for the second user ID that does not match the first user ID;

[0031] The ID sequence is stored in the ID storage system.

[0032] Secondly, this application also provides an ID merging apparatus, the apparatus comprising:

[0033] The acquisition module is used to acquire the first user ID to be merged and the associated user ID of the first user ID;

[0034] The determination module is used to determine any first user ID as a target first user ID, and to determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID;

[0035] The merging module is used to merge the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID if there is a second user ID that matches the target first user ID.

[0036] In some embodiments of this application, the acquisition module is specifically used for:

[0037] Retrieve each user ID, and each user ID corresponds to an associated user ID;

[0038] Based on preset filtering conditions and the associated user IDs corresponding to each user ID, each user ID is filtered to obtain the first user ID to be merged and the associated user IDs of the first user ID.

[0039] In some embodiments of this application, the acquisition module is further configured to:

[0040] Obtain each initial user ID, and each initial user ID corresponds to an associated user ID;

[0041] Check whether the ID naming of each initial user ID conforms to the ID naming rules, and determine the initial user ID that conforms to the ID naming rules as the user ID.

[0042] In some embodiments of this application, the acquisition module is further configured to:

[0043] Based on the ID type of the associated user ID corresponding to each user ID, determine the theoretical number of associated user IDs corresponding to each user ID;

[0044] Determine the actual number of associated user IDs corresponding to each user ID;

[0045] The user IDs whose actual number of associated user IDs matches the theoretical number are determined as the first user IDs, so as to obtain the first user IDs to be merged and the associated user IDs of the first user IDs.

[0046] In some embodiments of this application, the determining module is specifically used for:

[0047] Determine the merging priority between the target first user ID and each second user ID;

[0048] Based on the merging priority of each second user ID with the target first user ID, a second user ID matching the first user ID is obtained.

[0049] In some embodiments of this application, the determining module is further configured to:

[0050] Obtain the first behavior data of the first user ID and obtain the second behavior data corresponding to each of the second user IDs;

[0051] Determine the first behavioral feature of the first behavioral data and determine the second behavioral feature of each of the second behavioral data;

[0052] The similarity between the first behavioral feature and each of the second behavioral features is determined to obtain multiple similarities, with one similarity corresponding to one first behavioral feature and one second behavioral feature.

[0053] Based on the multiple similarities, the merging priority between the target first user ID and each second user ID is determined.

[0054] In some embodiments of this application, the ID merging device may further include a storage module, which is specifically used for:

[0055] The merged user IDs are stored in a pre-defined ID storage system;

[0056] Determine the second user ID that does not match the first user ID;

[0057] Create a corresponding ID sequence for the second user ID that does not match the first user ID;

[0058] The ID sequence is stored in the ID storage system.

[0059] Thirdly, this application also provides a server, the server including a processor, a memory, and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the steps in any of the ID merging methods described above.

[0060] Fourthly, this application also provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the steps in any of the ID merging methods described above.

[0061] The ID merging method provided in this application determines the probability that a first user ID and a second user ID are the same user by determining the degree of matching between them. When it can be determined that a second user ID matches the first user ID, it can be determined that the users corresponding to the first user ID and the second user ID are the same actual person. At this point, the associated user IDs corresponding to the first user ID and the associated user IDs corresponding to the second user ID are merged, thus solving the problem of not being able to merge across user IDs. Attached Figure Description

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

[0063] Figure 1 This is a schematic diagram of a scenario for the ID merging system provided in the embodiments of this application;

[0064] Figure 2This is a flowchart illustrating one embodiment of the ID merging method in this application.

[0065] Figure 3 This is a schematic diagram of a functional module of the ID merging device in an embodiment of this application;

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

[0067] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0068] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0069] In this application, the term "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. Furthermore, it is understood that in the specific embodiments of this application, user information, user data, and other related data are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0070] To enable any person skilled in the art to implement and use this application, the following description is provided. In this description, details are set forth for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be implemented without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0071] This application provides an ID merging method, apparatus, device, and storage medium, which will be described in detail below.

[0072] Please see Figure 1 , Figure 1 This is a schematic diagram illustrating a scenario of the ID merging method provided in an embodiment of this application. The ID merging system may include a server 100 and a storage device 200, which are communicatively connected. The server 100 can transmit data to the storage device 200, and the storage device 200 can also transmit data to the server 100. Figure 1 The server 100 can process the ID merging method mentioned in this application based on the ID information stored in the storage device 200.

[0073] In this embodiment, server 100 includes, but is not limited to, a standalone server, or a server network or server cluster, including, but not limited to, computers, network hosts, single network servers, multiple network server sets, or cloud servers composed of multiple servers. The cloud server can be composed of a large number of computers or network servers based on cloud computing.

[0074] In the embodiments of this application, the server 100 and the storage device 200 can communicate through any communication method, including but not limited to mobile communication based on the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), and Worldwide Interoperability for Microwave Access (WiMAX), or computer network communication based on the TCP / IP Protocol Suite (TCP / IP) and User Datagram Protocol (UDP).

[0075] Those skilled in the art will understand that Figure 1 The application environment shown is merely one application scenario of the solution in this application and does not constitute a limitation on the application scenario of the solution in this application. Other application environments may include those that are more specific to this application. Figure 1 The number of servers and backend devices shown is more or less, for example Figure 1 Only one server or backend device is shown in the diagram. The ID merging system may also include one or more other servers and servers that can process data, which are not specified here.

[0076] It should be noted that, Figure 1The schematic diagram of the ID merging system shown is merely an example. The ID merging system and scenario described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will know, with the evolution of ID merging systems and the emergence of new business scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0077] like Figure 2 As shown, Figure 2 This is a flowchart illustrating one embodiment of the ID merging method in this application. The ID merging method may include the following steps 201-203:

[0078] 201. Obtain the first user ID to be merged and the associated user ID of the first user ID.

[0079] In this embodiment, the first user ID can be a user ID from any business line. Furthermore, since a user creates a corresponding user ID when using a specific business, such as a nickname, and during registration, the user also fills in information related to that nickname, such as a mobile phone number, email address, or binds a WeChat account to that nickname, etc., in this embodiment, for ease of understanding, the first user ID can be understood as a user nickname, and the associated user ID can be understood as a mobile phone number, email address, or bound WeChat account, etc. It should be noted that the first user ID can be understood not only as a user nickname, but also that the associated user ID can be understood not only as related user information such as mobile phone numbers, email addresses, or WeChat accounts; the specific details can be determined according to the actual situation, and no specific limitation is made here.

[0080] In addition, after a user registers for a specific business, the server will receive the relevant user information for that specific business. At this time, the user's user ID and the associated user ID can be stored. When it is necessary to merge user IDs, the user ID and the associated user ID can be retrieved from the stored device.

[0081] 202. Determine any first user ID as the target first user ID, and based on the associated user IDs of the target first user ID, determine whether there exists a second user ID that matches the target first user ID.

[0082] Based on the steps above, since there may be multiple business types, each business line can correspond to at least one first user ID. Even within the same business line, multiple first user IDs may be provided. Therefore, after obtaining multiple first user IDs, in order to merge them, it is necessary to determine which first user IDs are most likely to belong to the same actual user. When it can be determined that several specific first user IDs can belong to the same actual user, the associated user IDs corresponding to these specific first user IDs can be merged. Therefore, to perform the merging, any one of the many first user IDs can be determined as a baseline user ID, i.e., the target first user ID. Then, the other first user IDs besides the target first user ID can be determined as second user IDs.

[0083] Furthermore, once the target first user ID and second user ID are determined, the second user ID that matches the target first user ID can be determined through the associated user ID corresponding to the target first user ID and the associated user ID corresponding to the second user ID.

[0084] Specifically, the number of first IDs associated with the target first user ID can be determined, and then the number of second IDs associated with the second user ID can be determined. If the sum of the number of first IDs and the number of second IDs is equal to or less than a preset threshold, then the second user ID corresponding to that number of second IDs can be determined as a matching second user ID of the target first user ID. For example: Suppose there is a target first user ID-A, and the number of associated user IDs of this target first user ID is 1; and two second user IDs-B and C, where the number of associated user IDs of second user ID-B is also 1, and the number of associated user IDs of second user ID-C is 7. If the threshold is 5, then the second user ID C can be determined as a mismatched second user ID.

[0085] Alternatively, we can determine the first ID type of the associated user ID corresponding to the target first user ID, and then determine the second ID type of the associated user ID corresponding to the second user ID. If the two ID types are different, then the second user ID corresponding to the second ID type is the second user ID that matches the target first user ID. For example: Suppose there is a target first user ID-A, and the associated user ID of this target first user ID is of type mobile phone. There are also two second user IDs-B and C. The associated user ID of second user ID-B is of type email, and the associated user ID of second user ID-C is of type mobile phone. In this case, we can also determine that the second user ID of second user ID C is a mismatched second user ID.

[0086] Alternatively, it can be determined whether there is a common associated user ID between the target first user ID and the second user ID. For example, if the target first user ID has an associated user ID that is mobile phone number A, and a second user ID also has an associated user ID that is the same as mobile phone number A, then it can be determined that the second user ID is the second user ID that matches the target first user ID.

[0087] 203. If there is a second user ID that matches the target first user ID, merge the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID.

[0088] Based on the above steps, when it is determined that a target first user ID has a second user ID, the associated user IDs of the two can be merged. For example: Suppose there is a target first user ID-A, whose associated user ID is a mobile phone number, and there is also a second user ID-B, whose associated user ID is an email address. In this case, the email address associated with the second user ID is merged with the mobile phone number associated with the target first user ID, resulting in a merged user ID that is associated with both a mobile phone ID and an email address. Alternatively, suppose there is a target first user ID-A, whose associated user IDs are a mobile phone number and a WeChat account, and there is also a second user ID-B, whose associated user IDs are an email address and a mobile phone number. If the mobile phone numbers of the two user IDs are the same, then the target first user ID is merged with the remaining associated user IDs of the second user ID, resulting in a merged user ID that can include a mobile phone number, an email address, and a WeChat account.

[0089] It should be noted that after each user ID is merged, there may be some remaining first user IDs that have not been merged. In this case, according to the merging method in this embodiment, a target first user ID is selected from the remaining first user IDs, and the remaining first user ID is used as the second user ID. This process is repeated until all user IDs are merged.

[0090] The ID merging method provided in this application determines the probability that a first user ID and a second user ID are the same user by determining the degree of matching between them. When it can be determined that a second user ID matches the first user ID, it can be determined that the users corresponding to the first user ID and the second user ID are the same actual person. At this point, the associated user IDs corresponding to the first user ID and the associated user IDs corresponding to the second user ID are merged, thus solving the problem of not being able to merge across user IDs.

[0091] To better implement the embodiments of this application, in one embodiment of this application, obtaining the first user ID to be merged and the associated user ID of the first user ID includes:

[0092] Obtain each user ID, and each user ID has a corresponding associated user ID; based on the preset filtering conditions and the associated user IDs of each user ID, filter each user ID to obtain the first user ID to be merged and the associated user IDs of the first user ID.

[0093] The above embodiments provide a scheme for merging different user IDs. However, to improve the efficiency of obtaining a second user ID that matches the target first user ID, some filtering steps can be performed to reduce the number of first user IDs. When the number of first user IDs is reduced, the number of second user IDs can also be reduced, thus reducing the computational load and improving the acquisition efficiency.

[0094] Specifically, the number of associated user IDs corresponding to each user ID can be determined. When the number of associated user IDs exceeds a certain filtering threshold, it indicates that the density of associated user IDs for that user ID is high, and further merging is unnecessary. In this case, user IDs whose associated user IDs exceed the filtering threshold can be removed. For example, if a user ID corresponds to 7 associated user IDs, and the filtering threshold is 5, then the number of associated user IDs for that user ID has exceeded the threshold of 5, and this user ID can be removed. If the number of associated user IDs for the remaining user IDs does not exceed the filtering threshold of 5, then the remaining user IDs can be considered the first user ID.

[0095] To better implement the embodiments of this application, in one embodiment of this application, obtaining each user ID includes:

[0096] Obtain each initial user ID, and each initial user ID corresponds to an associated user ID; check whether the ID naming of each initial user ID conforms to the ID naming rules, and determine the initial user ID that conforms to the ID naming rules as the user ID.

[0097] To further improve the efficiency of obtaining the first user ID to be merged, filtering can be performed on each user ID during the selection process. The user IDs that are not filtered are the initial user IDs. The initial user IDs can be pre-stored in the corresponding storage device or can be user IDs sent by the user in real time; the specific method is not limited here.

[0098] Specifically, upon obtaining each initial user ID and its corresponding associated user ID, the process first checks if any illegal characters exist in the initial user ID. If illegal characters are found, the initial user ID can be directly filtered. If no illegal characters are found, the associated user IDs corresponding to the initial user IDs are then checked to see if they conform to the specified rules. For example, if a mobile phone number is an 11-digit Arabic numeral, and the detected associated user ID is a mobile phone number that is not 11 digits, then that initial user ID is also a target for filtering. After filtering, it is determined which initial user IDs are eligible for filtering.

[0099] To better implement the embodiments of this application, in one embodiment, each user ID is filtered according to preset filtering conditions and its corresponding associated user IDs to obtain a first user ID to be merged and its associated user IDs, including:

[0100] Based on the ID type of the associated user IDs corresponding to each user ID, determine the theoretical number of associated user IDs corresponding to each user ID; determine the actual number of associated user IDs corresponding to each user ID; determine the user IDs whose actual number of associated user IDs matches the theoretical number as the first user ID, so as to obtain the first user ID to be merged and the associated user IDs of the first user ID.

[0101] The above embodiments provide a filtering method. In order to improve the filtering effect, this application embodiment provides a filtering method based on the type of associated user ID and the number of associated user IDs.

[0102] Specifically, the ID type of the associated user IDs corresponding to each user ID can be determined in advance, and then the actual number of IDs under that ID type can be determined. Filtering can then be performed based on the actual number of IDs. For example: Suppose there are three user IDs: User ID-A, User ID-B, User ID-C, and User ID-D. If the associated user ID type for User ID-A is a mobile phone number, and there is only one such mobile phone number; if the associated user ID type for User ID-B is an email address, and there is only one such email address; and if the associated user ID type for User ID-C is also a mobile phone number, and there is only one such mobile phone number; and if the associated user ID for User ID-D is a WeChat account, then multiple filtering thresholds can be set: a threshold of 2 for email + mobile phone, a threshold of 1 for mobile phone + mobile phone, a threshold of 2 for email + WeChat account, and a threshold of 2 for mobile phone + WeChat account.

[0103] At this point, User ID-A + User ID-B meets the threshold of email + mobile phone, so the result is 2; User ID-A + User ID-C does not meet the threshold of mobile phone + mobile phone, so the result is 1; User ID-C + User ID-B meets the threshold of email + mobile phone; User ID-A + User ID-D meets the threshold of mobile phone + WeChat ID, so the result is 2; and User ID-B + User ID-D meets the threshold of email + mobile phone. Therefore, User ID-A, User ID-B, and User ID-D can be determined as the first user ID; or User ID-C, User ID-B, and User ID-D can be determined as the first user ID.

[0104] Furthermore, determining whether a user ID is the primary user ID can be done by identifying the ID type and actual number of associated user IDs. For example, suppose we can set a limit of three mobile phone numbers associated with a user ID. If a user ID is associated with five mobile phone numbers, then this user does not meet the requirements for ID type and number. In this case, we can first identify this user ID as a non-primary user ID. After filtering in this way, we can obtain the non-primary user IDs, and then use the remaining IDs as the primary user IDs. Alternatively, we can perform pairwise checks on the remaining user IDs based on type and number before determining the specific primary user ID; the specific method is not limited here.

[0105] Of course, in reality, the number of user IDs obtained is far more than four. As the number of user IDs increases, the method in this embodiment is still applicable. Furthermore, since a user ID can obtain a corresponding associated user ID during registration, obtaining the associated user IDs for each user ID is the same as in the above embodiment, and will not be repeated here. In addition, the filtering steps in this embodiment are not limited to determining the first user ID by ID type and ID quantity, but also include other methods that can implement any filtering method, which are not limited here.

[0106] To better implement the embodiments of this application, in one embodiment, determining whether there exists a second user ID matching the target first user ID based on the associated user ID of the target first user ID includes:

[0107] Determine the merging priority between the target first user ID and each second user ID; based on the merging priority between each second user ID and the target first user ID, obtain the second user ID that matches the first user ID.

[0108] The above embodiments provide a method for matching based on quantity or type. However, there is also a situation where there are multiple second users that meet the matching criteria based on quantity or type. For example, if the target first user ID-A has no associated user ID, and there are two matching second user IDs-B and-C, if second user ID-B includes an associated user ID of a mobile phone type, and second user ID-C also includes an associated user ID of a mobile phone type, and only one mobile phone number can be merged in the end, then it is impossible to determine how to merge second user ID-B and second user ID-C with the target first user ID-A. Therefore, it is necessary to determine the merging priority between second user ID-B and target first user ID-A, and the merging priority between second user ID-C and target first user ID-A. Only after determining the merging priority between each pair can it be determined which second user ID will be merged with the target first user ID.

[0109] Specifically, the priority between pairs of user IDs can be determined automatically by the system. For example, the system can automatically generate a random number for each pair of user IDs, and the merging priority is determined by the magnitude of the random number; the larger the random number, the higher the priority. The second user ID with the highest merging priority is then selected as the matching second user ID. Alternatively, the merging priority can be determined manually. Once manually determined, the relevant staff can input the determined priority into the system, and the system will then merge the pairs according to the manually input priority.

[0110] To better implement the embodiments of this application, in one embodiment of this application, determining the merging priority between the target first user ID and each second user ID includes:

[0111] Obtain the first behavior data of the first user ID and the second behavior data corresponding to each second user ID; determine the first behavior feature of the first behavior data and the second behavior feature of each second behavior data; determine the similarity between the first behavior feature and each second behavior feature respectively, and obtain multiple similarities, with one similarity corresponding to one first behavior feature and one second behavior feature; determine the merging priority between the target first user ID and each second user ID based on the multiple similarities.

[0112] To further determine the merging priority between pairs of users, we can obtain the behavioral data corresponding to the user IDs and calculate the similarity of the user behavioral data to determine the corresponding merging priority.

[0113] Specifically, since the first user ID originates from a specific business line, and users generate corresponding business data or behavioral data when using those business lines, the system can collect behavioral data corresponding to each user ID. By comparing the similarity between the behavioral data, the higher the similarity, the higher the merging priority.

[0114] Specifically, assuming business line A is music software A, the behavioral data of the first user ID-A corresponding to music software A may include: rock songs account for 90% of the collected songs; business line B is music software B, and the behavioral data of the second user ID-B corresponding to music software B may include: rock songs account for 89% of the collected songs; business line C is music software C, and the behavioral data of the second user ID-C corresponding to music software C may include: rock songs account for 50% of the collected songs. In this case, 90%, 89%, and 50% can be considered behavioral characteristics corresponding to the behavioral data. Comparing these behavioral characteristics reveals that 90% and 89% are extremely similar, while 90% and 50% are dissimilar. Therefore, the merging priority of the first user ID-A and the second user ID-B is higher than that of the first user ID-A and the second user ID-C. If, at this point, the associated user IDs of both the second user ID-B and the second user ID-C only include phone numbers, then the first user ID-A and the second user ID-B can be merged.

[0115] It should be noted that the data listed in the embodiments of this application are only for ease of understanding. In actual situations, the methods for determining behavioral data and behavioral characteristics can be set according to the actual situation, and no specific limitations are made here.

[0116] To better implement the embodiments of this application, in one embodiment of this application, after merging the first user ID, the second user ID, the associated user ID of the first user ID, and the associated user ID of the second user ID, the method further includes:

[0117] The merged user IDs are stored in a preset ID storage system; a second user ID that does not match the first user ID is identified; a corresponding ID sequence is created for the second user ID that does not match the first user ID; and the ID sequence is stored in the ID storage system.

[0118] The above embodiments illustrate an ID merging scheme. After user IDs are merged, among the numerous first user IDs, there may be second user IDs that have not been merged. In this case, the unmerged second user IDs can be considered as independent actual users. Thus, the unmerged second user IDs can be designated as entirely new users, i.e., a completely new ID sequence can be created to represent this second user ID as a new user. Then, the merged user IDs and the second user IDs with the newly created ID sequence are stored for subsequent modification, association, and other operations.

[0119] Furthermore, embodiments of this application may also provide a comprehensive ID merging scheme, which is shown below:

[0120] Assume the user table already contains the following data:

[0121]

[0122]

[0123] The corresponding user configuration is simplified as follows:

[0124]

[0125] Assuming user A1 is linked to mobile number 131xxx in the corresponding business line, the corresponding data will be constructed as follows:

[0126]

[0127] After the above data is sent to the system associated with this ID, users 1 and 2 will be merged into one user. At this time, the user table will look like this:

[0128]

[0129] At this point, we can see that by using the mobile phone number as an ID, users from business line A and business line B can be successfully identified and merged into one user, thus realizing cross-business line user association.

[0130] Assuming user B2 manually binds the email address a@a.com within the business line, the corresponding data will be constructed as follows:

[0131]

[0132] After the above data is sent to the system associated with this ID, users with IDs 1 and 3 will be merged into one user. At this time, the user table will look like this:

[0133]

[0134] At this point, it can also be seen that, using the email address as an ID, users from business line B and business line C can be successfully identified and merged into one user.

[0135] In the above scenario, user association across business lines was achieved through mobile phone numbers and email addresses. In actual use, any ID in the system can be associated with / merged with existing users, ultimately achieving automatic identification and association of login user IDs from multiple business lines.

[0136] To better implement the ID merging method in the embodiments of this application, an ID merging device is also provided in the embodiments of this application, such as... Figure 3 As shown, the device 300 includes:

[0137] The acquisition module 301 is used to acquire the first user ID to be merged and the associated user ID of the first user ID;

[0138] The determination module 302 is used to determine any first user ID as the target first user ID, and to determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID;

[0139] The merging module 303 is used to merge the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID if there is a second user ID that matches the target first user ID.

[0140] The ID merging device provided in this application obtains a first user ID through an acquisition module 301, and then determines the matching degree between the first user ID and a second user ID through a determination module 302, thereby determining whether the two are likely to be the same user. When it can be determined that a second user ID matches the first user ID, it can be determined that the users corresponding to the first user ID and the second user ID are the same actual person. At this time, the merging module 303 merges the associated user IDs corresponding to the first user ID and the associated user IDs corresponding to the second user ID, thus solving the problem of not being able to merge across user IDs.

[0141] In some embodiments of this application, the acquisition module 301 is specifically used for:

[0142] Retrieve each user ID, and each user ID corresponds to an associated user ID;

[0143] Based on the preset filtering conditions and the associated user IDs corresponding to each user ID, each user ID is filtered to obtain the first user ID to be merged and the associated user IDs of the first user ID.

[0144] In some embodiments of this application, the acquisition module 301 is further configured to:

[0145] Obtain each initial user ID, and each initial user ID corresponds to an associated user ID;

[0146] Check whether the ID naming of each initial user ID conforms to the ID naming rules, and determine the initial user ID that conforms to the ID naming rules as the user ID.

[0147] In some embodiments of this application, the acquisition module 301 is further configured to:

[0148] Based on the ID type of the associated user ID corresponding to each user ID, determine the theoretical number of associated user IDs corresponding to each user ID;

[0149] Determine the actual number of associated user IDs corresponding to each user ID;

[0150] The user IDs whose actual number of associated user IDs matches the theoretical number are determined as the first user IDs, so as to obtain the first user IDs to be merged and the associated user IDs of the first user IDs.

[0151] In some embodiments of this application, the determining module 302 is specifically used for:

[0152] Determine the merging priority between the target first user ID and each second user ID;

[0153] Based on the merging priority of each second user ID with the target first user ID, a second user ID that matches the first user ID is obtained.

[0154] In some embodiments of this application, the determining module 302 is further configured to:

[0155] Obtain the first behavior data for the first user ID and the second behavior data corresponding to each second user ID;

[0156] Determine the first-beginning characteristics of the first-beginning data and the second-beginning characteristics of each second-beginning data;

[0157] The similarity between the first behavioral feature and each of the second behavioral features is determined to obtain multiple similarities, with one similarity corresponding to one first behavioral feature and one second behavioral feature.

[0158] Based on multiple similarities, determine the merging priority between the target first user ID and each second user ID.

[0159] In some embodiments of this application, the ID merging device may further include a storage module, which is specifically used for:

[0160] The merged user IDs are stored in a pre-defined ID storage system;

[0161] Determine the second user ID that does not match the first user ID;

[0162] Create a corresponding ID sequence for the second user ID that does not match the first user ID;

[0163] Store the ID sequence in the ID storage system.

[0164] This application also provides a server, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to implement the steps of any of the ID merging methods in this application. This server integrates any of the ID merging methods provided in this application, such as... Figure 4 As shown, it illustrates a schematic diagram of the server structure involved in an embodiment of this application. Specifically:

[0165] The server may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will understand that... Figure 4 The server structure shown does not constitute a limitation on the server and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0166] in:

[0167] Processor 401 is the control center of the server, connecting various parts of the server through various interfaces and lines. It performs various server functions and processes data by running or executing software programs and / or modules stored in memory 402, and by calling data stored in memory 402, thereby providing overall monitoring of the server. Optionally, processor 401 may include one or more processing cores; processor 401 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. Preferably, processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the aforementioned modem processor may not be integrated into processor 401.

[0168] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the server, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0169] The server also includes a power supply 403 that supplies power to the various components. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 403 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0170] The server may also include an input unit 404, which can be used to receive input numeric or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0171] Although not shown, the server may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the server loads the executable files corresponding to the processes of one or more applications into the memory 402 according to the following instructions, and the processor 401 runs the applications stored in the memory 402 to realize various functions, such as:

[0172] Obtain the first user ID to be merged and the associated user ID of the first user ID;

[0173] Identify any first user ID as the target first user ID, and determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID;

[0174] If a second user ID exists that matches the target first user ID, the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID are merged.

[0175] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0176] Therefore, embodiments of this application provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk, etc. A computer program is stored thereon, and the computer program is loaded by a processor to execute the steps in any of the ID merging methods provided in embodiments of this application. For example, the computer program loaded by the processor can execute the following steps:

[0177] Obtain the first user ID to be merged and the associated user ID of the first user ID;

[0178] Identify any first user ID as the target first user ID, and determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID;

[0179] If a second user ID exists that matches the target first user ID, the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID are merged.

[0180] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the detailed descriptions of other embodiments above, which will not be repeated here.

[0181] In practice, each of the above units or structures can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units or structures, please refer to the previous method embodiments, which will not be repeated here.

[0182] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0183] The above provides a detailed description of an ID merging method and apparatus provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. An ID merging method, characterized in that, The method includes: Obtain the first user ID to be merged and the associated user IDs of the first user ID, and remove the first user ID whose number of associated user IDs exceeds the filtering threshold. Each first user ID is a login user ID of a business line, and the associated user IDs are the relevant user information registered for the corresponding business line. Identify any first user ID as the target first user ID, and determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID; If a second user ID exists that matches the target first user ID, the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID are merged. Determining whether a second user ID matches the target first user ID includes: Determine the first ID type of the associated user ID of the target first user ID, and determine the second ID type of the associated user ID of the second user ID. If the first ID type and the second ID type are different, then determine the second user ID corresponding to the second ID type as the second user ID that matches the target first user ID. The method further includes: Determine the merging priority between the target first user ID and each second user ID; Based on the merging priority of each second user ID with the target first user ID, a second user ID matching the target first user ID is obtained.

2. The ID merging method according to claim 1, characterized in that, The step of obtaining the first user ID to be merged and the associated user ID of the first user ID includes: Retrieve each user ID, and each user ID corresponds to an associated user ID; Based on preset filtering conditions and the associated user IDs corresponding to each user ID, each user ID is filtered to obtain the first user ID to be merged and the associated user IDs of the first user ID.

3. The ID merging method according to claim 2, characterized in that, The process of obtaining each user ID includes: Obtain each initial user ID, and each initial user ID corresponds to an associated user ID; Check whether the ID naming of each initial user ID conforms to the ID naming rules, and determine the initial user ID that conforms to the ID naming rules as the user ID.

4. The ID merging method according to claim 2, characterized in that, The step of filtering each user ID according to preset filtering conditions and the associated user IDs corresponding to each user ID to obtain the first user ID to be merged and the associated user IDs of the first user ID includes: Based on the ID type of the associated user ID corresponding to each user ID, determine the theoretical number of associated user IDs corresponding to each user ID; Determine the actual number of associated user IDs corresponding to each user ID; The user IDs whose actual number of associated user IDs matches the theoretical number are determined as the first user IDs, so as to obtain the first user IDs to be merged and the associated user IDs of the first user IDs.

5. The ID merging method according to claim 1, characterized in that, Determining the merging priority between the target first user ID and each second user ID includes: Obtain the first behavior data of the first user ID and obtain the second behavior data corresponding to each of the second user IDs; Determine the first behavioral feature of the first behavioral data and determine the second behavioral feature of each of the second behavioral data; The similarity between the first behavioral feature and each of the second behavioral features is determined to obtain multiple similarities, with one similarity corresponding to one first behavioral feature and one second behavioral feature. Based on the multiple similarities, the merging priority between the target first user ID and each second user ID is determined.

6. The ID merging method according to claim 1, characterized in that, After merging the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID, the method further includes: The merged user IDs are stored in a pre-defined ID storage system; Determine the second user ID that does not match the first user ID; Create a corresponding ID sequence for the second user ID that does not match the first user ID; The ID sequence is stored in the ID storage system.

7. An ID merging device, characterized in that, The device includes: The acquisition module is used to acquire the first user ID to be merged and the associated user IDs of the first user ID, and to remove the first user ID whose number of associated user IDs exceeds the filtering threshold. Each first user ID is a login user ID of a business line, and the associated user IDs are the relevant user information registered for the corresponding business line. The determination module is used to determine any first user ID as a target first user ID, and to determine whether there is a second user ID that matches the target first user ID based on the associated user ID of the target first user ID; The merging module is used to merge the target first user ID, the second user ID, the associated user ID of the target first user ID, and the associated user ID of the second user ID if there is a second user ID that matches the target first user ID. The determining module is further configured to: determine the first ID type of the associated user ID of the target first user ID, and determine the second ID type of the associated user ID of the second user ID; if the first ID type and the second ID type are different, then determine that the second user ID corresponding to the second ID type is the second user ID that matches the target first user ID. The determining module is further configured to: determine the merging priority between the target first user ID and each second user ID; and obtain a second user ID that matches the target first user ID based on the merging priority between each second user ID and the target first user ID.

8. A server, characterized in that, The server includes a processor, a memory, and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the steps of the ID merging method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is executed by a processor to implement the steps of the ID merging method according to any one of claims 1 to 6.

Images