User information merging methods, devices, equipment, storage media, and program products

Abstract

This application relates to a user information merging method, apparatus, device, storage medium, and program product, belonging to the field of big data technology. The method includes: normalizing the original user information of the users to be merged to obtain target user information; determining the user type of the users to be merged based on the target user information; grouping the users to be merged according to the user type and target user information to obtain at least one target user set; and merging the target user information of the users to be merged in each target user set to obtain general user information for the users to be merged in each target user set. This method can improve the efficiency and quality of user information merging.

Description

Technical Field

[0001] This application relates to the field of big data technology, and in particular to a method, apparatus, device, storage medium, and program product for merging user information. Background Technology

[0002] With the development of big data technology, there are increasingly more application scenarios for merging user information across systems. For example, in the scenario of merging multiple enterprises, it is necessary to merge the user information of different enterprises under their respective systems. However, since each enterprise uses its own user information management system, and each system has its own corresponding user identification method, merging user information across systems will face many problems.

[0003] Currently, merging user information across systems is done manually, which is inefficient and produces low-quality results. Furthermore, over time, a large amount of repetitive customer information needs to be merged, and the existing manual merging method cannot completely solve the problem of merging customer information across systems. Therefore, improving the efficiency and quality of user information merging, and maintaining dynamic merging of user information systems, is an urgent problem to be solved. Summary of the Invention

[0004] Therefore, it is necessary to provide a user information merging method, apparatus, device, storage medium, and program product that can improve the efficiency and quality of user information merging in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a method for merging user information. The method includes:

[0006] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0007] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0008] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0009] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0010] In one embodiment, the users to be merged are grouped according to their user type and target user information to obtain at least one set of target users, including:

[0011] If the user type of the user to be merged is a natural person, then determine whether the user to be merged includes a target user based on the target user information of the user to be merged; where the target user is the user to be merged that needs to have its target user information adjusted.

[0012] If included, the target user information of the target user will be adjusted, and users whose target user information is the same after adjustment will be grouped into a set of target users.

[0013] In one embodiment, if the users to be merged belong to registered users under different systems, then based on the target user information of the users to be merged, it is determined whether the users to be merged include the target user, including:

[0014] Based on the system affiliation information of the registration system corresponding to the user to be merged, determine whether the registration system contains a subsystem; wherein, the system affiliation information of the registration system is recorded in the target user information of the user to be merged;

[0015] If so, then the user to be merged is identified as the target user.

[0016] In one embodiment, adjusting the target user information of the target user includes:

[0017] Based on the number of subsystems contained in the registration system, the target user information of the target user is migrated to obtain the target user information corresponding to each subsystem;

[0018] Adjust the system affiliation information in the target user information corresponding to each subsystem.

[0019] In one embodiment, the users to be merged are grouped according to their user type and target user information to obtain at least one set of target users, including:

[0020] If the user type of the users to be merged is a non-natural person, then the users to be merged with the same first key information will be divided into an initial user set.

[0021] For each initial user set, users with the same second key information are grouped into a target user set;

[0022] The target user information of the users to be merged includes at least one first key piece of information and at least one second key piece of information.

[0023] In one embodiment, the original user information of the users to be merged is normalized to obtain the target user information of the users to be merged, including:

[0024] The original user information of the users to be merged is classified, and the normalization strategy corresponding to each category is determined.

[0025] Based on the normalization strategy corresponding to each category, the original user information of the corresponding category is normalized to obtain the target user information of the users to be merged.

[0026] In one embodiment, the target user information of the users to be merged in each target user set is merged to obtain general user information of the users to be merged in each target user set, including:

[0027] For each target user set, sort the users to be merged in that target user set according to the user identifier information in the target user information of the users to be merged;

[0028] Based on the sorting results, determine the general user information of the users to be merged in the target user set of this group.

[0029] In one embodiment, the method further includes:

[0030] If user information for at least two new users is received, then the at least two new users are grouped to obtain at least one reference user set;

[0031] Compare the user information of each new user in each reference user set with the general user information corresponding to each target user set to determine the target user set corresponding to each new user.

[0032] Each new user is added to the corresponding target user set, and the user information of each new user is adjusted to the general user information of the target user set to which they belong.

[0033] In one embodiment, the user information of each newly added user in each reference user set is compared with the general user information corresponding to each target user set to determine the target user set corresponding to each newly added user, including:

[0034] For each new user in each reference user set, if the user information of the new user is different from the general user information corresponding to each target user set, then determine whether the other new users in the reference user set to which the new user belongs have been identified as the target user set.

[0035] If so, then the target user set corresponding to other users will be used as the target user set corresponding to the newly added user.

[0036] Secondly, this application also provides a user information merging device. The device includes:

[0037] The processing module is used to normalize the original user information of the users to be merged, so as to obtain the target user information of the users to be merged.

[0038] The determination module is used to determine the user type of the users to be merged based on the target user information of the users to be merged.

[0039] The grouping module is used to group the users to be merged according to their user type and target user information, so as to obtain at least one set of target users.

[0040] The merging module is used to merge the target user information of the users to be merged in each target user set to obtain the general user information of the users to be merged in each target user set.

[0041] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0042] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0043] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0044] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0045] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0046] Fourthly, this application also provides a computer-readable storage medium. This computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0047] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0048] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0049] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0050] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0051] Fifthly, this application also provides a computer program product. This computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0052] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0053] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0054] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0055] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0056] The aforementioned user information merging method, apparatus, device, storage medium, and program product obtain target user information by acquiring the original user information of all users to be merged and normalizing it. The user type of each user to be merged is determined based on the target user information. Then, the users to be merged are grouped according to their user type and the target user information, resulting in multiple target user sets. The user information of all users to be merged in all target user sets is merged to obtain general user information for all users in each target user set. Since the original user information of all users to be merged is normalized before merging the user information of each user, transforming it into target user information under the same identification method, a foundation is provided for subsequent user information merging. Furthermore, merging target user information under the same identification method is more convenient and simpler than directly merging original user information from multiple systems, and the merging quality is correspondingly improved. Furthermore, before merging user information, different grouping strategies are applied to different types of users to group their information more effectively and improve the quality of user information grouping. Then, for each target user set obtained after grouping, the target user information is merged within that target user set, further improving the quality and efficiency of user information merging. This ultimately achieves the goal of improving the efficiency and quality of user information merging. Attached Figure Description

[0057] Figure 1 This is an application environment diagram of a user information merging method provided in this embodiment;

[0058] Figure 2 This is a flowchart illustrating the first user information merging method provided in this embodiment;

[0059] Figure 3 This is a schematic diagram of the first method for grouping users to be merged, as provided in this embodiment.

[0060] Figure 4 This is a schematic diagram of the second process for grouping users to be merged, as provided in this embodiment;

[0061] Figure 5 This is a schematic diagram illustrating a process for merging newly added user information provided in this embodiment;

[0062] Figure 6 This is a flowchart illustrating the second user information merging method provided in this embodiment;

[0063] Figure 7 This is a structural block diagram of the first user information merging device provided in this embodiment;

[0064] Figure 8 This is a structural block diagram of the second type of user information merging device provided in this embodiment;

[0065] Figure 9 This is a structural block diagram of the third type of user information merging device provided in this embodiment;

[0066] Figure 10 This is a structural block diagram of the fourth type of user information merging device provided in this embodiment;

[0067] Figure 11 This is a structural block diagram of the fifth type of user information merging device provided in this embodiment;

[0068] Figure 12 This is a structural block diagram of the sixth type of user information merging device provided in this embodiment;

[0069] Figure 13 This is a structural block diagram of the seventh type of user information merging device provided in this embodiment;

[0070] Figure 14 This is an internal structural diagram of a computer device provided in this embodiment. Detailed Implementation

[0071] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0072] The user information merging method provided in this application embodiment can be applied to, for example... Figure 1 In the application environment shown, in one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows. Figure 1 As shown. This computer device includes a processor, memory, and network interface connected via a system bus.

[0073] The computer device's processor provides computing and control capabilities. Its memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs in the non-volatile storage media. The computer device's database stores data related to user information merging. The computer device's network interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a user information merging method.

[0074] In one embodiment, such as Figure 2 As shown, a user information merging method is provided, which can be applied to... Figure 1 Taking a computer as an example, the explanation includes the following steps:

[0075] S201, normalize the original user information of the users to be merged to obtain the target user information of the users to be merged.

[0076] In this context, the users to be merged can be all users in the systems whose user information needs to be merged. Taking an enterprise system as an example, the users to be merged can be users who have registered in the various enterprises to be merged. The original user information can be the user information recorded by the users to be merged in their registration systems. In this embodiment, the normalization process can be to normalize the original user information of the users to be merged in different systems into target user information under the same identification method. The target user information can be user information identified using the identification method of the merged new system.

[0077] Optionally, in this embodiment, there are many ways to normalize the original user information of the users to be merged, and there is no limitation on this. One possible approach is to use a pre-trained user information normalization model, input the original user information of the users to be merged into the user information normalization model, and automatically output the target user information of the users to be merged.

[0078] Another possible approach is to classify the original user information of the users to be merged and determine the normalization strategy corresponding to each category; then, based on the normalization strategy for each category, normalize the user information of the corresponding category to obtain the target user information of the users to be merged. Optionally, taking a scenario of merging multiple enterprises as an example, obtain the original user information of all users to be merged and classify the original user information into multiple categories. Optionally, this embodiment can include different categories of information for the original user information of different types of users to be merged. Specifically, if the user type of the user to be merged is a natural person, then the original user information of the user to be merged can at least include information on the category of legal entity, the category of identification document, the category of identification document number, and the category of user name. Based on the pre-determined normalization strategy corresponding to each category, normalize the original user information of the corresponding category to obtain the target user information of the user to be merged under the identification method of the new system. If the user type of the user to be merged is a non-natural person, then the original user information of the user to be merged can at least include information on the category of legal entity and the category of customer name. Based on the pre-determined normalization strategy for each category, the original user information of the corresponding category is normalized to obtain the target user information of the users to be merged under the identification method of the new system.

[0079] For example, the normalization strategy corresponding to the legal entity category can be: determining the legal entity information of the enterprise to which the user belongs when opening a user ID or account, and assigning a corresponding legal entity identification code to each legal entity. It should be noted that each enterprise will only have one legal entity. The normalization strategy corresponding to the document type category can be: using pre-defined document type codes to convert the original system's document type codes, and uniformly recognizing ID cards, household registration books, and temporary ID cards as ID cards and converting them; for document types that are empty, directly using the original system's user ID to ensure that the category information is not empty. The normalization strategy corresponding to the document number category can be: uniformly converting all types of document numbers to uppercase, and uniformly upgrading valid 15-digit ID card numbers to 18-digit ID card numbers. The normalization strategy corresponding to the name category can be: directly using the valid names of customers in the original system. The normalization strategy corresponding to the customer name category can be: directly using valid customer names. It should be noted that if the information in a certain category is empty, the user ID from the original system will be used for normalization to ensure that the information in each category is not empty, thus providing a guarantee for the subsequent merging of user information.

[0080] In addition, other categories of information are not processed during normalization if the information in the category is empty. These include: Unified Social Credit Code document category, National Organization Code category, Normalized National Organization Code category, Enterprise Legal Person Business License category, Enterprise Non-Legal Person Business License Number category, Individual Business License Number category, National Tax Registration Certificate Number category, Local Tax Registration Certificate Number category, Other Certificate Type category, and Other Certificate Number category. For the Unified Social Credit Code document category, National Organization Code category, Enterprise Legal Person Business License category, Enterprise Non-Legal Person Business License Number category, Individual Business License Number category, National Tax Registration Certificate Number category, and Local Tax Registration Certificate Number category, the normalization strategy can be simply to convert to uppercase. The normalization strategy for the Normalized National Organization Code category can be: if the information is not empty, use the original information directly; if empty, determine if the information corresponding to the Unified Social Credit Code document type is an 18-digit valid number; if so, truncate digits 9-17 as the information corresponding to the Normalized National Organization Code category. The normalization strategy corresponding to the document type category can be: transcoding according to a predetermined code value standard. It should be noted that other document types are only collected when none of the above-mentioned document types are provided; otherwise, they are left blank.

[0081] In this embodiment, the original user information of all users to be merged is classified, and each type of information is normalized according to the pre-determined normalization strategy. This makes the user information of the users to be merged more uniform after normalization, improves the quality of normalization, and enhances the rigor of normalization, thus providing a guarantee for the subsequent merging of target user information.

[0082] S202, Determine the user type of the user to be merged based on the target user information of the user to be merged.

[0083] The user type can be the user registration type of the user to be merged, for example, it can be a natural person user or a non-natural person user.

[0084] Optionally, in this embodiment, different user types can be determined based on the target user information of the users to be merged. Accordingly, the user type of the users to be merged can be determined based on the target user information of the users to be merged according to a pre-set user type determination rule; or it can be determined directly based on a certain target user information in the target user information of the users to be merged that is used to characterize the user type, without limitation.

[0085] S203, based on the user type and target user information of the users to be merged, group the users to be merged to obtain at least one target user set.

[0086] The target user set can be a set of users to be merged that share the same information representing the same target object.

[0087] Optionally, the grouping of users to be merged can be done by determining the categories of user information to be compared based on the user type of the users to be merged, and grouping users with the same categories of user information to be compared into a target user set. It should be noted that the target user information for each user to be merged can include multiple categories. Information corresponding to all categories in the target user information of the users to be merged is obtained, and users with the same categories of user information to be compared are grouped into a target user set. For example, the categories of user information to be compared for natural person users can be set as four categories: legal entity category, document type category, document number category, and name category. Users of natural person type whose information is identical in all four categories are then grouped into a target user set. Similarly, the categories of user information to be compared for non-natural person type users can be set as two categories: legal entity category and customer name category. Users of non-natural person type users whose information is identical in both categories are then grouped into a target user set.

[0088] It is understandable that there can be different user grouping methods for each type of user to be merged. That is, the categories of user information to be compared are different when grouping different types of users to be merged.

[0089] S204, merge the target user information of the users to be merged in each target user set to obtain the general user information of the users to be merged in each target user set.

[0090] Among them, general user information can be information representing all user information in each target user set.

[0091] Optionally, there are many ways to merge the target user information of the users to be merged in each target user set to obtain the general user information of the users to be merged in each target user set, and there is no limitation on this. One possible approach is to merge each type of information in the target user information of all users to be merged in each target user set, and then merge each type of information again to obtain all the target user information of all users to be merged in that target user set, and use this as the general user information of the users to be merged in that target user set. Another possible approach is to sort the users to be merged in each target user set according to the user identifier information in the target user information of the users to be merged; and determine the general user information of the users to be merged in that target user set based on the sorting result. Here, the user identifier information can be numerical information used to distinguish users. It can be understood that in a system, each user's user identifier is unique. Optionally, the sorting of users to be merged in the target user set can be done by sorting the user identifier information of all users to be merged in each target user set according to a pre-set sorting rule. For example, it can be sorted from smallest to largest or from largest to smallest, without limitation. Based on the sorting result, the user information of the user to be merged who ranks first (i.e., the user with the smallest or largest user identifier information) can be used as the common user information for all users to be merged in that target user set.

[0092] In this embodiment, the user identification information of all users to be merged in each target user set can be sorted to obtain a sorting result. The user information of the user to be merged that appears first in the sorting result is used as the general user information for that target user set. This makes the user information merging process simpler and faster, improving the merging effect and efficiency of the user information of the users to be merged.

[0093] In the above embodiments, before merging the user information of each user to be merged, all user information to be merged is normalized, transforming the original user information of all users to be merged into target user information under the same identification method, providing a foundation for subsequent user information merging. Furthermore, merging target user information under the same identification method is more convenient and simpler than directly merging original user information from multiple systems, and the merging quality is correspondingly improved. In addition, before merging user information, different grouping strategies are used to group different types of users, allowing for more targeted grouping of user information for each type, improving the grouping quality. For each target user set obtained after grouping various types of users, the target user information is merged within the target user set, further improving the merging quality and efficiency. Thus, the goal of improving the efficiency and quality of user information merging can be achieved.

[0094] Furthermore, when grouping users to be merged, if the users to be merged are individual users, there may be situations where some users need to have their information adjusted before they can be grouped. To improve the merging effect of user information, in one embodiment, such as... Figure 3 As shown, based on the user type of the users to be merged and the target user information, the users to be merged are grouped to obtain at least one set of target users, including:

[0095] S301, Begin.

[0096] S302, if the user type of the user to be merged is a natural person, then determine whether the user to be merged contains the target user based on the target user information of the user to be merged. If yes, then execute S303; otherwise, then execute S304.

[0097] The target users are those whose target user information needs to be adjusted before merging. For example, the target users can be those whose user information contains multiple identity categories.

[0098] Optionally, in this embodiment, the method for determining whether the users to be merged include the target user can be to obtain a certain type of information based on the target user information of the users to be merged, and check whether the type of information has multiple information elements, for example, check whether it has multiple legal entity category information; if so, then it is regarded as the target user.

[0099] In this embodiment, when the user to be merged is a natural person, the system determines whether the user to be merged includes the target user based on a certain type of information in the target user information of the user to be merged, thus providing a basis for subsequent adjustments to the target user information of the target user.

[0100] In a preferred embodiment, the target user can be a user registered on different systems that is to be merged. If the users to be merged are registered users on different systems, the method to determine whether the users to be merged include the target user can be: based on the system affiliation information of the registration system corresponding to the user to be merged, determine whether the registration system contains a subsystem; wherein, the system affiliation information of the registration system is recorded in the target user information of the user to be merged; if so, the user to be merged is determined to be the target user.

[0101] The system affiliation information of the registration system can be information representing the legal entity to which the system belongs. The registration system can be the system of the unit to which the user account belongs, meaning the user has registered an account under this system. Subsystems can be other systems included in the registration system, and the user information of the subsystems needs to be inherited by the registration system. For example, the registration system can be the system of a parent company A, which may include subsidiaries A1 and A2. It should be noted that although subsidiaries A1 and A2 can handle business and have their own legal entities, they do not have online systems and their user information needs to be stored in the corresponding parent company A's system. For instance, if the user information of subsidiaries A1 and A2 is stored in the parent company A's system, and a user has registered an account in both subsidiaries A1 and A2, when parent company A needs to be merged into company B, the user information in the statistics will show the legal entity to which parent company A belongs. However, the actual legal entity to which the user belongs should be the legal entity to which subsidiaries A1 and A2 belong. In this case, the user is considered the target user.

[0102] Optionally, it can be determined whether the registration system corresponding to the user to be merged contains a subsystem based on a certain type of information in the user information of the user to be merged. Alternatively, the user information of the user to be merged can be parsed to obtain the parsing result, and then it can be determined whether the registration system corresponding to the user to be merged contains a subsystem. Users whose registration systems corresponding to the user to be merged contain a subsystem are selected as target users.

[0103] In this embodiment, based on the affiliation information of the registration system corresponding to the user to be merged, it can be determined whether the registration system contains a subsystem. If it does, the user to be merged is then designated as the target user. Using the affiliation information of the registration system corresponding to the user to be merged to determine whether the user is a target user simplifies the process of identifying target users and provides a basis for subsequent adjustments to the user information of the target user.

[0104] S303, if included, then adjust the user information of the target user, and take the users to be merged with the same target user information after adjustment as a set of target users.

[0105] Optionally, the user information of the target user can be adjusted by inputting the target user information into a pre-trained user information adjustment model, which processes the target user information and outputs the adjusted target user information. Alternatively, it can be adjusted according to a pre-set target user information adjustment strategy. In one embodiment, the strategy for adjusting the target user information may be: migrating the target user information based on the number of subsystems included in the registration system to obtain user information corresponding to each subsystem; and adjusting the system affiliation information in the target user information corresponding to each subsystem.

[0106] The system affiliation information can be the affiliation legal entity information, used to indicate which subsystem the user belongs to. Optionally, in this embodiment, the number of subsystems contained in the registration system corresponding to the user to be merged can be determined first. Based on the number of subsystems, the target user information of the target user is migrated. The migration of the target user information can be done by copying the target user information of the target user according to the number of subsystems, and copying the target user information of the target user to each subsystem accordingly, generating target user information for multiple target users commensurate with the number of subsystems, i.e., obtaining target user information corresponding to each subsystem. The system affiliation information in the target user information corresponding to each subsystem is then adjusted to match the affiliation legal entity information of that subsystem.

[0107] In this embodiment, the target user information of the target user can be copied multiple times according to the number of subsystems contained in the registration system, and the target user information of the target user can be mapped to each subsystem. The system affiliation information in each target user information can be adjusted to the affiliation information corresponding to that subsystem.

[0108] S304, if not included, then users with the same target user information to be merged will be grouped into a target user set.

[0109] In this embodiment, if it is determined from the target user information of the users to be merged that the target user is not included, then the users to be merged with the same target user information are directly regarded as a set of target users.

[0110] In the above embodiments, when the users to be merged are individual users, it is determined whether they include users whose user information needs to be adjusted (i.e., target users). If so, the target user information of the target user is adjusted before grouping. This can make the target user information of the users to be merged in the grouped target user set more complete, providing a guarantee for the subsequent merging of target user information.

[0111] In one embodiment, such as Figure 4The diagram illustrates a detailed process for grouping users to be merged into at least one target user set based on their user type and target user information when the users to be merged are non-natural person users. This process may include the following steps:

[0112] S401, if the user type of the users to be merged is a non-natural person, then the users to be merged with the same first key information are divided into an initial user set.

[0113] Non-natural persons can include legal persons, individual businesses, and social organizations, and legal persons can include both corporate and non-corporate legal persons. The primary key information can be one or more pieces of information from the user information that are most commonly used to identify a user as a non-natural person. The number of primary key information pieces can be one or more. For example, it could be the legal person category information and customer name category information from the non-natural person user information. The initial user set can be a set of users whose primary key information is completely identical and are to be merged.

[0114] Optionally, in this embodiment, the method of dividing the initial user set may be to obtain the user information of all users whose user type is non-natural persons, classify the information of each category in the user information of non-natural persons, compare whether the first key information of each non-natural person user is the same according to the predetermined first key information, and divide the users with completely identical first key information into a group of initial user sets.

[0115] S402, for each initial user set, users with the same second key information are divided into a target user set.

[0116] The target user information of the users to be merged includes at least one first key piece of information and at least one second key piece of information. The second key piece of information can be any other information in the user information of the users to be merged, except for the first key piece of information.

[0117] Optionally, in this embodiment, for each initial user set, the second key information of all users to be merged can be obtained, and it can be determined whether there are other types of information that are the same in the second key information of each pair of users to be merged. If so, they are regarded as a target user set; if the second key information of a certain user to be merged does not contain the same type of information as the second key information of other users to be merged, it is regarded as a separate target user set.

[0118] It should be noted that, to make the determination of the target user set more rigorous and reliable, if a certain category of information is missing when comparing the second key information of two users to be merged, we can search within the second key information of those users to see if there are other categories that can substitute for that category. For example, the unified social credit code certificate category can be replaced by the national organization code category, the normalized national organization code category, the enterprise legal person business license category, the enterprise non-legal person business license number category, and the individual business license number category; the national tax registration certificate number category can be replaced by the local tax registration certificate number category.

[0119] In the above embodiments, when the users to be merged are non-natural person users, the users to be merged with the same first key information are first grouped into an initial user set. Then, in each initial user set, it is determined whether there are users to be merged with the same second key information. The users to be merged with the same second key information are further divided into target user sets. This makes the method of determining the target user set for non-natural person users more complete and improves the accuracy of the target user set for non-natural person users.

[0120] In addition, after merging the user information of all existing users to be merged, it is also necessary to merge newly added user information to ensure that the user information system can be dynamically merged. In one embodiment, such as Figure 5 As shown, the above-mentioned user information merging method also includes:

[0121] S501, if user information of at least two new users is received, then the at least two new users are grouped to obtain at least one reference user set.

[0122] The reference user set can be a set of newly added users whose information categories are the same as those to be compared.

[0123] In this embodiment, for the user information of newly added users, the category information of each newly added user can be obtained. The category information of each newly added user is compared, and newly added users whose user information categories are the same are grouped into a reference user set. It should be noted that the category information of the user information to be compared can be pre-specified and is the same category used when merging existing users to be merged. Of course, if the user information of a certain newly added user is different from the user information of all other users, then that newly added user is treated as a separate reference user set.

[0124] S502, compare the user information of each newly added user in each reference user set with the general user information corresponding to each target user set to determine the target user set corresponding to each newly added user.

[0125] Optionally, in this embodiment, comparing the user information of each newly added user in each reference user set with the general user information corresponding to each group of target user sets to determine the target user set corresponding to each newly added user can be as follows: For each newly added user in each reference user set, determine whether the information of the user information category to be compared in the user information of the newly added user is the same as the corresponding information in the general user information corresponding to each group of target user sets. If so, add the user information of the newly added user to the corresponding target user set. If not, determine whether the target user sets of other newly added users in the reference user set to which the newly added user belongs have been determined. If so, use the target user sets corresponding to other users as the target user set corresponding to the newly added user. Otherwise, use the group of reference user sets as a new target user set.

[0126] Specifically, for each new user in each reference user set, the category information in the user information is obtained, and each category information is compared with the corresponding category information in the general user information of each target user set. It is determined whether the information of the user information to be compared is the same. If so, the user information of the new user is added to the corresponding target user set. If not, it is determined whether other new users B in the reference user set to which the new user belongs can determine the corresponding target user set. If the reference user set to which the new user belongs contains a new user B whose target user set has been determined, the new user is added to the target user set corresponding to new user B. If the reference user set to which the new user belongs does not contain a new user B whose target user set has been determined, then this set of reference user sets is taken as a new target user set.

[0127] S503, add each new user to the corresponding target user set, and adjust the user information of each new user to the general user information of the target user set to which they belong.

[0128] Optionally, adjusting the user information of each newly added user to the general user information of the target user set can be done in two ways: either directly adjusting the user information of the newly added user to the general user information of the target user set before the update; or, for the updated target user set, performing the operation again to sort the users to be merged in the target user set according to the user identifier information in the target user information of the users to be merged, and determining the general user information of the users to be merged in the target user set based on the sorting result. This completes the update of the target user set.

[0129] In the above embodiments, the user information of newly added users is grouped to obtain a reference user set, and the user information of each newly added user in each reference user set is compared with the general user information corresponding to each target user set. Based on the comparison results, the grouping and merging of the newly added users' user information are completed, which can maintain the dynamic merging of the user information system and improve the efficiency of user information merging.

[0130] To facilitate understanding of the content of this embodiment by those skilled in the art, in one embodiment, such as Figure 6 As shown, the user information merging method may include the following steps:

[0131] S601, classify the original user information of the users to be merged, and determine the normalization strategy corresponding to each category.

[0132] S602, based on the normalization strategy corresponding to each category, normalize the original user information of the corresponding category to obtain the target user information of the users to be merged.

[0133] S603. Based on the target user information of the users to be merged, determine the user type of the users to be merged. If it is a natural person, then execute S604; if it is a non-natural person, then execute S608.

[0134] S604. If the user type of the user to be merged is a natural person, then determine whether the registration system contains a subsystem based on the system affiliation information of the registration system corresponding to the user to be merged. If yes, then execute S605; otherwise, execute S607.

[0135] The system affiliation information of the registration system is recorded in the target user information of the users to be merged.

[0136] S605, if the user to be merged is determined to be the target user, then the target user information of the target user is migrated according to the number of subsystems contained in the registration system to obtain the target user information corresponding to each subsystem.

[0137] S606, adjust the system affiliation information in the target user information corresponding to each subsystem. Then, group the users to be merged who have the same target user information after adjustment into a single target user set.

[0138] S607, users with the same target user information are grouped into a set of target users.

[0139] S608 divides users to be merged who have identical first key information into an initial user set.

[0140] S609, for each initial user set, users with the same second key information are divided into a target user set.

[0141] The target user information of the users to be merged includes at least one first key piece of information and at least one second key piece of information.

[0142] S610, for each target user set, sort the users to be merged in the target user information according to the user identifier information in the target user information of the users to be merged.

[0143] S611. Based on the sorting results, determine the general user information of the users to be merged in the target user set of this group.

[0144] S612, if user information of at least two new users is received, then the at least two new users are grouped to obtain at least one reference user set.

[0145] S613, for each new user in each reference user set, if the user information of the new user is different from the general user information corresponding to each target user set, then determine whether the other new users in the reference user set to which the new user belongs have been identified as the target user set. If yes, then execute S614; otherwise, then execute S615.

[0146] S614, take the target user set corresponding to other newly added users as the target user set corresponding to this newly added user.

[0147] S615, taking this set of reference users as a new target user set, will determine the general user information for this target user set.

[0148] S616, add each new user to the corresponding target user set, and adjust the user information of each new user to the general user information of the target user set to which they belong.

[0149] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0150] Based on the same inventive concept, this application also provides a user information merging apparatus for implementing the user information merging method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more user information merging apparatus embodiments provided below can be found in the limitations of the user information merging method described above, and will not be repeated here.

[0151] In one embodiment, such as Figure 7 As shown, a user information merging device 1 is provided, including: a processing module 10, a determining module 11, a grouping module 12, and a merging module 13, wherein:

[0152] Processing module 10 is used to normalize the original user information of the users to be merged, so as to obtain the target user information of the users to be merged.

[0153] The first determining module 11 is used to determine the user type of the user to be merged based on the target user information of the user to be merged.

[0154] The first grouping module 12 is used to group the users to be merged according to the user type of the users to be merged and the target user information to obtain at least one set of target users.

[0155] The merging module 13 is used to merge the target user information of the users to be merged in each target user set to obtain the general user information of the users to be merged in each target user set.

[0156] In one embodiment, such as Figure 8 As shown, the first grouping module 12 includes a first determining unit 120 and an adjusting unit 121. Wherein:

[0157] The first determining unit 120 is used to determine whether the users to be merged include the target user, based on the target user information of the users to be merged, if the user type of the user to be merged is a natural person.

[0158] Among them, the target users are the users whose target user information needs to be adjusted and who are to be merged.

[0159] The adjustment unit 121 is used to adjust the target user information of the target user when the users to be merged include the target user, and to take the users to be merged with the same target user information after adjustment as a set of target users.

[0160] In one embodiment, the first determining unit 120 includes a first determining subunit and a second determining subunit. Wherein:

[0161] The first determining subunit is used to determine whether the registration system contains a subsystem based on the system affiliation information of the registration system corresponding to the user to be merged.

[0162] The system affiliation information of the registration system is recorded in the target user information of the users to be merged.

[0163] The second determining subunit is used to determine the user to be merged as the target user if the registration system contains a subsystem.

[0164] In one embodiment, the adjustment unit 121 includes a migration subunit and an adjustment subunit. Wherein:

[0165] The migration subunit is used to migrate the target user information of the target user according to the number of subsystems contained in the registration system, so as to obtain the target user information corresponding to each subsystem.

[0166] The adjustment subunit is used to adjust the system affiliation information in the target user information corresponding to each subsystem.

[0167] In one embodiment, such as Figure 9 As shown, the first grouping module 12 includes a first partitioning unit 122 and a second partitioning unit 123. Wherein:

[0168] The first partitioning unit 122 is used to partition users whose first key information is completely identical into an initial user set when the user type of the users to be merged is a non-natural person.

[0169] The second partitioning unit 123 is used to partition users with the same second key information into a target user set for each initial user set.

[0170] The target user information of the users to be merged includes at least one first key piece of information and at least one second key piece of information.

[0171] In one embodiment, such as Figure 10 As shown, the processing module 10 includes a strategy determination unit 100 and a processing unit 101. Wherein:

[0172] The strategy determination unit 100 is used to classify the original user information of the users to be merged and determine the normalization strategy corresponding to each category.

[0173] The processing unit 101 is used to normalize the original user information of the corresponding category according to the normalization strategy of each category, so as to obtain the target user information of the users to be merged.

[0174] In one embodiment, such as Figure 11 As shown, the merging module 13 includes a sorting unit 130 and a second determining unit 131. Wherein:

[0175] The sorting unit 130 is used to sort the users to be merged in the target user set for each target user set according to the user identification information in the target user information of the users to be merged.

[0176] The second determining unit 131 is used to determine the general user information of the users to be merged in the target user set of the group based on the sorting results.

[0177] In one embodiment, such as Figure 12 As shown, Figure 7 The user information merging device 1 shown also includes a second grouping module 14, a second determining module 15, and an adjustment module 16. Wherein:

[0178] The second grouping module 14 is used to group at least two new users to obtain at least one reference user set if user information of at least two new users is received.

[0179] The second determining module 15 is used to compare the user information of each newly added user in each reference user set with the general user information corresponding to each target user set, and determine the target user set corresponding to each newly added user.

[0180] The adjustment module 16 is used to add each new user to the corresponding target user set and adjust the user information of each new user to the general user information of the target user set to which they belong.

[0181] In one embodiment, such as Figure 13 As shown, the second determining module 15 includes a judging unit 150 and a third determining unit 151. Wherein:

[0182] The judgment unit 150 is used to determine whether other new users in the reference user set to which the new user belongs have been identified as the target user set if the user information of the new user is different from the general user information corresponding to each target user set.

[0183] The third determining unit 151 is used to determine the target user set corresponding to other new users in the reference user set to which the new user belongs, if the target user set corresponding to other new users has been determined.

[0184] Each module in the aforementioned user information merging device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0185] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 14 As shown, the computer device includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a user information method. The display unit is used to form a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0186] Those skilled in the art will understand that Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0187] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0188] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0189] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0190] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0191] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0192] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0193] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0194] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0195] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0196] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0197] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0198] The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged.

[0199] Based on the target user information of the users to be merged, determine the user type of the users to be merged;

[0200] Based on the user type and target user information of the users to be merged, the users to be merged are grouped to obtain at least one set of target users;

[0201] The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set.

[0202] It should be noted that the user information (including but not limited to various categories of information, original user information, and target user information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0203] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0204] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0205] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for merging user information, characterized in that, include: The original user information of the users to be merged is normalized to obtain the target user information of the users to be merged. The original user information of different types of users to be merged includes different categories of information. According to the pre-determined normalization strategy for each category, the original user information of the corresponding category is normalized to obtain the target user information of the users to be merged under the identification method of the new system. Based on the target user information of the users to be merged, determine the user type of the users to be merged; Based on the user type of the users to be merged and the target user information, the users to be merged are grouped to obtain at least one set of target users; Merge the target user information of the users to be merged in each target user set to obtain the general user information of the users to be merged in each target user set. The step of grouping the users to be merged according to their user types and target user information to obtain at least one set of target users includes: If the user type of the user to be merged is a natural person, then based on the target user information of the user to be merged, it is determined whether the user to be merged includes a target user; wherein, the target user is the user to be merged whose target user information needs to be adjusted. If included, the target user information of the target user is adjusted, and the users to be merged with the same target user information after adjustment are taken as a set of target users; If the users to be merged belong to registered users under different systems, then based on the target user information of the users to be merged, it is determined whether the users to be merged include the target user, including: Based on the system affiliation information of the registration system corresponding to the user to be merged, it is determined whether the registration system contains a subsystem; wherein, the system affiliation information of the registration system is recorded in the target user information of the user to be merged. If so, then the user to be merged is determined to be the target user.

2. The method according to claim 1, characterized in that, Adjusting the target user information of the target user includes: Based on the number of subsystems included in the registration system, the target user information of the target user is migrated to obtain the target user information corresponding to each subsystem; Adjust the system affiliation information in the target user information corresponding to each subsystem.

3. The method according to claim 1, characterized in that, The step of grouping the users to be merged according to their user types and target user information to obtain at least one set of target users includes: If the user type of the users to be merged is a non-natural person, then the users to be merged with the same first key information are divided into an initial user set; For each initial user set, users with the same second key information are grouped into a target user set; The target user information of the users to be merged includes at least one first key information and at least one second key information.

4. The method according to any one of claims 1-3, characterized in that, The normalization process of the original user information of the users to be merged to obtain the target user information of the users to be merged includes: The original user information of the users to be merged is classified, and the normalization strategy corresponding to each category is determined. Based on the normalization strategy corresponding to each category, the original user information of the corresponding category is normalized to obtain the target user information of the users to be merged.

5. The method according to any one of claims 1-3, characterized in that, The target user information of the users to be merged in each target user set is merged to obtain the general user information of the users to be merged in each target user set, including: For each target user set, sort the users to be merged in that target user set according to the user identifier information in the target user information of the users to be merged; Based on the sorting results, determine the general user information of the users to be merged in the target user set of this group.

6. The method according to any one of claims 1-3, characterized in that, The method further includes: If user information for at least two new users is received, the at least two new users are grouped to obtain at least one reference user set; The user information of each newly added user in each reference user set is compared with the general user information corresponding to each target user set to determine the target user set corresponding to each newly added user. Each newly added user is added to the corresponding target user set, and the user information of each newly added user is adjusted to the general user information of the target user set to which it belongs.

7. The method according to claim 6, characterized in that, The step of comparing the user information of each newly added user in each reference user set with the general user information corresponding to each target user set to determine the target user set corresponding to each newly added user includes: For each new user in each reference user set, if the user information of the new user is different from the general user information corresponding to each target user set, then determine whether the other new users in the reference user set to which the new user belongs have been identified as the target user set. If so, then the target user set corresponding to the other newly added users shall be used as the target user set corresponding to the newly added user.

8. A user information merging device, characterized in that, The device includes: The processing module is used to normalize the original user information of the users to be merged to obtain the target user information of the users to be merged. The original user information of different types of users to be merged includes different categories of information. According to the pre-determined normalization strategy for each category, the original user information of the corresponding category is normalized to obtain the target user information of the users to be merged under the identification method of the new system. The determination module is used to determine the user type of the user to be merged based on the target user information of the user to be merged; The grouping module is used to group the users to be merged according to the user type of the users to be merged and the target user information, so as to obtain at least one set of target users; The merging module is used to merge the target user information of the users to be merged in each target user set to obtain the general user information of the users to be merged in each target user set. The device further includes: a first determining unit, configured to determine whether the users to be merged contain a target user based on the target user information of the users to be merged if the user type of the users to be merged is a natural person; wherein the target user is the user to be merged that needs to have its target user information adjusted; and an adjusting unit, configured to adjust the target user information of the target user when the users to be merged contain the target user, and to group the users to be merged with the same target user information after adjustment into a set of target users. The device further includes: a first determining subunit, configured to determine whether the registration system contains a subsystem based on the system affiliation information of the registration system corresponding to the user to be merged; wherein the system affiliation information of the registration system is recorded in the target user information of the user to be merged; and a second determining subunit, configured to determine the user to be merged as the target user if the registration system contains a subsystem.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images